On Thu, 2007-09-13 at 07:30 +0200, Roman Haefeli wrote:
i tried to always call it 'pd-vanilla/externals', not just 'pd-vanilla', in order to make clear, that i am using pd-vanilla and compiling the externals myself. anyway, if i compile the externals how it is described in the README, that comes with the externals, and which i call the 'original way' to compile them, i get one library containing several objects, where namespaces don't work.
iemlib is a special case, because there is not only the inconsistency of having namespaces in pd-extended and not having them in 'pd-vanilla/externals', but also different names of libraries. in order to create a patch, that works on both, it's required to have a [declare] with the all these flags: -stdpath iemabs -stdpath iemlib -stdlib iemlib1 -stdlib iemlib2 -stdlib iem_t3_lib just to get iemlib working everywhere.
since [declare] doesn't output an error, when not finding a lib or a path, this can be handled this way, though it is a bit awkward.
yo, lets make it simple: shouldn't the one or the other be skipped in cvs? since the libdir is more widely used, i assume, and has also some advantages compared to the old standard (am i right here?), let's skip the old way of creating externals. i thirst for consistency, really. i am going to found the church of consistency.
some people could probably find it a bit nasty, that a guy like me, who haven't contributed not a single line of code to the cvs yet, does make such proposals. please excuse me for that (i'm already a bit tired and have had some beers). however, the church of consistency will be founded.
roman
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de