FWH 13.04 / xHarbour Commercial

[toyet]

Is there something we must do to be able to build FIVEWIN 13.04 using xHarbour November 2009?
We seem to have error(s). Thanks in advance.
Toyet

[Antonio Linares]

Why don't you use the most recent xHarbour ?

FWH 13.04 is from 2013 April and you are using xHarbour from 2009

[toyet]

Antonio,

I remember sometime ago when we use different versions of xharbour and fivewin, there was an XBP file posted somewhere and we just rebuild the FiveHMX.lib to the xHarbour version of interest.

Am thinking if this is the same case.

Toyet

[Antonio Linares]

But why don't you consider to use the most recent version ? Why to keep using 2009 version ?

[toyet]

Antonio,

Well, every penny that we save is a penny earned you know.
Our second option is to use the Harbour that comes with FWH.
Anyway, is there really no other way? The errors seems to come
mostly from FiveHCM.lib. Here's the last of the long list of
unresolved externals:

xLINK: error: Unresolved external symbol '_png_set_strip_16 referenced from FiveHCM.lib(FWPNG.obj)'.

xLINK: error: Unresolved external symbol '_png_read_update_info referenced from FiveHCM.lib(FWPNG.obj)'.

xLINK: error: Unresolved external symbol '_png_get_channels referenced from FiveHCM.lib(FWPNG.obj)'.

xLINK: error: Unresolved external symbol '_png_get_rowbytes referenced from FiveHCM.lib(FWPNG.obj)'.

xLINK: error: Unresolved external symbol '_png_read_image referenced from FiveHCM.lib(FWPNG.obj)'.

xLINK: error: Unresolved external symbol '_png_get_io_ptr referenced from FiveHCM.lib

Thanks In Advance.

Toyet

[Antonio Linares]

You have to link this library:
https://code.google.com/p/harbour-and-x ... me=png.lib

[toyet]

Thanks, Antonio. Many Thanks.

I'll let you know the results later.

Toyet

[toyet]

Antonio,

The very looong list of unresolved externals is now reduced to:

xLINK: error: Unresolved external symbol '_SendInput referenced from FiveHCM.lib(KEYBRD.obj)'.

xLINK: error: Unresolved external symbol '_GlobalMemoryStatusEx referenced from FiveHCM.lib(MEM.obj)'.

xLINK: error: Unresolved external symbol '_OleUIPasteSpecialA referenced from FiveHCM.lib(RICHEDIT.obj)'.

xLINK: error: Unresolved external symbol '__snprintf referenced from png.lib(png.obj)'.

xLINK: error: Unresolved external symbol '__CIpow referenced from png.lib(png.obj)'.

xLINK: error: Unresolved external symbol '__iob referenced from png.lib(pngerror.obj)'.

xLINK: fatal error: 7 unresolved external(s).

Thanks again in advance

Toyet

[Antonio Linares]

Please link these libraries too:

https://code.google.com/p/fivewin-contr ... =mem32.lib

https://code.google.com/p/harbour-and-x ... send32.lib

[Antonio Linares]

Also you need psapi.lib for PellesC (used in xhb.com)

My best advice: Migrate to Harbour

[driessen]

Toyet,

I use xHarbour commercial with FiveWin for many years now.

FWH 13.04 together with the latest official version of xHarbour commercial (Dec. 2012) is working just fine.

Just to let you know.

[TimStone]

I maintained an xHarbour (.com) subscription from the beginning, but finally gave it up in late 2010. The last useable version I had was August of 2010, and of course it was still labeled Beta ... though it was the distributable copy.

That version still works with my current FWH subscription ( 13.04 ), but it is my hope to be using MSVC 2010 for everything before long. My MSVC 2010 was actually updated until the release of 2012 so it is far more current. A review of the xHb libs and some tools date prior to 2008 ( in the 8/10 version ). The focus there was on the Visual xHarbour which I never used.

I normally agree with keeping the very latest subscriptions. FWH, Harbour, and Microsoft are constantly updated, and supported. That's the major reason I see them as the best path for the future.

And yes ... I realize I diverted the topic a bit.

Tim

[toyet]

Tim,

Have you tried FWH64 with xHarbour?

Toyet

[Antonio Linares]

Toyet,

Last time I tried to build xharbour 64 bits it didn't work the make file (it seemed to me that nobody was using it, our it should have been fixed).

I just tried it again, and see the error that keeps appearing:

c:\xHarbour>make_vc
Setting environment for using Microsoft Visual Studio 2010 x86 tools.
Creating System Files (ST) ...
'RC' is not recognized as an internal or external command,
operable program or batch file.
NMAKE : fatal error U1077: 'RC' : return code '0x1'
Stop.
'notepad' is not recognized as an internal or external command,
operable program or batch file.

thats why it seems to me that xharbour is not interested in 64 bits, same as it is not interested in OSes different from Windows, and this is unacceptable to me

[Antonio Linares]

I have been able to solve it copying rc.exe from VC98 to VC2010, now it is building. I have not tested it yet