On Jan 9, 2018, at 6:17 PM, pd-list-request@lists.iem.at wrote:
Date: Tue, 9 Jan 2018 09:17:49 -0800 From: Miller Puckette <msp@ucsd.edu mailto:msp@ucsd.edu> To: IOhannes m zmoelnig <zmoelnig@iem.at mailto:zmoelnig@iem.at> Cc: pd-list@lists.iem.at mailto:pd-list@lists.iem.at Subject: Re: [PD] pd-0.48.1 trouble getting started Message-ID: <20180109171749.GB32197@elroy.localdomain mailto:20180109171749.GB32197@elroy.localdomain> Content-Type: text/plain; charset=us-ascii
Yes, FYI I'm still using makefile.gnu. It takes about 25% as long to do the job as the automake thing does, and when it fails I can usually figure out why.
The configure step is slow but the actual make part is usually not much slower than a plain makefile since automate generates plain makefiles. However, the configure step gives you easily configurable build options, system checks, library checks, and a helpful configuration output print at the end.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Yep... the make step is decently fast. But I almost never just remake without for some reason having to reconfigure. This is probably because of my own file-hygeine habits which date from the 80s, so not relevant to anyone else.
cheers Miller
On Tue, Jan 09, 2018 at 10:55:46PM +0100, Dan Wilcox wrote:
On Jan 9, 2018, at 6:17 PM, pd-list-request@lists.iem.at wrote:
Date: Tue, 9 Jan 2018 09:17:49 -0800 From: Miller Puckette <msp@ucsd.edu mailto:msp@ucsd.edu> To: IOhannes m zmoelnig <zmoelnig@iem.at mailto:zmoelnig@iem.at> Cc: pd-list@lists.iem.at mailto:pd-list@lists.iem.at Subject: Re: [PD] pd-0.48.1 trouble getting started Message-ID: <20180109171749.GB32197@elroy.localdomain mailto:20180109171749.GB32197@elroy.localdomain> Content-Type: text/plain; charset=us-ascii
Yes, FYI I'm still using makefile.gnu. It takes about 25% as long to do the job as the automake thing does, and when it fails I can usually figure out why.
The configure step is slow but the actual make part is usually not much slower than a plain makefile since automate generates plain makefiles. However, the configure step gives you easily configurable build options, system checks, library checks, and a helpful configuration output print at the end.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 2018-01-10 02:53, Miller Puckette wrote:
ep... the make step is decently fast. But I almost never just remake without for some reason having to reconfigure.
i see.
<ad> btw, you can have multiple configurations in parallel.
e.g. the following will prepare to build Pd for linux with and without jack and for W32 (using mingw32 for cross-compilation¹):
$ mkdir build-linux build-linuxjack build-w32 $ cd build-linux; ../configure --enable-jack; cd .. $ cd build-linuxjack; ../configure --enable-jack; cd .. $ cd build-w32; ../configure --host=i686-w64-mingw32; cd ..
then trigger a build for all flavours with:
$ for d in build-linux build-linuxjack build-w32; do \
make -C "${d}" -j4; \
done
or similar.
</ad>
fgmasdr IOhannes
¹ cross-building for W32 currently requires christof's PR#275 to properly work.
Any reason not to use CMake? I find it makes things a lot easier, especially when dealing with multiple platforms. It requires installing CMake, of course, but I think it is reasonable to expect that anyone building Pd from source can install CMake.
On 1/10/2018 12:08 PM, IOhannes m zmoelnig wrote:
On 2018-01-10 02:53, Miller Puckette wrote:
ep... the make step is decently fast. But I almost never just remake without for some reason having to reconfigure.
i see.
<ad> btw, you can have multiple configurations in parallel.
e.g. the following will prepare to build Pd for linux with and without jack and for W32 (using mingw32 for cross-compilation¹):
$ mkdir build-linux build-linuxjack build-w32 $ cd build-linux; ../configure --enable-jack; cd .. $ cd build-linuxjack; ../configure --enable-jack; cd .. $ cd build-w32; ../configure --host=i686-w64-mingw32; cd ..
then trigger a build for all flavours with:
$ for d in build-linux build-linuxjack build-w32; do \ make -C "${d}" -j4; \ doneor similar.
</ad>
fgmasdr IOhannes
¹ cross-building for W32 currently requires christof's PR#275 to properly work.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 2018-01-10 14:53, David Medine wrote:
Any reason not to use CMake? I find it makes things a lot easier, especially when dealing with multiple platforms. It requires installing CMake, of course, but I think it is reasonable to expect that anyone building Pd from source can install CMake.
i find CMake *much* harder to do what i want it to do than an arcane thingee like "autotools".
fgam,sdr IOhannes
-
Dan Wilcox -
David Medine -
IOhannes m zmoelnig -
Miller Puckette