Thanks again, Christof. Trying that, I’m getting this result:
➜ pd-cyclone-master make make-lib-executable=yes arch="arm64 x86_64" ++++ info: using Makefile.pdlibbuilder version 0.6.0 ++++ info: using Pd API /Applications/Pd-0.52-1-arm64.app/Contents/Resources/src/m_pd.h ++++ info: making target all in lib cyclone pd-lib-builder/Makefile.pdlibbuilder:815: *** Can not build library blob because lib.setup.sources is undefined. Stop.
I’ve searched for any mention of ‘lib.setup.sources’ and come up empty. Can anybody tell me how to set that correctly?
Thanks for your patience, all!
Phil Stone UC Davis
P.S. My system is up and running on an M1 MacBook, and it is, by my very rough estimate, around 3X faster than my system running on x86-64 Pd. That is, setups which ate nearly all the processor available for audio, now don’t go above 33%. I’m *very* happy, and thinking up ways to use up this bandwidth bonanza.
Date: Fri, 25 Mar 2022 01:17:02 +0100 From: Christof Ressi <info@christofressi.commailto:info@christofressi.com> To: pd-list@lists.iem.atmailto:pd-list@lists.iem.at Subject: Re: [PD] (no subject) Message-ID: <98e3752a-6ac1-2a05-abe1-c79375703ec2@christofressi.commailto:98e3752a-6ac1-2a05-abe1-c79375703ec2@christofressi.com>
Is there a way, using pd-lib-builder, to build the ?unified? library for Cyclone?
Do you mean building everything as a single binary (instead of separate binaries per object)? This can be done with:
$ make make-lib-executable=yes
Christof
I?m currently working well enough for my own needs, but I?d like to supply a deployable library for Deken for cyclone-darwin (including arm64), and am not sure how to do that.
Best,
Phil Stone
UC Davis
IOhannes wrote:
On 3/24/22 15:44, Philip Stone via Pd-list wrote:
/Thank you for the pointers. Running ?make? on its own does indeed
build cyclone, and since I?m doing it on an M1 macbook, it generates arm64 executables, and ?install? puts them in ~/lib/cyclone. (? - Is that right?), and they actually work!/
//
/However, I was hoping to generate fat, single-library binaries for
Deken, and I thought CMake might make that easier. >> I will look into the necessary flags for doing it with ?make?./
//
make arch="arm64 x86_64 i386 ppc"
leave out the architectures you do not want or know (and those that the
compiler is not able to produce, which most likely includes all but the
first two)
mdfgasd
IOhannes