We had this in VS2010 for 2012 but I am not sure about 2013. Basically what we did was to use our own MACROS or variable instead of the one from setenv.bat. All you need to do is take your project generated from the wizard , start visual studio normally with call to setenv.bat and make your own solution and in the properties set the paths for include and libs for XSI manually. That should not work. At least it did for us.

On 12/09/2012 1:40 PM, Julian Johnson wrote:
Just moving from VS2008 to VS2010 SP1 for 2013 SP1 and getting this compile error when trying to build any of the custom tools or ICE nodes (e.g. SnapTestTool/CustomPassThrough):

1>TRACKER : error TRK0002: Failed to execute command: ""C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\amd64\CL.exe" @C:\Users\Julian\AppData\Local\Temp\aa1a941ecf4d479fafe00df2f75cc872.rsp". The handle is invalid.

Has anyone seen this or have a solution?

Tried the workarounds here:
http://connect.microsoft.com/VisualStudio/feedback/details/505682/x64-c-c-projects-cannot-compile

But didn't seem to help.

Julian


-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2221 / Virus Database: 2437/5264 - Release Date: 09/12/12

Reply via email to