When I change a header file for a library, and then do a "make" in the
build directory, only source (C++) files which directly include that header
get rebuilt, but those which use it indirectly do not. But when I link to
the library, the other files do get rebuilt.
Example:
lib/mod.cpp
lib/mod2.
On 2014-12-08 12:53-0600 Chris Johnson wrote:
When I change a header file for a library, and then do a "make" in the
build directory, only source (C++) files which directly include that header
get rebuilt, but those which use it indirectly do not. But when I link to
the library, the other files
Thanks for the reply and good advice, Alan. Will do.
..chris
On Mon, Dec 8, 2014 at 2:58 PM, Alan W. Irwin
wrote:
> On 2014-12-08 12:53-0600 Chris Johnson wrote:
>
> When I change a header file for a library, and then do a "make" in the
>> build directory, only source (C++) files which direct
On 2014-12-08 12:53-0600 Chris Johnson wrote:
When I change a header file for a library, and then do a "make" in the
build directory, only source (C++) files which directly include that header
get rebuilt, but those which use it indirectly do not.
Hi Chris:
For one of my C projects (ephcom) I
On 12/8/2014 1:53 PM, Chris Johnson wrote:
When I change a header file for a library, and then do a "make" in the
build directory, only source (C++) files which directly include that
header get rebuilt, but those which use it indirectly do not. But when
I link to the library, the other files do
Well of course it had to not be all that simple. My first attempt to
create a simple (2 header files in library) example failed to fail in the
same way as my much more complex real-life project. :-p
I will continue to try to whittle down the real problem to the smallest
possible set, but it may
On 12/9/2014 9:45 AM, Chris Johnson wrote:
Well of course it had to not be all that simple. My first attempt to
create a simple (2 header files in library) example failed to fail in
the same way as my much more complex real-life project. :-p
I will continue to try to whittle down the real prob
That's the strange thing. All the dependencies in those files in the real
project look right. It's as if they are just not getting used during the
library compile, although they do get used when the program is linked to
the library and the "current-ness" of the library is checked before the
actua