It’ll build an empty JUCE window using my usual settings. The README should tell you everything you need to know, but I’ll do a quick rundown of the relevant files. There are basically three files to worry about when creating an autoconf-based project (Anjuta just provides a GUI wrapper to autoconf, really, so everything here applies to it too); configure.ac, Makefile.am, and src/Makefile.am (assuming you’re using the standard(?) *nix directory scheme, anyway). Generally you’d run aclocal, autoconf, and automake on them, which would generate a configure script and some Makefile.in’s, before running the configure script itself to generate the actual Makefiles (tailored somewhat to your computer), and finally running make itself.

AC_OUTPUT([
Makefile
src/Makefile
])[/code]
This is used to generate the configure script, which will in turn generate Makefiles for your project when run. As you can see, this file was originally generated by Anjuta, but I’ve added a bunch of checks to ensure all the necessary libraries get linked in. It’s fairly simple stuff; AC_CHECK_LIB checks if the required library exists on your system, and if it does, adds -l to your LDFLAGS. By default the configure script will assume JUCE is in the app’s parent directory, but the AC_ARG_WITH macro lets you set which directory it’s in when you run the configure script (e.g. ./configure --with-JUCE=/home/niall/juce).

Copy all the spec files. Of cource, only one is actually used.

[/code]Makefile.am is used to generate the root Makefile. Again, it’s auto-generated by Anjuta (complete with spelling mistake :lol:) - I’ve only added a single line (“JuceExampleProject.anjuta”) to ensure the Anjuta project file gets included in the tarball when you run ‘make dist’. If you have any non-source, non-documentation files you want to include in the tarball, this is where you put them.

JuceExampleProject_LDADD = (X_PRE_LIBS) \
(X_LIBS)
$(X_EXTRA_LIBS)
[/code]
This is used to generate the Makefile for the src directory, and it’s here where the rest of the compiler settings get set. Again it’s generated by Anjuta, and when you add any source files to your project in Anjuta, they’ll get added to the list ‘JuceExampleProject_SOURCES’ (which you’d do by hand if you were just using plain autoconf). I’ve added the preprocessor macros JUCE needs to ‘AM_CXXFLAGS’, and added the stuff needed to build against the X libs to ‘INCLUDES’ and ‘JuceExampleProject_LDADD’.