FWH 16.03 & MSVC 2013 - 32 Bit (SOLVED)

[Horizon]

Hi Antonio,

Compiler errors here.

Code: Select all  Expand view

LIBCMT.lib(printf.obj) : warning LNK4006: _printf already defined in rddcdx.lib(dbfcdx1.obj); second definition ignored
   Creating library IcraW.lib and object IcraW.exp
hbpp.lib(ppcore.obj) : error LNK2001: unresolved external symbol ___acrt_iob_func
hbssl.lib(ssl.obj) : error LNK2001: unresolved external symbol ___acrt_iob_func
FiveH32.lib(HARBOUR.obj) : error LNK2019: unresolved external symbol ___acrt_iob_func referenced in function _HB_FUN_FREOPEN_STDERR
hbvm.lib(hvmall.obj) : error LNK2001: unresolved external symbol ___acrt_iob_func
rddcdx.lib(dbfcdx1.obj) : error LNK2001: unresolved external symbol ___acrt_iob_func
hbcplr.lib(hbcomp.obj) : error LNK2001: unresolved external symbol ___acrt_iob_func
hbcplr.lib(gencc.obj) : error LNK2001: unresolved external symbol ___stdio_common_vfprintf
hbpp.lib(ppcore.obj) : error LNK2001: unresolved external symbol ___stdio_common_vfprintf
hbssl.lib(ssl.obj) : error LNK2001: unresolved external symbol ___stdio_common_vfprintf
hbcplr.lib(hbmain.obj) : error LNK2001: unresolved external symbol ___stdio_common_vfprintf
hbcplr.lib(hbcomp.obj) : error LNK2001: unresolved external symbol ___stdio_common_vfprintf
hbcplr.lib(genc.obj) : error LNK2001: unresolved external symbol ___stdio_common_vfprintf
hbcplr.lib(compi18n.obj) : error LNK2001: unresolved external symbol ___stdio_common_vfprintf
FiveH32.lib(PRV2PDF.obj) : error LNK2019: unresolved external symbol ___stdio_common_vfprintf referenced in function __vfprintf_l
hbrtl.lib(errintlo.obj) : error LNK2001: unresolved external symbol ___stdio_common_vfprintf
hbvm.lib(hvmall.obj) : error LNK2001: unresolved external symbol ___stdio_common_vfprintf
rddcdx.lib(dbfcdx1.obj) : error LNK2001: unresolved external symbol ___stdio_common_vfprintf
FiveHC32.lib(ACTX.obj) : error LNK2019: unresolved external symbol "void __cdecl operator delete(void *,unsigned int)" (??3@YAXPAXI@Z) referenced in function "public: void * __thiscall TActiveX::`scalar deleting destructor'(unsigned int)" (??_GTActiveX@@QAEPAXI@Z)
FiveHC32.lib(GDIPLUS.obj) : error LNK2001: unresolved external symbol "void __cdecl operator delete(void *,unsigned int)" (??3@YAXPAXI@Z)
IcraW.exe : fatal error LNK1120: 3 unresolved externals
 

[Antonio Linares]

Hakan,

I am emailing you the FWH libs for VS2013

[Antonio Linares]

Please use this Harbour for VS2013:

https://bitbucket.org/fivetech/harbour-xharbour-builds/downloads/harbour_3.2_32bits_VS2013_20160309.zip

[Horizon]

Antonio,

With New Libs and Harbour for MSVC2013

Error List:

Code: Select all  Expand view

  Creating library IcraW.lib and object IcraW.exp
FiveH32.lib(HARBOUR.obj) : error LNK2019: unresolved external symbol ___acrt_iob_func referenced in function _HB_FUN_FREOPEN_STDERR
hbssl.lib(ssl.obj) : error LNK2001: unresolved external symbol ___acrt_iob_func
FiveH32.lib(PRV2PDF.obj) : error LNK2019: unresolved external symbol ___stdio_common_vfprintf referenced in function __vfprintf_l
hbssl.lib(ssl.obj) : error LNK2001: unresolved external symbol ___stdio_common_vfprintf
FiveHC32.lib(ACTX.obj) : error LNK2019: unresolved external symbol "void __cdecl operator delete(void *,unsigned int)" (??3@YAXPAXI@Z) referenced in function "public: void * __thiscall TActiveX::`scalar deleting destructor'(unsigned int)" (??_GTActiveX@@QAEPAXI@Z)
FiveHC32.lib(GDIPLUS.obj) : error LNK2001: unresolved external symbol "void __cdecl operator delete(void *,unsigned int)" (??3@YAXPAXI@Z)
IcraW.exe : fatal error LNK1120: 3 unresolved externals
 

