Re: [Alephmodular-devel] Some things about Autoconf

[Br'fin <br...@ma...>]

On Saturday, January 4, 2003, at 02:58  PM, Alexander Strange wrote:

> Here's how I plan to do the autoconf/automake setup:
>
> * Keep everything in alephModular/builds/unix/. Have a script that 
> copies them to alephModular/, then generates the configure scripts and 
> etcetera. Autoconf has its own way to do this, but I don't know what 
> it is.
>
> * The project.pbxproj won't be automatically generated, because you'd 
> have to do a reverse-configure thingy to commit after it's edited.
>
I actually don't mind having to take diffs from project.pbxproj before 
and after an edit and applying them to the project.pbxproj.in file. 
(With only the .in file in the repository)

For the other project I work on, Bochs, you have to do that same kind 
of effort whenever you edit the Makefile or whenever you edit the 
configure script.

It seems fairly typical of the process.

> * Get rid of the MPW stuff or move it off somewhere else; it has name 
> conflicts.

Understood. I don't mind labeling and removing the MPW make and build 
files for being Obsolete.

Do you have a list of mpw files I should be removing?

> * Build the individual sections of the code as separate static 
> libraries, then link them together. If someone has a list of the AM 
> modules, I'll use that; otherwise, I'll figure out a temporary one 
> from A0.

For now I think it's just going to be the one directory of 
alephModular/marathon2. I think we're making progress on module 
definitions. But the code isn't in any shape for it currently.

> * The configure script won't be very useful, since this is Carbon-only 
> at the moment; so it'll just detect Carbon and set up everything for 
> that.

Definitely understood. Trying to setup autoconf now is laying framework 
for the future. The only major changes and benefits for the current 
time are moving project builder compile flags to a more flexible space. 
Likewise setting up one place to specify version.

-Jeremy Parsons