My gut feeling is that this is best kept as two separate builds for the platform. IMO we don't want to have to resort to a lot of trickery fighting the system's preferred modus operandi as it will, as you write, likely blow up in our faces.
On Jun 12, 2023, at 12:00 PM, pd-dev-request@lists.iem.at wrote:
Message: 1 Date: Mon, 12 Jun 2023 09:08:36 +0200 From: IOhannes m zm?lnig <zmoelnig@iem.at mailto:zmoelnig@iem.at> To: pd-dev@lists.iem.at mailto:pd-dev@lists.iem.at Subject: Re: [PD-dev] double precision pd? Message-ID: <d02ebe17-dce6-98a3-b55c-0f923c5f79ec@iem.at mailto:d02ebe17-dce6-98a3-b55c-0f923c5f79ec@iem.at> Content-Type: text/plain; charset="utf-8"; Format="flowed"
On 6/8/23 15:23, IOhannes m zm?lnig wrote:
Oh no, compilation will be complex.
Not really. You basically have to build twice...
oh no, i forgot about the intricacies of the windows build.
with macOS and Linux we have this nice single "pd" binary (or "pd64"). but with Windows we need the supporting pd.dll library where all the guts live (so externals have something to link against), and as of now, double-precision externals on Windows will link against pd.dll as well (but expect that to be contain the double-variant).
-------- Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Not really that we have to do this but:
Surely we need 2 compilations but in my head it does not hurt much that certain files have their "64" appended in the filename and share the same bin and extra dir.
like
pd/bin pd.exe pd64.exe pd.com pd64.com pd.dll pd64.dll pdreceive.exe pdreceive64.exe pdsend.exe pdsend64.exe
pd/extra bob~/ bob~.dll bob~.Windows-amd64-64.dll ...
pd-lib-builder can easily be instructed to pick pd64.dll for a double build.
This should also work on Linux and macOS apps.
building should look like:
make make clean make64
"make64" rename and copies the files on target.
if this is feasible we avoid having tons of duplicate .pd files and stuff and also having 2 different packages.
just thinking
--
Mensaje telepatico asistido por maquinas.
On 12/06/2023 07:21, Dan Wilcox wrote:
My gut feeling is that this is best kept as two separate builds for the platform. IMO we don't want to have to resort to a lot of trickery fighting the system's preferred modus operandi as it will, as you write, likely blow up in our faces.
On Jun 12, 2023, at 12:00 PM, pd-dev-request@lists.iem.at wrote:
Message: 1 Date: Mon, 12 Jun 2023 09:08:36 +0200 From: IOhannes m zm?lnig zmoelnig@iem.at To:pd-dev@lists.iem.at Subject: Re: [PD-dev] double precision pd? Message-ID: d02ebe17-dce6-98a3-b55c-0f923c5f79ec@iem.at Content-Type: text/plain; charset="utf-8"; Format="flowed"
On 6/8/23 15:23, IOhannes m zm?lnig wrote:
Oh no, compilation will be complex.
Not really. You basically have to build twice...
oh no, i forgot about the intricacies of the windows build.
with macOS and Linux we have this nice single "pd" binary (or "pd64"). but with Windows we need the supporting pd.dll library where all the guts live (so externals have something to link against), and as of now, double-precision externals on Windows will link against pd.dll as well (but expect that to be contain the double-variant).
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com robotcowboy.com http://robotcowboy.com
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
-
Dan Wilcox -
Lucas Cordiviola