Re: [AD] MacOS X dynamic linking and enduser package

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


> Personally I'm against creating another allegro-config fork...

Great :-)

> Expecially since the modifications would be minimal. I'm attaching a
> suggested patch to the current allegro-config.in, which should in no
> way harm other ports.

I presume you need other bits for the MacOS X makefile machinery, right?


@@ -49,6 +57,10 @@
    exit $1
 }
 
+if test `uname` = Darwin; then
+   accepts_frameworks=yes
+fi
+
 if test $# -eq 0; then
    usage 1 1>&2
 fi

This would give a false positive for the X11 Darwin port.  Can't you simply 
turn the 'no' in

@@ -19,8 +19,11 @@
 static_libs=@LINK_WITH_STATIC_LIBS@
 lib_type=@LIB_TO_LINK@
 
+accepts_frameworks=no
+
 allegro_ldflags="@LDFLAGS@"
 allegro_libs="@LIBS@"
+allegro_frameworks="@FRAMEWORKS@"
 allegro_cflags=""
 allegro_cppflags=""
 
to a 'yes' with a bit of sed magic?


Otherwise looks good.  I'll add a

AC_SUBST(FRAMEWORKS)

to configure.in so as to get rid of the @..@ in the Unix version.


> About the enduser package, can we generate it automatically using the 
> SF compile farm at each new release (using the provided script in 
> misc/mkpkg.sh), and put it up on the Allegro homepage in the downloads 
> section?

This is Grzegorz's domain.  Do you think it's doable, Grzegorz?

-- 
Eric Botcazou




Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/