Re: [gnome-love] Using make

[Ross Golder <ross golder org>]

We tend to use 'automake' to generate a Makefile.in file from a
Makefile.am, and then 'autoconf' creates a configure script that the
user runs to generate their Makefile(s).

autoconf and automake can be quite convoluted and daunting, but the
benefits are worth it. Start by copying the Makefile.am and configure.in
from a simple project, and using the automake/autoconf docs for
reference, mould them to work with your project, getting to understand
them at the same time.

http://developer.gnome.org/doc/tutorials/gnome-libs/using-autoconf-automake.html

--
Ross

On Mon, 2002-04-29 at 21:50, Maya wrote:
> Ok, I know that this is not much of a GNOME thing but I started to 
> play around with GNOME/Gtk C and C++ widget library. The idea is to 
> eventually port all applications to GNOME. Right now I am using Qt, 
> but I am a not too sure about the terms of the Qt License and Qt is 
> becoming sort of the Linux wing of MS world and knowing MS as well as 
> I do, I know that eventually they will start canivalizing those who 
> have used their "free" services.
>
> Now going back to my problem, one of the biggest obstacles I have 
> found is making my own 'Makefile'. Under Qt that was not a problem and 
> under MS it was transparent. I am looking for a way that I can have my 
> own 'Makefile' but without the burden of having to maintain the 
> 'Makefile' myself. Perhaps, I am asking too much, but like I said I am 
> a new comer and don't have any idea what GNOME has to offer.
>
> I have, however, tried Glade and Anjuta, but at the moment I am more 
> interested in learning the library than unsing the RADs.
>
> TIA
>
> _______________________________________________
> gnome-love mailing list
> gnome-love gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-love