It would be great to have [readanysf~] maintained in the CVS. Then I
could do the MacOS X porting and maintain it as part of the MacOS X
packages, as well as any other packages for platforms that [readanysf~]
runs on.
.hc
On Jul 16, 2004, at 11:16 AM, august wrote:
as you said August the Nick's binary is dynamically linked to all the libs, so to works, we have to put all the libraries in the good
places. I didn't want to do that, so I tried to recompile it with just flext and libsamplerate but without success.the problem was some missing defines in the main.cpp. if you download
it again, you should be able to compile without the mad, vorbis or flac
libs....
After that I finally decided to install the Nick's binary and all the libs at the good place for the binary, and it works well!
good to hear.
About the proper way on a Mac to distribute a binary, I think it's to built it with all the libs included in it. That's because on os X there's no standard place to put the libs. It depends if you use fink or darwinport or build it by hand. The other way is to distribute a package that will install the binary plus all the libs at the good places.
I think the later is the way to go. If you compile all the libs statically, then the binary will be well over 2 or 3 megs (I'm
guessing). And, you'd have to load that every time you add a readanysf~ object in
pd. that will add up after a while. Same with flext externals. they
should link to flext dynamically where possible. this will cut down down on
RAM usage.-august.
PD-list mailing list PD-list@iem.at to manage your subscription (including un-subscription) see http://iem.at/cgi-bin/mailman/listinfo/pd-list
Man has survived hitherto because he was too ignorant to know how to
realize his wishes.
Now that he can realize them, he must either change them, or perish.
-William Carlos Williams