URL:
<http://gna.org/bugs/?20406>
Summary: scons --clean: creates then destroys
mypaintlib_wrap.cpp
Project: MyPaint
Submitted by: achadwick
Submitted on: Fri 04 Jan 2013 02:58:55 PM GMT
Severity: 2 - Minor
Priority: 5 - Normal
Status: Confirmed
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 1.1.0 17322aeb
Planned Release: None
Operating System:
_______________________________________________________
Details:
Confirmed by Sebastinas on OFTC during a debian packaging review. "scons -c"
in its simplest case (running on an already clean tree) regenerates
mypaintlib_wrap.cpp each time, only to destroy it later in the very same
command:
$ scons --clean
scons: Reading SConscript files ...
building for 'python2.7' (use scons python_binary=xxx to change)
using 'python2.7-config' (use scons python_config=xxx to change)
rm -f libmypaint-tests.so libmypaint.so libmypaintlib.so
python2.7 generate.py
Writing mypaint-brush-settings-gen.h
Writing brushsettings-gen.h
swig -Wall -o mypaintlib_wrap.cpp -noproxydel -python -c++ mypaintlib.i
rm -f _mypaintlib.so
set umask to 0022 (was 0002)
scons: done reading SConscript files.
scons: Cleaning targets ...
Removed brushlib/brushsettings-gen.h
Removed brushlib/mypaint-brush-settings-gen.h
Removed brushlib/brushsettings.pyc
Removed lib/mypaintlib_wrap.cpp
Removed lib/mypaintlib.py
scons: done cleaning targets.
The same is true when running on a built tree, of course.
This appears to serve no purpose. Is it possible to have scons -c not do this?
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?20406>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Mypaint-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/mypaint-bugs
