FWH 10.1 - DLL32 Function

Re: FWH 10.1 - DLL32 Function

Postby don lowenstein » Fri Feb 19, 2010 9:56 pm

Problem Solved!! :D

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.
Don Lowenstein
www.laapc.com
User avatar
don lowenstein
 
Posts: 197
Joined: Mon Oct 17, 2005 9:09 pm

Re: FWH 10.1 - DLL32 Function

Postby vilian » Sat Feb 20, 2010 3:18 am

Cool
Sds,
Vilian F. Arraes
vilian@vfatec.com.br
Belém-Pa-Brazil
User avatar
vilian
 
Posts: 975
Joined: Wed Nov 09, 2005 2:17 am
Location: Brazil

Re: FWH 10.1 - DLL32 Function

Postby Antonio Linares » Sat Feb 20, 2010 8:53 am

Don,

glad to know it is solved :-)

Vilian,

many thanks for your help :-)
regards, saludos

Antonio Linares
www.fivetechsoft.com
User avatar
Antonio Linares
Site Admin
 
Posts: 42082
Joined: Thu Oct 06, 2005 5:47 pm
Location: Spain

Re: FWH 10.1 - DLL32 Function

Postby codemaker » Mon Jun 07, 2010 8:25 pm

don lowenstein wrote:Problem Solved!! :D

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.

How can I make the FWH libraries linked before xHarbour libraries???
I Am using xBuildW.exe and cannotcontrol this order??
User avatar
codemaker
 
Posts: 208
Joined: Wed Dec 03, 2008 4:48 pm
Location: Belgrade, Serbia

Re: FWH 10.1 - DLL32 Function

Postby don lowenstein » Wed Jun 16, 2010 6:51 pm

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.
Don Lowenstein
www.laapc.com
User avatar
don lowenstein
 
Posts: 197
Joined: Mon Oct 17, 2005 9:09 pm

Previous

Return to FiveWin for Harbour/xHarbour

Who is online

Users browsing this forum: Google [Bot] and 29 guests