Re: resolving linker errors
- From: nathan@xxxxxxxx (Nathan Mates)
- Date: Sun, 09 Mar 2008 23:40:19 -0000
In article <e72aD2bgIHA.3780@xxxxxxxxxxxxxxxxxxxx>,
Norbert Unterberg <nunterberg@xxxxxxxxxxxxxxxxx> wrote:
Therefore, what are the practical reasons (if any) to add the
included .h files to the solution so that they are visible in
solution explorer?
Purely convenience in locating and opening them. You can remove them
from the solution, and the project would still compile.
It would still compile, but maybe not compile "enough". Putting the
header files into the solution puts them under control of the
IDE. That means they are checked out of source control when you
modify them, and the make process will monitro changes on the files
and automatically recompile all dependend source files.
Nope. Go edit <windows.h> or <vector> (just put a blank line at the
end), and hit build. Rebuild city. As above, C/C++ header files in
your DevStudio "solution" (I still gotta do the work, it's not a
solution) explorer window is a convenience, but doesn't affect actual
compilation.
Nathan Mates
--
<*> Nathan Mates - personal webpage http://www.visi.com/~nathan/
# Programmer at Pandemic Studios -- http://www.pandemicstudios.com/
# NOT speaking for Pandemic Studios. "Care not what the neighbors
# think. What are the facts, and to how many decimal places?" -R.A. Heinlein
.
- References:
- resolving linker errors
- From: pauldepstein
- Re: resolving linker errors
- From: pauldepstein
- Re: resolving linker errors
- From: Igor Tandetnik
- Re: resolving linker errors
- From: Norbert Unterberg
- resolving linker errors
- Prev by Date: Re: static library linking.
- Next by Date: Re: asm and x64
- Previous by thread: Re: resolving linker errors
- Next by thread: Video Training Library
- Index(es):
Relevant Pages
|
