Well, I am in the process of working with Nando, the PlanetCCRMA creator.  We are building the new PlanetCCRMA Pd packages directly from the Pd-extended build system.  So far its mostly working pretty well.  I think this model would work well for the debian packages.

You can already easily redirect every library's install target using $(DESTDIR) and $(prefix) per the GNU standards.  So the Debian build could just do something like:

make DESTDIR=/path/to/build/zexy prefix=/usr zexy_install

make DESTDIR=/path/to/build/pdp prefix=/usr pdp_install

make DESTDIR=/path/to/build/pidip prefix=/usr pidip_install

make DESTDIR=/path/to/build/maxlib prefix=/usr maxlib_install

etc. etc. Then each lib will be built as a distinct Debian package.

.hc

On Aug 9, 2006, at 6:14 PM, David Merrill wrote:

Agreed - thanks for the clarification HC - I didn't understand the build process either.

now.. what would be *really* nice would be if fresh versions all of the externals could be "apt-gotten" with apt-get (I guess this would be linux-only).. It's become quite convenient on Ubuntu to type:

apt-get update
apt-get install puredata pd-zexy

..and have it all just work. :) Anyone know if this is easy to set up?

-David M.

On 8/9/06, Frank Barknecht <fbar@footils.org> wrote:
Hallo,
Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:

> In reality, in order to build the externals
> with the Pd-extended build system, you need:
>
> externals/
> pd/
> packages/Makefile.buildlayout
>
> That doesn't seem like much of a burden to me.

Thanks for clarifying this. I agree that this isn't much of a burden.

Ciao
--
Frank Barknecht                 _ ______footils.org_ __goto10.org__

_______________________________________________
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