David Merrill wrote:
Hello all,
hi.
i am redirecting this to pd-dev, since i hope this mail will lead to
some further dev-specific discussion and hopefully to some usable build
system.
Has anyone else had a problem trying to compile an external from the CVS
source? I just checked out
Hallo,
Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
But yet again, it seems to me a massive waste of time to build Yet
Another Build System. How about instead making the existing one
better?
I agree with that, and I see IOhannes' and Thomas' wish for being able
On Aug 9, 2006, at 4:57 PM, Frank Barknecht wrote:
Hallo,
Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
But yet again, it seems to me a massive waste of time to build Yet
Another Build System. How about instead making the existing one
better?
I agree with that, and I
On 8/9/06, Frank Barknecht [EMAIL PROTECTED] wrote:
What I mean is: Maybe there is a way to make the makefiles in thevarious subdirectories also handle small builds? I don't reallyunderstand how it currently works, but for example a single externallike hid.pd_linux
has to be built anyways. So if
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
Hi all,
there is some weirdness happening when VASP is being loaded as -lib
(ok, perhaps I shouldn't do such things) and [plugin~] is being used.
The combination results in a segfault. I had exactly the same issue
with [pool] a while back (and it was in fact pointed out to me that I
should
