Thank you for posting very useful information.
I tried to compile one simple ProToolkit application for 64 bit configuration using steps described in the document.
The project setting works well for Win32 configuration but fails for x64.
I am using WF 3.0 and visual studio 2005 on a 32 bit machine and getting errors for ProToolkit functions while linking.
main.obj : error LNK2001: unresolved external symbol ProMdlRetrieve
Are different protk_dllmd.lib, prodev_dllmd.lib needed for 64 bit machines?
In Reply to Patrick Williams:
Having trouble setting up Visual Studio to compile your 64 bit Pro/TOOLKIT applications? This document will get you started.
Patrick Williams | Sr. Application Engineer | Engineering Systems | Steelcase Inc. | 616.698.4078
> Are different protk_dllmd.lib, prodev_dllmd.lib needed for 64 bit machines?
While you can build 64bit applications on 32bit systems, you will need the
64bit versions of the Pro/Toolkit .lib files to do this. These files can be
obtained by going through the install process of 64bit Pro/E. You are probably
using the 32bit .lib files which cannot be used to build 64bit applications.
Unfortunately for WF3 and WF4 installs, PTC did not provide a way to install
64bit Pro/E (or any of its components) on a 32bit system. They seem to have
forgotten that multi-architecture Pro/E installs have had built-in support for
about two decades.
Anyway, by copying setup.exe and the dsrc\i486_nt\obj folder from a 32bit install
disk image into all disks of the 64bit install disk image, you can install 64bit
Pro/E on a 32bit system. For your application, you only need the Pro/Toolkit stuff,
but you will need a 64bit install for testing sooner or later.