Re: resolving linker errors
- From: "Igor Tandetnik" <itandetnik@xxxxxxxx>
- Date: Sat, 8 Mar 2008 22:02:18 -0500
<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. 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.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925
.
- Follow-Ups:
- Re: resolving linker errors
- From: Norbert Unterberg
- Re: resolving linker errors
- References:
- resolving linker errors
- From: pauldepstein
- Re: resolving linker errors
- From: Norbert Unterberg
- Re: resolving linker errors
- From: pauldepstein
- resolving linker errors
- Prev by Date: Re: resolving linker errors
- Next by Date: Re: Properties tabs of .EXE file
- Previous by thread: Re: resolving linker errors
- Next by thread: Re: resolving linker errors
- Index(es):
Relevant Pages
|
Loading