lmao Yeah, I guess that is kind of vague.
Here's what I want the paths to be, if I'm trying to do this correctly:
C Compiler: D:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\cl.exe
C++ Compiler: D:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\cl.exe
Link for Dynamic Libs: D:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\link.exe
Link for Static Libs: D:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\link.exe
Resource Compiler: D:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\RC.exe
Make Program: D:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\nmake.exe
So, I have two directories, D:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\ and D:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\.
Auto-detect sets the compiler path to D:\Program Files (x86)\Microsoft Visual Studio 10.0\VC, but with the Microsoft SDKs path set appropriately for RC.exe, CB seems to change the working directory to check for the other tools to that path as well, even with it typed into the "additional directories" field.
The underlying problem that I'm trying to solve is a simple "Hello World" console program will not run unless I start the debugger. edit: And in fact, the executable is not made, even with CB run as an administrator. I suspect the libraries are correct since it runs under the debugger, which is what made me suspect the toolchain. This is not installed to the default "Program Files", as my OS runs on a SSD. Only vital stuff is on the system drive.
Here's the code for that.
\\ main.cpp
#include <iostream>
int main()
{
std::cout << "Hello world!" << "\n";
int waiter;
std::cin >> waiter;
return 0;
}
I figured that I must have my tools set up incorrectly. My idea that the working directory checked for each tool changes comes from what happens when I click the browse button. I'd expect it to show the path currently used for the file, but it shows the last path I browsed to. I may be misinterpreting that, come to think of it.
