Re: [Alephmodular-devel] Autotools patch
Status: Pre-Alpha
Brought to you by:
brefin
From: Alexander S. <ast...@it...> - 2003-01-05 03:47:30
|
On Saturday, January 4, 2003, at 10:17 PM, Br'fin wrote: > > On Saturday, January 4, 2003, at 08:20 PM, Alexander Strange wrote: > >> Here's the preliminary autotools patch: >> http://astrange.ithinksw.net/alephmodular-autotools.patch.bz2 >> >> What It Does: >> Generates a PB project with the current version number, and >> InfoPlist.strings and marathon2.r. >> You can specify whether to add '.CVS' to the version with ./configure >> --with-release. >> >> What It Doesn't Do: >> Produce a Makefile that does anything useful. >> >> What You Do After Patching: >> Move the project.pbxproj to project.pbxproj.in, the InfoPlist.strings >> to InfoPlist.strings.in, and the marathon2.r to marathon2.r.in. (Why >> didn't I do it? To make the patch smaller) >> >> It also might barf on InfoPlist.strings, but the conflict stuff can >> be fixed easily. >> > Ok, got the patch essentials setup. > > I had a little trouble with autogen.sh since I didn't have libtoolize > installed. So commented out that portion of the script for the quick > run. You can replace that part of autogen.sh with 'glibtoolize'; the Developer Tools come with that. > Now I admit I am unskilled almost completely with autoconf and such. > So I can only compare with Bochs. Bochs doesn't have any Makefile.am's > (only Makefile.in's) Likewise it has a config.h.in and a configure.in, > but no configure.ac > > In a similar way, configure.in is checked in, but so is configure so > most folks just run ./configure without creating it from configure.in. configure.ac is the same thing as configure.in. > In other words, I think there must be a somewhat simpler way of > setting up autoconf. We seem to have too many files by the time we've > built configure. > > -Jeremy Parsons Comparing with another project (liboss), we have 15 more files than before we run autogen.h. It has 12 more. This is explained by the way we keep our three files in build/unix/. So, we're normal :) Also, some of these files aren't needed when we make a distribution (see http://www.gnu.org/manual/automake/html_chapter/automake_14.html#SEC89 and http://www.gnu.org/manual/automake/html_chapter/automake_15.html#SEC90). |