FWH / Harbour with MS VC++ 2013

[bradmaudlin]

Hi,

I have been using FW for Harbour/xHarbour with BCC5.8.2 C++ for years... I thought I would try compiling some of the samples (C:\FWH\Samples\) using Microsoft C++ compilier instead of Embarcadero.
I am using buildh32.bat and get a lot of warnings and errors.

First, I am currently using FWH 15.01 32bit and Harbour 3.2.0.
Will both of these work with the Microsoft C++ compilier?? If I look at the .c code generated it says Borland C++ 5.8.2 (32-bit) at the top of it.
/*
* Harbour 3.2.0dev (r1501292255)
* Borland C++ 5.8.2 (32-bit)
* Generated C source from "graph.prg"
*/


Do I need FW and Harbour .lib's built for microsoft??

I also tried setting it up in as a project in "Visual Studios 2013" and get the exact same errors.

Thanks,

Brad.

[TimStone]

First, with FWH 16.03 and beyond, all MSVC files are built with Visual Studio 2015 Community edition, which is free to you from Microsoft. There were some significant changes made to the C compiler with this version.

Antonio has provided a set of libs with the latest Harbour release that you can use to build your programs. For the past few months, there are several articles on the forum about the issues that arose, and I think as of today, they have all been resolved. I now have a fully functioning, very large, application running without any ( found ) flaws at this time using FWH 16.03, Harbour 3.2 ( 32 bit ), MSVC 2015.

If you want to build using Visual Studio 2013, you will need to use the libs in FWH 16.02 or before, and yes, you do need to use Microsoft built Harbour files.

Tim

[bradmaudlin]

Thanks for your quick reply, and I have been following your posts on using Visual Studios 2015 (that's what made me think about switching).
I think I might upgrade FW to 16.?? and VS 2015 Community and try again.

Any Pro's or Con's in using MSVC 2015 compared to BCC5.8.2?
Does the Resource Editor work OK?

Thanks again for your time,

Brad

[Antonio Linares]

Brad,

You need FWH 16.03 and VSC2015 (Visual Studio community)

They work very fine together, in both 32 and 64 bits.