Back to 2395: My python expertise isn't 5 star, and I'm confused on how to propagate a "symlinks" argument down.
What I imagine my SConscript should do: env.InstallAs( a, b, symlinks=False ) Where the scons copy command exists: SCons.Tools.install.copyFunc There are so many wrapper layers I feel like I'm spinning in circles. I was able to follow it up until "src/engine/SCons/Action.py:1065" and then I get an argument count mismatch for installFunc. I'm worried about changing the Action.execute interface, so I'm not sure how to proceed. Any thoughts? On Sat, Jul 12, 2014 at 1:20 PM, William Blevins <[email protected]> wrote: > Added a pull request for that test. Please take a looksy. > > I noticed in the test documentation we were deprecating test.write in > favor of file copying; the writes for this test are very small and I didn't > see the need to refactor. Let me know if that is unacceptable. > > > On Sat, Jul 12, 2014 at 1:09 PM, William Blevins <[email protected]> > wrote: > >> [wblevins@localhost scons]$ ./runtest.py test/Java/DerivedSourceTest.py >>> 1/1 (100.00%) /usr/bin/python -tt test/Java/DerivedSourceTest.py >>> /home/wblevins/BitBucket/scons/src/script/scons.py returned 2 >>> STDOUT >>> ========================================================================= >>> scons: Reading SConscript files ... >>> scons: done reading SConscript files. >>> scons: Building targets ... >>> scons: building terminated because of errors. >>> >>> STDERR >>> ========================================================================= >>> scons: *** [.] ValueError : zero length field name in format >>> >>> >>> FAILED test of /home/wblevins/BitBucket/scons/src/script/scons.py >>> at line 598 of /home/wblevins/BitBucket/scons/QMTest/TestCommon.py >>> (_complete) >>> from line 701 of /home/wblevins/BitBucket/scons/QMTest/TestCommon.py >>> (run) >>> from line 390 of /home/wblevins/BitBucket/scons/QMTest/TestSCons.py >>> (run) >>> from line 95 of test/Java/DerivedSourceTest.py >>> >> >> After making the tool update which I assume is a work-around for a bug in >> the main trunk, I still got this error. I ran the system with python 2.7.X >> and it was fine. Based on the output, I believe this error happens because >> scons is printing the python warning banner to STDERR. It doesn't make >> much sense to fail a test due to the python version warning banner. Can we >> change this or make runtest check versions and fail before running the test? >> >> >> On Sat, Jul 12, 2014 at 12:43 PM, Dirk Bächle <[email protected]> wrote: >> >>> On 12.07.2014 18:28, William Blevins wrote: >>> >>> I run my test: >>> >>> >>>> STDERR >>>> ========================================================================= >>>> ValueError: zero length field name in format: >>>> File "/tmp/testcmd.12339.qe2sNH/SConstruct", line 4: >>>> env = Environment() >>>> >>> >>> Try to get around the D tool being used, with something like >>> >>> env = Environment(tools=['jar','javac']) >>> >>> >>> >>> And the scons call works just fine, so I am confused. Is it a RHEL6 >>> default python version issue? >>> >>> Possible, I can't say for sure. >>> >>> >>> >>> _______________________________________________ >>> Scons-dev mailing list >>> [email protected] >>> http://two.pairlist.net/mailman/listinfo/scons-dev >>> >>> >> >
_______________________________________________ Scons-dev mailing list [email protected] http://two.pairlist.net/mailman/listinfo/scons-dev
