[Scons-users] Need clarifications about --implicit-deps-unchanged

[William Blevins]

Addendum. Plus, the purpose of doing a clean build like that is
correctness, so using the option there even if the database existed would
not supportthat criteria under any case where the checkout points were not
identical.

On Dec 16, 2016 11:44 AM, "William Blevins" <wblevins001 at gmail.com> wrote:

> Consider how the option works. SCons uses previously stored information in
> .sconsdblite (name check) rather than getting dependencies implicitly from
> the source. If you are starting from scratch then that dependency
> information will not exist. I don't know if SCons errors in this case or
> just ignores the argument but this is not an appropriate use case.
>
> On Dec 16, 2016 9:12 AM, "Pierre-Luc Boily" <pierreluc.boily at gmail.com>
> wrote:
>
>> Thx!
>>
>> One last question.  In our build server where release is created, the same
>> process is always executed :
>> 1 - Delete previous check out
>> 2 - svn co last revision
>> 3 - make
>>
>> For our build server, since it is always a one shot deal, does that make
>> sense there to use --implicit-deps-unchanged to speed up compilation?
>>
>> thx
>>
>>
>>
>> --
>> View this message in context: http://scons.1086193.n5.nabble
>> .com/Need-clarifications-about-implicit-deps-unchanged-tp40840p40848.html
>> Sent from the Users mailing list archive at Nabble.com.
>> _______________________________________________
>> Scons-users mailing list
>> Scons-users at scons.org
>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20161216/e6780520/attachment.html>