Hi,
I just started testing the 1.4.0 version, and had a few suggestions.
The configure script for the examples could fail more nicely if not
finding Agar (from agar-1.4.0/demos), as we can see shell errors and the
configure script believing wrongly that it found an Agar version:
""
.../configure
[..]
checking for the X/Open Threads Extension...yes
checking for PTHREAD_MUTEX_RECURSIVE...no
checking for PTHREAD_MUTEX_RECURSIVE_NP...no
checking for SDL (http://www.libsdl.org)...no
checking for OpenGL (http://www.opengl.org)...yes
checking whether -lopengl32 works...no
checking whether OpenGL works...yes
checking for FreeType (http://www.freetype.org)...no
checking for Agar (http://libagar.org/)...[: 3029: -gt: unexpected operator
[: 3029: -eq: unexpected operator
*
* Found Agar version ..
* This software requires at least version 1.3.
* Please upgrade Agar and try again.
*
*
* If the previous test failed due to Agar not being found,
* make sure you have already installed Agar on your system
* and that the agar-config binary is in your PATH.
*
* To install Agar, go to the top-level directory and run:
* make all install
*
make: *** [configure] Erreur 1
"""
Adding a -h/--help option would be useful, to tell notably "check that
the agar-config binary is in your PATH" (same thing for SDL/sdl-config,
Freetype/freetype-config) directly from the help. It could even continue
to fake the autotool conventions, with a --with-sdl-prefix option for
example.
I configured Agar to be single-threaded, and the overall configure
script stops on error for the 'threads' test, requiring that
--enable-threads be selected when building the library. Maybe skipping
this test (with a proper warning) should be preferred when having to
deal with a single-threaded version of the library?
My purpose is now to test a custom Agar event loop with SDL+OpenGL.
Thanks for the customeventloop.c example!
Best regards,
Olivier.
_______________________________________________
Agar mailing list
[email protected]
http://libagar.org/lists.html
