nanogui: Microwindows cleanups .... some ideas
Subject:
Re: [nanogui] Microwindows cleanups .... some ideas
From:
Jachym Holecek ####@####.####
Date:
19 Apr 2005 18:40:04 +0100
Message-Id: <20050419173951.GA8686@merlot.ics.muni.cz>
Hi,
> some ideas I'm thinking about and would like to do for
> microwindows:
> - the basic idea is to avoid compiling something that
> a target will for sure never use. [... snip ...]
Nice.
> - another one would be much simpler. A bit of source
> file reorganisation and configuration framework (make
> menuconfig ? ). I think there are now more and more
> things in several folders (like /drivers) and it would
> help if we could separate drivers from each others ...
> for example there are so many mouse and keyboard
> drivers, they could be moved into drivers/mouse
> drivers/keyboard ... for example ...
> as far as the configuration framework ... well ...
> something similar to the usual make menuconfig would
> be great ?
I don't find 'make menuconfig' particularly exciting (and once you
want to maintain a number of different configurations, it gets about
zero-useful). FWIW, I would prefer a configuration mechanism driven
by well-though-out configuration file[s] -- but NanoX's build isn't
probably complicated enough to warrant designing such a system. In fact,
current configuration scheme is close-enough to it, I don't see any
immediate problem to fix.
'make menuconfig' is just eye-candy -- it won't really help and you'll
have to spend time maintaining it. Perhaps a more interesting project
would be to make NanoX build in separate objdirs?
Just my 2c.
Regards,
-- Jachym Holecek
