Author Topic: B2: Windows, C++ standalone project fails to build  (Read 460 times)

jporkkahtc

  • Senior Community Member
  • Posts: 1330
  • Hero Points: 97
  • Text
B2: Windows, C++ standalone project fails to build
« on: October 06, 2015, 08:13:24 pm »
I've got VisualStudio 2013 installed.
When I have no workspace open in VS I created a new C++ file.
When I build it fails because it cannot find "cl.exe"

How is "cl.exe" supposed to be in the path for Slick to find it?
When I installed VS2013 it didn't add CL to the path.


C:\Users\joe\Documents\Projects\Problems>"C:\Program Files\SlickEdit Pro 20.0.0 Beta2\win\vsbuild" -signal 60419 -command cl /c /Zi /Od  /Fo"C:\Users\joe\Documents\Projects\Problems\Debug\\" /Fd"C:\Users\joe\Documents\Projects\Problems\Debug\File1.pdb" @"C:\Users\joe\Documents\Projects\Problems\File1.cpp"  /nologo
 VSLICKERRORPATH="C:\Users\joe\Documents\Projects\Problems"

vsbuild: File not found (cl)

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1948
  • Hero Points: 81
Re: B2: Windows, C++ standalone project fails to build
« Reply #1 on: October 06, 2015, 08:14:47 pm »
Could you launch SlickEdit from a Visual Studio command prompt?

jporkkahtc

  • Senior Community Member
  • Posts: 1330
  • Hero Points: 97
  • Text
Re: B2: Windows, C++ standalone project fails to build
« Reply #2 on: October 06, 2015, 08:20:50 pm »
Yes, that works, but of course that isn't how I normally start Slick.


Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 3839
  • Hero Points: 251
Re: B2: Windows, C++ standalone project fails to build
« Reply #3 on: October 06, 2015, 09:25:22 pm »
For single file Visual Studio projects, SlickEdit does not attempt to muck with the PATH and other environment variables. This might get changed though.