[no subject]

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


> My understanding of the build process was you needed configure.in and
> makefile.am. aclocal will generate some m4 macros, autoconf will
> generate configure, automake will generate makefile.in, and configure
> will generate all the makefiles.

We don't use automake.

> It would be much simpler to change the linking of X extensions by editing
> Makefile.am instead of makefile.in

Why?

> (btw, many unix people refer to makefile's with a capital M ).

Both are recognized automatically by GNU make, so this doesn't really matter.

> Basically Im wondering where did makefile.in come from and can we switch
> to makefile.am?

Why?

-- 
Eric Botcazou




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