[PD-dev] Packaging of Libraries

[Pierre Alexandre Tremblay]

Dear IOhannes

Thank you for the response. I’m still puzzled, because, for instance, I cannot package the help files tidily in a help folder, they seem to have to share the same folder as the external. Do these need to be top level folder? I can experiment but since I don’t have access to all platform/os combinations, I wondered if there is something that will work across everything.

What I have now, that does not work for help files:

- FluidCorpusManipulation (top folder)
	- externals (2nd level folder)
		- all externs
	- help
		- all helps and sub patches
	- audio
		- all audio
	- examples
		- all code examples
	- ref
		- all html code

And we are building now the CMake to do the packaging conform. Do you suggest I do

- FluidCorpusManipulation (top folder)
	- all externals
	- all helps and sub patches
	- audio
		- all audio
	- examples
		- all code examples
	- ref
		- all html code

That would make a messier top folder but if that is what is needed, we’ll do it.

P

> On 11 Dec 2019, at 18:12, IOhannes m zmölnig <zmoelnig at iem.at> wrote:
> 
> On 12/11/19 10:16 PM, Pierre Alexandre Tremblay wrote:
>> Dear all
>> 
>> We plan to use the fantastic Deken infrastructure to distribute the Fluid Corpus Manipulation objects (flucoma.org), but also to respect its folder architecture for any other type of download, i.e. GitHub binaries and such things… I read the very clear document here (https://github.com/pure-data/deken/blob/master/developer/README.md) but it is not clear how we can package extra material, like a folder of audio files used in the help files, and now that we can use html files, some extra references… and even maybe an example folder.
> 
> just include whatever you want at your won discretion.
> 
> vmxadf
> IOhannes
> 
> _______________________________________________
> Pd-dev mailing list
> Pd-dev at lists.iem.at
> https://lists.puredata.info/listinfo/pd-dev