Paul Wise wrote:
Ok, put SCONS=scons in top of the file and changed all the $(MAKE) to $(SCONS)On Sun, Mar 8, 2009 at 9:36 AM, Daniel Moerner <dmoerner@gmail.com> wrote:In general, it's pretty similar to a normal make setup. Instead of calling $(MAKE), just define SCONS (e.g., SCONS = scons, at the top of the file) and then call $(SCONS). The upstream SConstruct file should support DESTDIR setting when you call $(SCONS) install.
Most of the time you'll have to implement DESTDIR support yourself (or convince upstream to switch to autotools or something that does DESTDIR out of the box). Check the packages in the scons reverse build-deps for examples: sudo apt-get install devscripts ; build-rdeps scons
Sorry, but how can I check it? Where can I find the rules files?
Be aware that due to the way scons works, "scons -c" will not work if the SConstruct file cannot initialize itself. That is to say, if "scons" does not work without patching the makefile, then to allow the package to build properly, you will either have to (a) manually replicate the purpose of scons clean in the clean: target of debian/rules, or (b) force the clean target to depend on the patch target, e.g.:
This is the clean entry: clean: dh_testdir dh_testroot rm -f build-stamp configure-stamp # Add here commands to clean up after the build process. $(SCONS) clean dh_clean How should I change it? I do get this now: fakeroot debian/rules clean dh_testdir dh_testroot rm -f build-stamp configure-stamp # Add here commands to clean up after the build process. scons clean scons: Reading SConscript files ... scons: done reading SConscript files. scons: Building targets ... scons: *** Do not know how to make target `clean'. Stop. scons: building terminated because of errors. make: *** [clean] Fout 2dpkg-buildpackage: failure: fakeroot debian/rules clean gave error exit status 2
\r