[epiar-devel] GNU Autotools Walkthrough
Moss Jones
bmossjon at yahoo.com
Mon Nov 2 14:28:43 PST 2009
I agree with that and noticed that too. We should have a build, bin, docs
directory and so on. On the 0.5 source, it was declared in the
Makefiles (i.e. Makefile.linux). Now I think there is just the Makefile.am
where you declare OBJS=main.o, sprites.o, etc. Just place the dir
name ./objs/ in front of this or declare a variable OBJ_DIR=./objs
as such. Still working with github.com and new source codes, so
posting that info here...
----- Original Message ----
From: Matthew Zweig <thezweig at gmail.com>
To: "epiar-devel at epiar.net" <epiar-devel at epiar.net>
Cc: "epiar-devel at epiar.net" <epiar-devel at epiar.net>
Sent: Mon, November 2, 2009 3:39:53 PM
Subject: Re: [epiar-devel] GNU Autotools Walkthrough
I spent a few hours this weekend trying to figure out how to have the
*.o files not generated in the project root. I never found a solution
that I liked. If it's possible, I would like to get our repo cleaned
up.
~Matt
Sent from my iPhone
On Nov 2, 2009, at 11:53 AM, Christopher Thielen <cthielen at mac.com>
wrote:
> I saw a decent explanation of the build system we use and I know it
> confuses a lot of people so here's the GNU Autotools build system in
> one page: http://epiar.net/trac/wiki/AutotoolsBuildSystemHowto
>
> I took it from reddit.com and it's permanently hosted on our Trac
> system
>
>
> _______________________________________________
> epiar-devel mailing list
> epiar-devel at epiar.net
> http://epiar.net/mailman/listinfo/epiar-devel
_______________________________________________
epiar-devel mailing list
epiar-devel at epiar.net
http://epiar.net/mailman/listinfo/epiar-devel
More information about the epiar-devel
mailing list