ProE WildFire 4 and VC++ 2010 express edtion-configuration

I vauguely recall that the express edition can only compile and link a multi-threaded exe (or dll).
Single-threaded is required.

This is one of the reasons that I abandoned Pro/Toolkit and moved to J-Link.

Gerry Champoux
Williams International
Walled Lake, MI

In Reply to Shreeshail Lokhande:

Hello All,

I'm a newbie for proe customisation.I have been using "Proetoolkiy_GSG.pdf" file to run the "pt_install_test" application using Proe4 and VC++ 2010.I have followed all the steps given in the above mentioned pdf file.In VC++ 2010 I manged to configure my project platform to "x64" since I'm compling the files on 64-bit machine(Windows XP x64 OS).WhenI build the sample projectI can see all the".obj" files getting created,however my"pt_inst_test.dll" is not getting created instead I'm getting following errors.

1>LINK : fatal error LNK1181: cannot open input file 'bufferoverflowu.lib'

1>NMAKE : fatal error U1077: "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\x86_amd64\link.EXE" : return code '0x49d'

1> Stop.

1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.MakeFile.Targets(38,5): error MSB3073: The command "nmake /f make_install dll" exited with code 2.

========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

Patrick,

Thanks for the extra info. I had forgotten about the SDK until you mentioned it.
I now recall something else:
If you intend to compile for 64-bit PC's, you will also need the SDK for Windows 2003 R2 or possibly Windows 2008.
Thiese too are free from Microsoft.

Gerry

In Reply to Patrick Williams:

Shreeshail,
Let me bring some information to the discussion before I answer your question. The MS Visual Studio IDE (Professional or Express) is just a GUI with additional tools to aid the developer in his work. It is shipped with specific versions of the compiler (cl.exe), linker (link.exe), headers (.h), and libraries (.lib) that it uses to compile and link your application. In other words, the IDE and compiling/linking tools are SEPARATE!

Now, the express versions of the IDE's are shipped with different compiler, linker, headers, and libraries than the professional versions. Therefore (in my experience which sounds like it's not the same as Gerry's experience) you CANNOT EVER compile and link a Pro/TOOLKIT application with the express versions of the IDE's as they are shipped and delivered.

Why is that?

When you download the compatibility matrix for Pro/TOOLKIT you will see that WF 4.0 is compatible with MS Visual Studio 2005 Professional. What PTC is actually stating is that WF 4.0 is compatible with the compiler, linker, headers, and libraries that shipped with MS Visual Studio 2005, not the IDE itself. This is a good thing.

So do you have to spend the $$$ to purchase the professional version of MS Visual Studio 2005? NO! You can use the Express version.

Wait a minute...I just told you that you CANNOT EVER compile and link a Pro/TOOLKIT application with the express version. That's correct. However; there is something called the Windows SDK (formerly known as Platform SDK) which contains the compiler, linker, headers, and libraries that PTC certifies! Hooray!

By downloading and installing the correct SDK for WF 4.0 you can "point" MS Visual Studio Express at the SDK which will force it to use the SDK compiler, linker, headers, and libraries when compiling and linking your Pro/TOOLKIT application and voila! You now have a FREE environment for building Pro/TOOLKIT applications. This can be done for ALL versions of Wildfire. You just have to make sure your IDE is pointing to the correct SDK paths. That's the trick!

Patrick,

Patrick,

Thanks a lot for the reply.As told by you and Mark I happened to do following things :

1)First I installed VC++2005 Express Edition

1.1)My machine configuration is
64 bit machine
OS-Windows XPx64

1.2)Myproe(Wildfire 4)-along with toolkit installation is 64 bit.

2)It basically means I'm using VC++2005 express editionand try to compile 64 bit application

3)so I'm getting the following error

4)To tackle the above error I installed Windows 7.1 platform SDK

5)Now I go to configuration manager of VC++ 2005
and try to create new platform.But unfortunately I don't see 'x64' platform in the list.
(Note :I did samething but with VC++2010 and I can see 'x64' platform in the list but I get error which i told in my 1st post)

6)Here are the few excerpt from your reply
"By downloading and installing the correct SDK for WF 4.0 you can "point" MS Visual Studio Express at the SDK which will force it to use the SDK compiler, linker, headers, and libraries when compiling and linking your Pro/TOOLKIT application and voila! You now have a FREE environment for building Pro/TOOLKIT applications. This can be done for ALL versions of Wildfire. You just have to make sure your IDE is pointing to the correct SDK paths."

7)I guess my problem has something to do with the pointing VC++2005 to SDK,but I dont know how to do that....it would be great help for me if you can give me some meticulous steps of doing it....

Thanks in advance

P.S :My previous two replies with "Patrick," text only were sent by mistake ,please consider my sincere apologies for the same.

Patrick,

Thanks a lot for your reply.Yes I work in Whirlpool Corporation but in India...:) .I happened to follow each and every step you told in your previous reply.In SDK's start up command prompt I tried to execute devenv.exe,but since this file doesn't exist in the VC installation I got "devenv.exe file is not recognized as internal or external command" .I'm hanged up here. I tried to setup development environment on 32 bit machine and I was able to do it sucessfully, but 64 bit machine is really giving me trouble.If you know any work around for the above problem with respect to 64 bit machine please let me know. IfI buy Visual Studio 2005 ,will it promise me with sucessful environment setup for 64 bit machine ??