[Scons-users] Going from SCons 2.5.1 to SCons 3.0.1

[Bill Deegan]

Yes. The safest thing would be to do a full clean with 2.5.1, remove the
sconsign, and then build with 3.0.1

Unless you are using 3.0.1 with py3 you should not have to change your
SConstructs/SConscripts.
Unless.. you have created your own node types or mucked around with more
internal API calls.

-Bill

On Wed, Apr 25, 2018 at 5:59 AM, Pierre-Luc Boily <pierreluc.boily at gmail.com
> wrote:

> Hello,
>
> I know this has been answer before, but I can`t find the thread.  We are
> about to migrate from 2.5.1 to 3.0.1 and in order to make this less painful
> as possible for developers I need to know what needs to be done prior to
> re-launch the build.  Is the only file need to be remove is the
> .sconsign.dblite file, or do we need to go through a full clean before
> updating SCons?
>
> Thx
>
>
>
> --
> Sent from: http://scons.1086193.n5.nabble.com/Users-f16930.html
> _______________________________________________
> 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/20180425/d175007a/attachment.html>