[Antonio Linares]

Hakan,

Those errors come from using VS2013 and VSC2015 together

Please double check that you are using the right Harbour libs and the FWH libs that I sent you

[Horizon]

Antonio,

Will it be run MSVC 2013?

[Horizon]

Hi Antonio,

Last libraries that you have mailed to me is working good with MSVC 2013.

I have also checked in windows 7. There is not any problem.

Will you support msvc 2013 next versions of fwh?

Thank you again.

[Antonio Linares]

Hakan,

> Will you support msvc 2013 next versions of fwh?

We will always support our users

Hopefully your app finally will work with VSC2015 (or we get extra work)

[TimStone]

For clarification on a few points here:

1) On my main computer, I have VS 2013 Professional, and VS 2015 Community installed. I can build programs with Visual Studio 2015 with no problems, and they work. I can build with a .bat/.mak combination, and I can build with the IDE.

2) On my other two computers, I have ONLY VS 2015 Community. The program also builds there with absolutely no difference.

3) The C++ standards have been upgraded, and VS 2015 incorporates those changes. An article I read this morning says clearly 1/3 of all developers build programs still in C++ and that number is actually growing. ( It is significant when you consider ALL of the programming languages available ). All of work is ultimately .c code so it's a good idea to have access to the latest versions.

4) The most likely cause of problems with linking, in my experience, is that older code ( .lib files ) may be created with older versions of C and perhaps have compatibility issues. For those of us who use almost exclusively FWH / Harbour libraries, this is not an issue.

5) Right now there are FWH libraries for xHarbour( .com ), Borland, and Microsoft. To split these further ( ie. two versions of MSFT visual studio ) just increased the possibility of more problems.

I hope you can get this running in Visual Studio 2015. It will be the best for your future work.

Tim

[Antonio Linares]

Tim,

> Right now there are FWH libraries for xHarbour( .com ), Borland, and Microsoft

Also GNU MinGW gcc

> I hope you can get this running in Visual Studio 2015. It will be the best for your future work

I totally agree

thanks

[Horizon]

Hi Antonio,

As you know I had some problems with MSVC 2015 in windows 7. Most of my customers uses w7. I had to back again MSVC 2103 urgently. (Harbour (harbour_3.2_32bits_VS2013_20160309.zip), MSVC 2013, 2013 related old libraries and your fwh 1604 (build zero) libraries for MSVC 2013)

I should say to thank you again for your great support.

I have not any problem with W7.

But after a while, I have realized that my application cannot run in XP. (I have a few. I advise them to upgrade it at least W7)

When I run in XP, it gives an error code like It happen in MSVC 2015 again. I am sure I copied the old libs and dlls.

Can we solve this?

Thanks.

[TimStone]

I also have clients who use XP and they face many problems now with many programs plus major security breaches. For those people, and other older OS users, I have my application built in xHarbour ( .com version ). I would not provide those people with anything but a 32 bit solution.

My exact same source code builds just fine with FWH / Harbour / MSVC 2015. You should know that 2015 was not just a minor upgrade. The C++ standards have been upgraded. In fact, it is still one of the strongest, most used, languages today by everyone. The 2015 Visual Studio includes all of the upgrades for those new standards. If your clients want the best, they need to upgrade. Those using Windows 7 have a few weeks left to upgrade to Windows 10 for FREE. All of my clients who have done the upgrade are very happy and have no problems.

Again, my application code is the same source for both the xHarbour build and the MSVC 2015 build. The libraries are different in FWH, but you have both. Both are 100% working. I would consider this option with your clients. It's a lot of extra work for Antonio to try and build those MSFT libs with 2013. In his case, he has had problems with both 2013 and 2015 installed on the same machine.

[Enrico Maria Giordano]

The C++ standards have been upgraded. In fact, it is still one of the strongest, most used, languages today by everyone.

Probably you are confusing C and C++. I agree that C is still one of the most used languages but C++ is becoming less and less used because of its extreme complexity.

EMG

[TimStone]

http://www.tiobe.com/tiobe_index?page=index

C, C++, and C# rank 2, 3, and 4. Java ranks 1st.

You might also like to read this:

https://msdn.microsoft.com/en-us/library/hh409293.aspx

Clearly, the C language as a whole, and its derivatives, C++ and C#, are not dying, and VS 2015 updated C++ beyond the standards used in 2013, which was exactly my point.

I shared this because I had encountered these articles, and several others.

[Antonio Linares]

Hakan,

When I run in XP, it gives an error code like It happen in MSVC 2015 again. I am sure I copied the old libs and dlls.

Can we solve this?

What error is it ? Please provide us a screenshot and a way to reproduce the error, thanks