Re: resolving linker errors
- From: Norbert Unterberg <nunterberg@xxxxxxxxxxxxxxxxx>
- Date: Sun, 09 Mar 2008 09:13:45 +0100
Igor Tandetnik schrieb:
<pauldepstein@xxxxxxx> wrote in message
news:08f88d7a-93b6-41c1-a846-5c46db359e81@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
The #include
"somefile.h" statements already tell the compiler to compile the
necessary h files. 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.
As far as I know, only files that are part of the workspace are included in the build dependency tree. If you do not add the headers, changes in these headers might not cause the moduels using the header to be recompiled.
Norbert
In fact, your project likely uses lots of .h files that are not listed in the Solution Explorer - standard library headers, Windows headers, perhaps third-party libraries..
- Follow-Ups:
- Re: resolving linker errors
- From: Nathan Mates
- Re: resolving linker errors
- References:
- resolving linker errors
- From: pauldepstein
- Re: resolving linker errors
- From: Norbert Unterberg
- Re: resolving linker errors
- From: pauldepstein
- Re: resolving linker errors
- From: Igor Tandetnik
- resolving linker errors
- Prev by Date: Re: iterator for deque
- Next by Date: Re: anti-standard code can compile -- about template class
- Previous by thread: Re: resolving linker errors
- Next by thread: Re: resolving linker errors
- Index(es):
Relevant Pages
|