Problem Solved!!
Thank you Vilian.
The problem is a "user error."
Image2pdf supplies 2 dll's - one uses "STDCALL" convention and one does not.
My new version of xHarbour ( 1.2 ) must have the STDCALL version and I was calling the "other" DLL file by mistake.
Following advice of Vilian, I call the "Image2PDF StdCall.dll" and everything seems to work fine now, as it did before.
There is no problem with FWH libraries, as long as the FWH libraries are listed before the xharbour libraries in the link script. I looked at the linker map and I believe that the FWH version of CALLDLL() is being used - not xHarbour CALLDLL()
So, Antonio, I apologize for wasting your valuable time, and the time of others who replied and monitored this topic.
FWH 10.1 - DLL32 Function
- don lowenstein
- Posts: 196
- Joined: Mon Oct 17, 2005 9:09 pm
- Contact:
Re: FWH 10.1 - DLL32 Function
Don Lowenstein
www.laapc.com
www.laapc.com
- Antonio Linares
- Site Admin
- Posts: 37481
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Contact:
Re: FWH 10.1 - DLL32 Function
Don,
glad to know it is solved
Vilian,
many thanks for your help
glad to know it is solved
Vilian,
many thanks for your help
Re: FWH 10.1 - DLL32 Function
How can I make the FWH libraries linked before xHarbour libraries???don lowenstein wrote:Problem Solved!!
Thank you Vilian.
The problem is a "user error."
Image2pdf supplies 2 dll's - one uses "STDCALL" convention and one does not.
My new version of xHarbour ( 1.2 ) must have the STDCALL version and I was calling the "other" DLL file by mistake.
Following advice of Vilian, I call the "Image2PDF StdCall.dll" and everything seems to work fine now, as it did before.
There is no problem with FWH libraries, as long as the FWH libraries are listed before the xharbour libraries in the link script. I looked at the linker map and I believe that the FWH version of CALLDLL() is being used - not xHarbour CALLDLL()
So, Antonio, I apologize for wasting your valuable time, and the time of others who replied and monitored this topic.
I Am using xBuildW.exe and cannotcontrol this order??
- don lowenstein
- Posts: 196
- Joined: Mon Oct 17, 2005 9:09 pm
- Contact:
Re: FWH 10.1 - DLL32 Function
Normally, if using a .lnk file to define the libraries to "pull in", the references are resolved in the order of the libraries listed.
ie - If FWH libraries listed before the xHarbour libraries, duplicate references will be pulled from FWH libraries.
ie - If FWH libraries listed before the xHarbour libraries, duplicate references will be pulled from FWH libraries.
Don Lowenstein
www.laapc.com
www.laapc.com