Re: [PD-dev] call for discussion double-precision file extension

2022-03-29 Thread Sebastian Shader via Pd-dev
I wonder if anything should be considered for multi-instance support as well (externals compiled w/ PDINSTANCE) -seb Date: Tue, 29 Mar 2022 11:28:57 +0200 From: IOhannes m zmoelnig To: Pd-dev@lists.iem.at Subject: [PD-dev] call for discussion double-precision file extension hi, TL;DR i'd like

Re: [PD-dev] call for discussion double-precision file extension

2022-03-29 Thread Lucas Cordiviola
Joining the discussion: I think the "deken-specifier" is Ok. We should probably be prepared for both apps installations coexisting. In the case of Windows we should have a different default location and a name for the double app. Think of Pd-double whose default installation via the

Re: [PD-dev] call for discussion double-precision file extension

2022-03-29 Thread Christof Ressi
One "con" I can imagine is that there are "cleaner" alternatives than name mangling. For example, VST3 plugins use a bundle structure which also allows for "merged bundles": https://developer.steinberg.help/display/VST/Plug-in+Format+Structure. Something similar *could* work for Pd

Re: [PD-dev] do we need Pd-double binaries (Re: call for discussion double-precision file extension)

2022-03-29 Thread Alexandre Torres Porres
Em ter., 29 de mar. de 2022 às 12:10, IOhannes m zmoelnig escreveu: > i'm not exactly sure what you mean here. > > 1st: you do not need a compiled version of Pd in order to produce a > double-precision external (at least on macOS and Linux). > so what are you waiting for? > I just don't think

Re: [PD-dev] call for discussion double-precision file extension

2022-03-29 Thread Roman Haefeli
On Tue, 2022-03-29 at 17:29 +0200, Christof Ressi wrote: > +1 +1 > I think it's nicer to use a common extension and have the > platform/arch/floatsize specifier as a seperate component. > > I didn't especially like this back then, but in the meantime i've > > come to the conclusion that it's

Re: [PD-dev] call for discussion double-precision file extension

2022-03-29 Thread Christof Ressi
+1 I think it's nicer to use a common extension and have the platform/arch/floatsize specifier as a seperate component. On 29.03.2022 11:28, IOhannes m zmoelnig wrote: hi, TL;DR i'd like to suggest to use deken-specifiers as (optional) part of external filenames, in order to allow

[PD-dev] do we need Pd-double binaries (Re: call for discussion double-precision file extension)

2022-03-29 Thread IOhannes m zmoelnig
On 3/29/22 16:08, Alexandre Torres Porres wrote: I haven't provided double precision externals yet because I think the binary should be easily available for those unaware of compiling magic i'm not exactly sure what you mean here. 1st: you do not need a compiled version of Pd in order to

Re: [PD-dev] call for discussion double-precision file extension

2022-03-29 Thread Alexandre Torres Porres
Yeah I guess it makes sense to have a distinct extension. I haven't provided double precision externals yet because I think the binary should be easily available for those unaware of compiling magic first. And while we're at it, I guess it's time to provide them at miller's site and puredata.info

[PD-dev] call for discussion double-precision file extension

2022-03-29 Thread IOhannes m zmoelnig
hi, TL;DR i'd like to suggest to use deken-specifiers as (optional) part of external filenames, in order to allow co-installability of externals of different OSs, architectures and floatsizes (and more to come). i would really love to push the double precision saga towards a (happy) end. we