after doing a make in /build/linux from a cvs (cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/pure-data co externals) i got this error after the compilation of m2f~.c
rm -f "m2f~.o" make: *** No rule to make target `makefile.common', needed by `all'. Stop.
patrick
On Tue, May 10, 2005 at 02:45:46AM -0400, patrick wrote:
after doing a make in /build/linux from a cvs (cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/pure-data co externals) i got this error after the compilation of m2f~.c
rm -f "m2f~.o" make: *** No rule to make target `makefile.common', needed by `all'. Stop.
the old build system is buggy (how do you build libraries? why is it hardcoded to use obsolete headers? why does it copy the help files twice?, why does it need makefile.common? why is there dozens of random things hacked into the 'make install' which often cause install to fail?), fortunately there is an alternative you might want to try:
cd /externals/build/ and type 'scons'
patrick
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
oups... i have one more question:
not all externals are copied in /externals/build/, some like pmpd, zexy are on the src/zexy/pmpd folder. it bother me a little, because what i like to do is to add simply external/build in the pd path setting. is there a script to take all .pd_linux in build? (maybe a simple bash? hum...)
patrick
On Mon, May 09, 2005 at 09:48:51PM -0400, patrick wrote:
oups... i have one more question:
not all externals are copied in /externals/build/, some like pmpd, zexy are on the src/zexy/pmpd folder. it bother me a little, because what i like to do is to add simply external/build in the pd path setting. is there a script to take all .pd_linux in build? (maybe a simple bash? hum...)
there seperate SConscripts for many libraries which are more complicated than single C files ( but i only added the ones i use...what is missing?). the binaries are added to the install queue, 'scons install' will move everything to the install location (you can adjust the 'prefix' variable from the cmdline to your own custom externals folder...)
patrick
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
On Tue, 10 May 2005, cr wrote:
On Tue, May 10, 2005 at 02:45:46AM -0400, patrick wrote:
after doing a make in /build/linux from a cvs (cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/pure-data co externals) i got this error after the compilation of m2f~.c
rm -f "m2f~.o" make: *** No rule to make target `makefile.common', needed by `all'. Stop.
the old build system is buggy (how do you build libraries? why is it hardcoded to use obsolete headers? why does it copy the help files twice?, why does it need makefile.common? why is there dozens of random things hacked into the 'make install' which often cause install to fail?), fortunately there is an alternative you might want to try:
cd /externals/build/ and type 'scons'
I think scons is really nice, but it won't save us from the problem of not having a standardized way of building externals. Because of this, when you stop maintaining the system it will break down.
The old system was designed to automatically compile new additions. I think the goal of a new system should be to allow this.
I would like to help with this, unfortunateley I can't find the time to do so anymore. This makes me think that I should officially step back from being the maintainer of the pd CVS on sourceforge, I hope the one taking over will be more successful.
Guenter
patrick
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
-
cr -
g�nter geiger -
ix＠replic.net
-
patrick