[CF-Devel] automake/libtool support...

Jacek Konieczny jajcus at bnet.pl
Wed Aug 7 12:30:23 CDT 2002


Helo,

This time I think I write to the right list :-)

I have nearly finished automake changes for crossfire. This changes
includes also some FHS-related fixes:
- configuration files go to ${pkgconfdir} (default: ${sysconfdir}/crosfire)
  this makes it easier to see which files hold local configuration.
- plugins go to ${pkglibdir}/plugins (default: ${prefix}/lib/crossfire/plugins)
  This is the proper place, as these are architecture-dependant
- various tools (including random_map) go to ${pkglibdir} (${prefix}/lib/crossfire)
  These are tools which are not frequently used and their names are not
  associated with crossfire. This is needed to prevent executable name
  conflicts, esspecialy when crossfire is installed in prefix like
  /usr/local or /usr
Nearly all of this can be changed using configure script options.
I have also made changes to python detection in configure script, so it
should work in more environments (at least it works for me :-)).

I have removed "patchlist" target, as I don't know what it is supposed
to do, but I suppose it can be done using some automake mechanisms.

I am working with CVS sources (using anon CVS) and I wanted to prepare
patch against them and send it here. But I found it very hard to make 
such patch using anon-cvs (I cannot mark added/removed files with cvs
add/remove), so maybe I could get r/w access to crossfire CVS. My
sourceforge account is "jajcus". I could commit my changes to separate
branch, so everybody interested can test it and if it is ok it would be
merged with HEAD. 

Greets,
        Jacek

    
    


More information about the crossfire mailing list