Andy Farnell a écrit :
Cheers Pat,
On Sun, 20 Jan 2008 17:33:02 +0100 Patrice Colet pat@mamalala.org wrote:
Hi andy, I usually build the last vanilla test package,
Okay, use Millers source, I will do that.
and use cvs for externals,abstractions,and extensions.
Also if you don't use to compile with linux, use have to install the tools for compiling, like autoconf, automake, gcc, g++, libc, alsa-devel, jack-devel, don't forget to put --enable-jack --enable--alsa at ./configure. The externals dependances will come in doc files or errors during compilation.
I've got most the libs and gcc installed already, no worries with compiling on 64 generally, I tried a couple of other things already. What confuses me is the structure of pd-ext which I am not familiar with.
For example I just want to compile one external and it doesn't have a makefile or configure.. and I don't know what flags to set.... anyway I will read the docs you gave.
if you want to build pd-extended, you might want look at this:
http://puredata.info/docs/developer/GettingPdSource/?searchterm=rsync
I dunno about gridflow (often changing) and flext (the complete install is not easy, I suspect flext isn't ready for 64bit distro), but Gem is easy to build from it's cvs:
Not really bothered about GEM or gridflow, I just want a properly working vanilla with a few essential externals like [fdn~], [ead~], [delta~], [moog~] etc, which I hopeto build myself.
if you have downloaded externals, you can go to externals folder with the console and type 'make creb'. It will build a bunch of externals that will contain [fdn~] and [ead~], 'make ggee' should build [moog~], and 'make cxc' for [delta~]