Sounds good. The real test will of couse be when you commit it and we see whether it
causes problems :)
Main thing I would worry about is the cross compilation. In all cases except the MIPS
version, macros set in the configuration affect the code in more significant ways than
just a compiler change.
This new build system could be very nice for managing builds to many architectures (as
I'm sure a few of us have to do now) easily. Right now the server allows you to build
for different configs/CPUs but you have to recompile everything. The client side
doesn't even have an easy way to crosscompile yet.
Thank goodness the C in CVS is for Concurrent!
On Tue, 24 April 2001, Frederic Gobry wrote:
>
> Hi,
>
> I've (locally for the moment) added support for autoconf in the pgserver
> module. The idea is the following :
>
> - the kernel-like configuration system is still here to define "profiles",
> in order to specify what goes in the server
>
> - an autoconf/automake system handles what can be detected automatically
> (SDL, ncurses,...) and provides additional services :
>
> * ability to compile different profiles in different compilation
> directories, which all refer to a unique source directory
>
> * automatic dependency tracking
>
> * archive generation,...
>
> How it will be usable once committed :
>
> - checkout the module from CVS
>
> - run the ./autogen.sh script _once_. This script sets up the
> autoconf/automake environment for a developper. It won't be used for
> packages that are distributed out of CVS.
>
> - run ./configure --with-config=<your favorite config>
>
> - run make
>
> That's it. In addition to the standard automake targets, I've added the
> following :
>
> make config
> make menuconfig
>
> ...which invoke the configuration editor on the config specified in the
> --with-config option.
>
> To compile in a separate directory :
>
> 1. eventually make distclean in the source directory if you have compiled
> in it. It is not possible to compile in multiple directories *and* in the
> source tree.
>
> 2. create a compilation directory anywhere
>
> 3. in this dir, run /path/to/configure --with-config=<config>
>
> 4. run make
>
> This will create a directory tree similar to the one containing the sources,
> but which will hold only object and config-specific files.
>
>
> For cross-compilation (I still have to experiment on that), the idea is to
> use something like :
>
> CC=m68k-pic-coff-gcc LD=... ./configure
>
> I'm eager to hear your comments about this (at least the idea, for the
> moment), and I'm sure I'll have lots of nice remarks once it will be
> discovered that it breaks the compilation once it will be committed in CVS
> :-)
>
> Stay tuned for more information !
>
> Fr�d�ric
>
> --
> Fr�d�ric Gobry SMARTDATA
> --- http://www.smartdata.ch
> Software Engineer Lausanne - Switzerland
> +41 21 693 84 98
>
> _______________________________________________
> Pgui-devel mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/pgui-devel
--
perl -e'socket S,2,1,tcp;connect S,pack(H16,"0200029a80692d32").\0x8;print
grep!/=/,<S>'
_______________________________________________
Pgui-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/pgui-devel
