Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You probably mean include paths and library paths in the compiler: </p> <ul> <li>include paths: where the compiler will look for headers; and</li> <li>library paths: where the linker, invoked by the compiler, will look for binary libraries to finish building your project.</li> </ul> <p>If that is the case, look <a href="http://www.network-theory.co.uk/docs/gccintro/gccintro_21.html" rel="nofollow">here</a> for a gentle explanation. Basically, what is happening is that the compiler looks in certain places for symbols defined by the operating system and other libraries installed system-wide. In addition to those paths, you need to tell the compiler where to find the symbols defined in your own project.</p> <p>You may also mean something related to installing the compiler itself or configuring the editor to use it. In that case, what is happening is that you need to tell the build system where to find the executable for the compiler. </p> <p>Basically, what is probably happening is that your editor wants to know where the compiler is so that it can provide real time feedback on your code. Adding the compiler to the system path will usually, but not always, solve your problem.</p> <p>In more detail: A C++ build is a rather complex tool chain, involving determining dependencies, preprocessing, compiling, and linking. There are tools that automate that tool chain, and those tools are in turn wrapped into the functionality of modern IDEs like Eclipse, Visual C++, or Sublime Text 2. You many need to tell your editor where to find the tools it uses to provide you with those services. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload