Hans,
Your lastest nightly snapshot is also missing flatspace (but at least it does build libdir,flib, and toxy). I've had to build libdir, flib, and toxy manually, so I guess there is a workaround for that (in other words the current svn build script simply ignores building those for whatever reason). But the absence of flatspace even in your nightly builds is baffling. Is this thing then deprecated in latest svn?
Ico
On Fri, 2010-12-03 at 13:54 -0500, Ivica Ico Bukvic wrote:
Hans,
Your lastest nightly snapshot is also missing flatspace (but at least it does build libdir,flib, and toxy). I've had to build libdir, flib, and toxy manually, so I guess there is a workaround for that (in other words the current svn build script simply ignores building those for whatever reason). But the absence of flatspace even in your nightly builds is baffling. Is this thing then deprecated in latest svn?
OK, found the source. externals/Makefile apparently omits these from being built, including loaders-libdir which has been apparently separated from the regular loaders thus making it impossible to load any of the libs. I suspect this is a omission by mistake.
However, flatspace, flib, and toxy are also omitted while some of its externals (here I speculate) have been assimilated into other packages. entry.pd_linux (from flatspace) is however missing. So are quite a few others.
On Dec 3, 2010, at 5:21 PM, Ivica Ico Bukvic wrote:
On Fri, 2010-12-03 at 13:54 -0500, Ivica Ico Bukvic wrote:
Hans,
Your lastest nightly snapshot is also missing flatspace (but at
least it does build libdir,flib, and toxy). I've had to build libdir, flib,
and toxy manually, so I guess there is a workaround for that (in other
words the current svn build script simply ignores building those for
whatever reason). But the absence of flatspace even in your nightly builds is baffling. Is this thing then deprecated in latest svn?OK, found the source. externals/Makefile apparently omits these from being built, including loaders-libdir which has been apparently separated from the regular loaders thus making it impossible to load
any of the libs. I suspect this is a omission by mistake.However, flatspace, flib, and toxy are also omitted while some of its externals (here I speculate) have been assimilated into other
packages. entry.pd_linux (from flatspace) is however missing. So are quite a few others.
Ok, the libdir loader should now be included in the builds:
http://pure-data.svn.sourceforge.net/viewvc/pure-data?view=revision&revi...
.hc
All mankind is of one author, and is one volume; when one man dies,
one chapter is not torn out of the book, but translated into a better
language; and every chapter must be so translated.... -John Donne
On Dec 3, 2010, at 1:54 PM, Ivica Ico Bukvic wrote:
Hans,
Your lastest nightly snapshot is also missing flatspace (but at
least it does build libdir,flib, and toxy). I've had to build libdir, flib, and toxy manually, so I guess there is a workaround for that (in other
words the current svn build script simply ignores building those for
whatever reason). But the absence of flatspace even in your nightly builds is baffling. Is this thing then deprecated in latest svn?
Hey Ico,
For the next release of Pd-extended, I'm trying to open up the process
of what gets included into Pd-extended and make sure there is a clear
maintainer for each library that's included. There are a number of
very old, obsolete libraries in there now, and I don't have the time
to maintain all of the libraries that are currently in Pd-extended.
Recently, we've put a lot of effort in making it easier to make,
distribute and install libraries, these are changes in Pd 0.43 and Pd-
extended 0.42. That means there is less pressure to put libraries
into Pd-extended. So I think its appropriate to make sure only really
stable (i.e. in bugs and in API) libraries should be included in Pd-
extended.
One last piece of this puzzle is that we've been working on getting
lots of libraries into Debian (and therefore Ubuntu, Mint, etc), so
I'm shifting my development focus there, and Pd-extended will be based
on what's in Debian.
This is definitely a moving target, and things are still taking shape,
but that's the general idea of what I'm thinking now. You can see
more here, and I'm going to try to get more organized on this topic too.
http://puredata.info/docs/developer/GettingIntoPdextended http://puredata.info/dev/NextRelease
.hc
'You people have such restrictive dress for women,’ she said, hobbling
away in three inch heels and panty hose to finish out another pink-
collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
Cool. Thanks for your reply.
So is it therefore safe to assume that flatspace, flib, and toxy are for all intents and purposes obsolete (at least for the time being)?
What about the absence of loaders-libdir? That seems like an erroneous omission since it is the very backbone of the lib loading?
Ico
On Dec 3, 2010, at 5:48 PM, Ivica Ico Bukvic wrote:
Cool. Thanks for your reply.
So is it therefore safe to assume that flatspace, flib, and toxy are
for all intents and purposes obsolete (at least for the time being)?
If anyone wants to maintain them, they can take them on. I personally
really think 'flatspace' should go away. flib and toxy are
interesting libraries, if anyone wants to be the maintainer of them.
I just can't do it all.
What about the absence of loaders-libdir? That seems like an erroneous omission since it is the very backbone of the lib loading?
fixed
.hc
There is no way to peace, peace is the way. -A.J. Muste
Cool. Thanks for your reply.
So is it therefore safe to assume that flatspace, flib, and toxy are for all intents and purposes obsolete (at least for the time being)?
If anyone wants to maintain them, they can take them on. I personally really think 'flatspace' should go away. flib and toxy are interesting libraries, if anyone wants to be the maintainer of them. I just can't do it all.
BTW, it seems to me that flatspace is simply a redundant collection of select externals from other libraries (with perhaps a few exceptions), no? That said, I just discovered that at least one of the pddp abstractions relies upon flatspace/prepend (e.g. print-to-canvas object inside pddp).
Ico
On Dec 4, 2010, at 10:50 AM, Ivica Ico Bukvic wrote:
Cool. Thanks for your reply.
So is it therefore safe to assume that flatspace, flib, and toxy are for all intents and purposes obsolete (at least for the time being)?
If anyone wants to maintain them, they can take them on. I
personally really think 'flatspace' should go away. flib and toxy are interesting libraries, if anyone wants to be the maintainer of them. I just can't do it all.BTW, it seems to me that flatspace is simply a redundant collection
of select externals from other libraries (with perhaps a few
exceptions), no? That said, I just discovered that at least one of
the pddp abstractions relies upon flatspace/prepend (e.g. print-to- canvas object inside pddp).
Fixed those. Yeah, flatspace is based on the idea of having a single
namespace with a managed collection of objects.
.hc
Computer science is no more related to the computer than astronomy is
related to the telescope. -Edsger Dykstra
-
Hans-Christoph Steiner -
Ivica Ico Bukvic