# For debugging, change LIBS = $(RELEASE) to $(DEBUG) # To compile sample programs on Windows, type: nmake /f nMakefile I just tried to use the vix.lib directly, it works, to do that, I changed the nMakefile64bit as following: The error happen when the linker try to find VC CRT internal function vacopy, it may caused by your dev environment. I don't want to have to resort to invoking "vmrun.exe" rather than using the VIX API directory. Unfortunately, the working version in "Workstation" directory does not contain the import library to link against (vix.lib) and attempting to run my application using the DLLs in the "Workstation" directory doesn't work.Īny advice here would be appreciated. It is clear that the version of VIX (and associated libraries) used by "vmrun" in the "Workstation" directory (which works) is different from the version in the "VMware VIX" directory that we are expected to build and run using. If I look at the corresponding matching files in the "VMware Workstation" directory (which I run vmrun.exe from and does work), I get: If I look at the files in the 32-bit "VMware VIX" directory (which I build/run my app against and doesn't work), I get:
However, the 32-bit "vmrun.exe" (in the "VMware Workstation" directory) powers it on correctly. My application builds happily against vix.lib in the "VMware VIX" directory of the VMware Workstation 15 installation, but when I attempt to power on the VM (using VIX API), I get "unknown error". OK, I've taken a further look into this and I still don't think the correct VIX is distributed.
0 kommentar(er)
