nanogui: config files -> config.h


Previous by date: 28 May 2005 10:23:30 +0100 Re: [PATCH] USE_FLOAT -> HAVEFLOAT, Alexander Neundorf
Next by date: 28 May 2005 10:23:30 +0100 usage of posix functions in src/engine/ and src/drivers/, Alexander Neundorf
Previous in thread: 28 May 2005 10:23:30 +0100 config files -> config.h, Alexander Neundorf
Next in thread: 28 May 2005 10:23:30 +0100 Re: config files -> config.h, Jachym Holecek

Subject: Re: [nanogui] config files -> config.h
From: Alain Volmat ####@####.####
Date: 28 May 2005 10:23:30 +0100
Message-Id: <20050528092321.GE28707@pop.mail.yahoo.com>

I don't know much about the eCos build system, but if big changes have to be
made to the build process of nanoX, I would prefer having some kconfig like
system. Maybe we could base nanoX build system on Erik Andersen's projects
(busybox, uclibc, buildroot) since they are a bit smaller than the linux
kernel. Said very simply, it allows to edit the config file (then avoid
compiling everything) and the configuration is converted into an include file
(like include/autoconf.h in the linux kernel) which allows to automatically
have access to the configuration from the source file too.

This point has been discussed a bit last month on the ML. We also have to
take care of other platform (borland and co) ...


* Alexander Neundorf [Sat, 28 May 2005 at 10:50 +0200]
<quote>
> Hi,
> 
> the nanox configuration is controlled by the "config" files which are used by 
> the makefiles.
> 
> Now this works as long as microwindows is built using these makefiles. This 
> isn't the case for microwindows under eCos, eCos has its own sophisticated 
> build system. There all the HAVE_FILEIO etc. flags have to be specified in 
> the ecos config tool.
> 
> IMO it would be easier if there was a config.h which would contain all the 
> settings and which would be included in the source files. 
> 
> There are also some settings right now already in the source files:
> HAVE_MMAP (device.h, devimage.c)
> USE_ALLOCA (device.h)
> HAVEFLOAT (device.h, devarc.c, devpoly.c)
> USE_FLOAT (devpoly.c)
> HIGHPRECISION (devarc.c)
> 
> and probably more.
> 
> What do you think ?
> The downside would be that the makefile doesn't know about enabled/disabled 
> features and so all files would have to be compiled.
> The sources could look like
> #include "config.h"
> #if HAVE_FEATURE
> ... all the sources of the file
> #endif
> 
> Bye
> Alex
> -- 
> Work: ####@####.#### - http://www.jenoptik-los.de
> Home: ####@####.####                - http://www.kde.org
>       ####@####.####               - http://www.neundorf.net
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 
</quote>

	

	
		
_____________________________________________________________________________ 
Découvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, photos et vidéos ! 
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com

Previous by date: 28 May 2005 10:23:30 +0100 Re: [PATCH] USE_FLOAT -> HAVEFLOAT, Alexander Neundorf
Next by date: 28 May 2005 10:23:30 +0100 usage of posix functions in src/engine/ and src/drivers/, Alexander Neundorf
Previous in thread: 28 May 2005 10:23:30 +0100 config files -> config.h, Alexander Neundorf
Next in thread: 28 May 2005 10:23:30 +0100 Re: config files -> config.h, Jachym Holecek


Powered by ezmlm-browse 0.20.