[PD-dev] lib name and trunk commit

[Cyrille Henry]

ok, thanks,

i'll certainly move nusmuk-audio and nusmuk-utils to trunk/externals as soon as I have time.
cheers
cyrille


Le 31/10/2012 17:40, Hans-Christoph Steiner a écrit :
>
> On Oct 31, 2012, at 9:20 AM, Cyrille Henry wrote:
>
>> hello,
>>
>> I would like to commit a new library.
>> I've heard that having a pmpd object in a pmpd lib did cause problem for some, but i can't remember why.
>> so does it matter to have a library name different from all objects name, or can i use the same?
>
> If you want to make a library that is only one object, then that is the best approach, check out plugin~, bassemu~, freeverb~, etc.  By default when loading [classname] Pd will try classname/classname.pd_linux then classname.pd_linux.
>
> If you have a library called 'bar' and it includes many objects including one called 'bar', that will make things confusing for a number of reasons.  [bar] will load just by typing [bar] (i.e. it'll find bar/bar.pd-linux) but any other object in that library will not load until you load the library itself using [declare] or [import].  vbap currently is like this and that setup is quite annoying.
>
>> Since finding a lib is harder when it's located in a developer directory, and since i will not be the only dev for this lib, can i upload it directly in trunc, or should i still use the nusmuk folder?
>
> I agree that the developer folders make things harder to find. Just put anything directly in trunk/externals where most libraries are. Feel free to move anything out of nusmuk there too.  If you base your libraries on the Library Template like pmpd, then it'll automatically be built as part of a nightly test build:
>
> https://macosx105-i386.pdlab.puredata.info/job/template-libraries/
>
> .hc
>