Sorry for the newb question: How can I set up the environment variables for use within 4coder when I press alt+m to build? Before, I just called vcvarsall.bat x64 from a cmd window and alt-tabbed to that window from Visual Studio when I wanted compile. The cracks have begun to show in the VS editor so I am trying out the 4coder demo and so far it's great, except for this problem that I am having. I only have VS 2017 installed and compile for 64-bit. I have added cl.exe to the path, but now of course the compiler doesn't know where windows.h, user32.lib etc. is. Thanks.
Edited by stenton
on
Reason: Initial post
Launch 4coder from a terminal that ran vcvarsall.bat x64
or have the build script run vcvarsall.bat x64 itself.
The latter will be slow per build but you can speed it up by manually setting the env vars that vcvarsall.bat sets up. They are not going to change until you upgrade your VS install anyway.
or have the build script run vcvarsall.bat x64 itself.
The latter will be slow per build but you can speed it up by manually setting the env vars that vcvarsall.bat sets up. They are not going to change until you upgrade your VS install anyway.
You're not dumb! The VS compiler path initialization on the other hand...
Edited by Allen Webster
on