FiveTech Support Forums

Tim,

Not sure what you mean exactly, but if you mean that you are going to migrate from VS2012 to VS2013 all you have to change is this:

1. Let Visual Studio initialize its own settings:

if exist "%ProgramFiles%\Microsoft Visual Studio 12.0\VC\vcvarsall.bat" call "%ProgramFiles%\Microsoft Visual Studio 12.0\VC\vcvarsall.bat" x86_amd64
if exist "%ProgramFiles(x86)%\Microsoft Visual Studio 12.0\VC\vcvarsall.bat" call "%ProgramFiles(x86)%\Microsoft Visual Studio 12.0\VC\vcvarsall.bat" x86_amd64

1. In the make file, just change these two lines:

VCDIR="c:\Program Files (x86)\Microsoft Visual Studio 12.0\VC"
SDKDIR="c:\Program Files (x86)\Windows Kits\8.1"

thats all

Tim,

You can generate a 32-bit application with "VS +FWH + ​​xHarbour"? How do I do that?

Thanks,

Antonio,

Currently I have a build using UltraEdit Studio, FWH, Harbour, and the files from VC++ 2012. The UEStudio make file works perfectly, and in it, I have the proper lib files called out.

Now, I am setting aside UE Studio, and building the program in Visual Studio 2013 Professional, just like you are doing with the 64 bit, except I am using 32 bit files. I am following your steps outlined elsewhere to start a project, and add the .prg files. I am adding all the .prg files that I used successfully in the UEStudio and VC 2012 build. I modify the properties for each and they are compiling with harbor to .c files as they should.

You also indicated we need to add the .lib files, and I understand how to do that. I used the same .lib files from my UE Studio build ( special, harbor, and fwh .libs ).

My question is this. In UE Studio, I needed to specify the Visual Studio libs also. Do I need to add those in the Visual Studio project, or will VS find them on its own ?

Thanks.

Tim,

Visual Studio will find them. Here you can see the libs that you just need to link:

viewtopic.php?p=144626#p144626

and here is the topic where it is explained how to build FWH apps from Visual Studio IDE:

viewtopic.php?f=3t=26298start=0

Antonio,

I have more Harbour libs and some externals. I think I have that under control.

I have a lot of .prg files and of course each one needs to have the properties set, so that takes a long time. I decided to see what would happen if I did a Build. Of course, each .prg compiles fine with Harbour into a .c file.

When VS 2013 tries to compile the .c programs, it gives the following error:

1>c:\users\timsaio\documents\visual studio 2013\projects\mls2015\mls2015\pro3900.c : fatal error C1853: 'Debug\MLS2015.pch' precompiled header file is from a previous version of the compiler, or the precompiled header is C++ and you are using it from C (or vice versa)
pro3800.c

What is the "precompiled header file" to which this is referring ? I did not add any. I'm using the latest libs from FWH, but my Harbour files are older. They were a set you sent me dated 4/4/13. However, I don't think those apply since it was not trying to link libraries.

Tim

Where is that screen ? I can't seem to find it.

Sorry...I should have posted that I found the setting earlier. No have about 30 more files to setup and them nit will be time to link.

Sent from my iPad using Tapatalk HD

Tim,

No doubt that you could find it. You are a great master, more and more, and I feel so fine about that, because I still remember sometimes that I told you (remember it?) to use VB (like a zen master would have told you, to make you understand) but you choosed the right tools and you have been brave enough to use Visual Studio, to decide your own tools and I feel proud of having masters like you in these forums

Tim,

1. You have a typo in the library name: Its correct name is msimg32.lib

1. You have to link OleDlg.lib too from Microsoft

and version.lib