I invite you to test allegro 4.3.11 SVN some more. What I'm most interested in is the build system, especially the macosx-universal target for addons. The most recent SVN snapshots can be found at http://www.strangesoft.net/allegro/
These packages are ready to be built, just like the normal releases.

Downloaded 4.3.10plus from your site, Milan. The base library built fine but the addons couldn't link for want of the allegro-config file which was nowhere in the base directory (`../../allegro-config... etc.`).

intel iMac 10.5.6 xcode 3.12

-Paul

make WITH_ALLEGRO_GL=1 WITH_LOADPNG=1 WITH_LOGG=1 WITH_JPGALLEG=1
Building them separately might not even work. I've also added a WITH_ALL_ADDONS in SVN now.

No, you're not supposed to install first. Oh, I didn't notice that on OSX allegro-config is generated on install.

Rev. 11360 failed to build for me with this error:

make[1]: Entering directory `/home/paul/src/allegro-4.3.10plus/addons/allegrogl'
gcc -o obj/unix/release/x.o -Iinclude -Iinclude/allegrogl -Iinclude/allegrogl/GLext -I../../include   -O2 -Wall -ffast-math -fomit-frame-pointer -fPIC -c src/x.c
src/x.c: In function ‘allegro_gl_x_create_window’:
src/x.c:1080: error: ‘struct _xwin_type’ has no member named ‘override_redirected’

GCC 4.3.2 on Linux

I am attempting to compile it with cygwin, I got the base allegro built, but when I go to compile a test application...

#include <allegro.h>

int main()  {
  allegro_init();
  allegro_message("Hello World!");
  return 0;
}
END_OF_MAIN()

I get the following...

$ gcc test.c -o test.exe -lalleg
In file included from /usr/local/include/allegro/internal/alconfig.h:44,
                 from /usr/local/include/allegro/base.h:41,
                 from /usr/local/include/allegro.h:25,
                 from test.c:1:
/usr/local/include/allegro/platform/almngw32.h:24:23: direct.h: No such file or directory

The only relevent direct.h is in "h:\cygwin\usr\include\mingw", forcing that into the include path gave me...

$ gcc test.c -o test.exe -I /usr/include/mingw -lalleg
/cygdrive/c/DOCUME~1/Timmy/LOCALS~1/Temp/cczsl7bl.o:test.c:(.text+0x7): undefined reference to `__errno'
collect2: ld returned 1 exit status

Which isn't really what I wanted. I searched the forum and this has come up before, but there was no solution posted.

I am not sure where to go from here. Any help will be greatly appreciated, I am going to try the current version (4.2.2) to see if it has the same problem.

On the plus side, allegro did actually compile.

Edit:
4.2.2 compiled with ALLEGRO_USE_C=1, but when it came to the test program, I get exactly the same problem.

No worries, the latest 4.3.x from strangesoft is what I was compiling. By stand alone allegro, I meant without enabling the simultaneous builds of the addons.

Ah, thank you. I'll try using the WITH_* options later. Now that the add ons are being bundled with Allegro, shouldn't the text help files in docs/build/ and docs/src be updated to notify the builder of the new options? Also, it would be nice to have both the dependencies of each add on and their respective licenses noted briefly in the main allegro/docs/[build | src]/platform_build_directions_file, or in a separate readme_addons file.

If the add ons are linking to the allegro library, where are they looking for it at? Do they specify a search path for the linker? In effect, if they're built separately (using the makefiles that come in allegro/addons/*, does allegro need to be installed to the compiler's lib directory?

It looks like AllegroGL needs to have the allegro folder two directory levels up, and adds a search path to ../../lib/$(COMPILER), so it's not linking against the allegro library in the compiler directory. It looks like logg does the same thing, as well as jpgalleg and loadpng. So it doesn't seem that any of the add on targets require allegro to be installed to the compiler directory and that each could be built separately after allegro is built two directories up.

Anyway, I'll try building them separately after I finish compiling zlib, libpng, and the ogg and vorbis libraries.

AllegroGL compiled fine for all [optimized | debug][dynamic | static] targets separately using the makefile in the addons/allegrogl folder.

I'm having some problems building jpgalleg though :

The 'all' STATICLINK=1 target built okay, both the lib and the examples, but then the 'all' STATICLINK=1 DEBUG=1 target didn't recompile the object files for the library or the examples, and immediately relinked the library. After that, both the debugging and non-debugging versions of the 'all' target failed, as can be seen in the log above (and neither tried to recompile any object files either).

Compiling libpng and zlib has been just about the least fun thing that I've done in a while. I had to manually install everything because they don't understand Windows doesn't have *NIX commands, except for the ones provided by MSYS, and that would install them in the wrong place for me. At least MSYS lets me use the configure scripts.

From reading the loadpng makefiles, it doesn't have any option for a debugging build, and it doesn't use separate names for the static and dynamic libraries... because there's no dll build, and STATICLINK=1 only seems to apply to the example programs it creates (only a statically linked .a archive is created). Other than that, loadpng compiled fine, except for some deprecated function warnings for browse.c.

That's enough for today though. Tomorrow I'll pickup ogg and vorbis, and compile logg.

Okay, now I have addons.html, addons.rtf, and addons.txt in their respectively named format folders ( I may have had them before though, but I didn't check ), but there's no addons.txt in the build folder. It makes sense to me to have 'targets.txt' and 'addons.txt' come with the distribution in the docs/build folder, but that's up to you guys.

I can confirm that, thanks. Everything built properly.

When you get allegro directly from SVN you have to run "make depend", among with many other things... So better use the snapshots I gave a link to.

lemranger: find where on is allegro-config on your system and copy it into the allegro build dir. This is a workaround for a rather big design flaw.

I managed to compile the logg addon sucessfully after coming up with a workaround for some trouble with getting libvorbis to compile correctly. It would be nice if the play_ogg and stream_ogg example programs from logg let you quit before the music is finished though.

If anyone's having trouble compiling libvorbis because of undefined references to ogg functions, you can try my workaround for it.
(Use 'export LIBS=-logg' in MSYS before running configure and make)

@Milan
Thanks for reconfiguring jpgalleg, I'll try the latest strangesoft package tomorrow.

Press Ctrl-C . Can't get input without creating a window in Linux, so to be fair they're console apps.

Ctrl+C should work in a console window, unless there is an interrupt handler that overrides it.