[PD] building all external on linux
hans at eds.org
Tue Apr 12 01:37:34 CEST 2005
Yes, the documentation is lacking. I updated externals/build/README
and externals/build/TODO. Hopefully it'll be more helpful now. Here's
how to add externals that use libs (from README), for example:
Externals That Need Libraries
In order to add an external that needs libraries to this build system,
a "libs" file with the exact same name as the source file (i.e.
oggread~.libs). If the .libs file has cross-platforms library options,
should go into externals/build/src. .libs files for platform-specific
options go in externals/build/PLATFORM (see TODO, this isn't totally
On Apr 11, 2005, at 5:56 PM, cyrille wrote:
> Hans-Christoph Steiner wrote:
>>> thanks hans! it works now. but, i was wondering about a thing. why is
>>> zexy.pd_linux not in /build/linux? or pmpd? what other externals are
>> Those have their own build system. No one has added them to the
>> externals/build setup. Ideally everything would be built there...
> yes, they have there own build system and it's not really a good point.
> they really should be in the external build system : it is so
> i had a look at the build system, and i don't really understand how
> does it work. specially to link all .c file to the /src folder.
> the readme says "In order to be platform independent this is done via
> c-includes." (?)
> is there some more documentation somwhere to explain how to add stuff
> to the build system?
>> __ ____
>> "I have the audacity to believe that peoples everywhere can have
>> three meals a day for their bodies, education and culture for their
>> minds, and dignity, equality and freedom for their spirits."
>> - Martin Luther King, Jr.
>> PD-list at iem.at mailing list
>> UNSUBSCRIBE and account-management ->
Using ReBirth is like trying to play an 808 with a long stick.
More information about the Pd-list