Now, assume thre are old foo.dll and libfoo.dll.a files around, but
foo.c has been edited. If Make would cache stat calls, it would not
have any reason to believe that libfoo.dll.a indeed got updated, too,
when foo.dll was produced by its recipe, would it? So it would run
the recipe once more.
GNU make needs to rebuild everything depending on a file, if that file
has been rebuild, regardless of timestamps. If any of the direct or
indirect dependencies of a file are newer it will be rebuild.
Hmm, but how is what you say related to the example I described? foo.c has been edited by the user,
not updated by a recipe run by Make.
If you are saying what I think you are saying, doing a "make clean && make foo.dll libfoo.dll.a" in
my example would have it run the recipe twice, once to update foo.dll and once to update
libfoo.dll.a. But it doesn't, it says "`libfoo.dll.a' is up to date".
Anyway, I don't know if this is directly related to the problem(s) at hand, so I will stop using
non-related examples now.
--tml
Context
- Re: [Libreoffice] a faster gnumake ? ... (continued)
Re: [Libreoffice] a faster gnumake ? ... · Lubos Lunak
Re: [Libreoffice] a faster gnumake ? ... · Tor Lillqvist
Re: [Libreoffice] a faster gnumake ? ... · Norbert Thiebaud
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.