[Numpy-discussion] Partially merging scons into trunk ?
Mon Oct 15 12:08:52 CDT 2007
I've only been following this thread on the perimeter, so I'm not sure
if "makefile" migration has been discussed. I have a script I wrote
about a year ago when we (Enthought) were looking at using SCons for our
internal builds. The script is capable of generating SConscript files
from setup.py scripts. It works by faking a build with distutils and
uses those build steps to generate the scons targets.
The script is not complete, for example 'weave' confuses it, but it
could be a good starting point. If anyone is interested in it, I'll post
it to the list.
David Cournapeau wrote:
> Following the previous thread on using scons within distutils in
> numpy, I would like to know if it is ok to merge some of the code from
> numpy.scons branch into the trunk ? I don't want to merge everything,
> just the part which has little chance to break anything (basically up to
> rev 4178 in numpy.scons branch; the code has been sucessfully tested on
> most major platforms). The only downside I can see is that it adds ~ 1
> Mb of code into numpy because I included a local copy on scons.
> Numpy-discussion mailing list
More information about the Numpy-discussion