Build script for Linux (waf)

[kris7t]

I wrote a waf (Python) build script for building DSPFilters.

Building the library should be possible on any system, but currently, dependecy checks for JUCE are only implemented for POSIX libraries, X11 and ALSA. Thus it should also build fine on any POSIX system which uses X11 for graphical user interface; I think that's most of them with the notable exception of OS X.

By passing the --build-demo switch to ./waf configure, DSPFiltersDemo will be built. Otherwise, only DSPFilters will be built.

Tested on ArchLinux (with Python 3).

[vinniefalco]

Great!!! I actually was hoping for some help with putting together an X11 build. OS X already has an XCode project, which is fine. Having dependencies on X11 and ALSA (or whatever other audio API is out there) is fine.

I'm wondering though, why does it require so much Python code to build DSPFilters in that environment? It should be possible to just gcc all the .cpp files together (with the appropriate include directories added to the command line switches), specify a couple of extra libraries to link in, and get an executable.

I don't develop on GNU/Linux so I'm in the dark on this. I do, however, have a VirtualBox with Ubuntu on it that I can use.

It would be nice to have a simple Makefile

[kris7t]

Having a simple Makefile is indedd possible, however, Python is rather ubiquitous in the Linux world, so depending on it isn't really more contstraining than depending on, for example, make.

Make is a rather "bare" tool, in a sense that a it is usually used together with autoconf/automake to simplify things like writing a configuration header, finding out what exact CXXFLAGS and LDFLAGS are required (libraries may live in different places in different distributions, different compilers may have different ways of passing options, etc.) and installing the resulting binaries. But I find autotools confusing, and I quite like waf, so I chose that as a build automation framework.

The list of dependecies I put in the script comes from a Makefile I found in the JUCE repository. There may be some unneeded ones, but all of them is a standard piece in most desktop Linux.

[vinniefalco]

UGH I hate autotools / autoconf / automake / autoanything. Well, as
long as it works I guess :-(

On Wed, Apr 4, 2012 at 9:23 AM, Kristóf Marussy
[email protected]
wrote:

Having a simple Makefile is indedd possible, however, Python is rather ubiquitous in the Linux world, so depending on it isn't really more contstraining than depending on, for example, make.

Make is a rather "bare" tool, in a sense that a it is usually used together with autoconf/automake to simplify things like writing a configuration header, finding out what exact CXXFLAGS and LDFLAGS are required (libraries may live in different places in different distributions, different compilers may have different ways of passing options, etc.) and installing the resulting binaries. But I find autotools confusing, but I quite like waf, so I chose that as a build automation framework.

The list of dependecies I put in the script comes from a Makefile I found in the JUCE repository. There may be some unneeded ones, but all of them is a standard piece in most desktop Linux.

---

Reply to this email directly or view it on GitHub:
#6 (comment)

[vinniefalco]

Can you please address issue #7
(#7)? I'm not set up
to test any changes. Let me know

Thanks,

Vinnie