Well, the new build system has been in PicoGUI's CVS for a while now, so I thought I'd 
share my thoughts on it.

- I love the extra flexibility it gives when cross-compiling. I was very pleased at 
how easy it was to cross compile pgserver and libpgui.

- The dependency checking and grouping of directories in .a files seems to reduce the 
compile time quite a bit

- I noticed that the 'make install' in cli_c doesn't install the header files right. 
It needs to copy the include/picogui/*.h files to a new directory, 
/usr/local/include/picogui, but instead it copies them to /usr/local/include.

- Tim reported problems with autogen and slackware. I haven't looked into this either. 
(Though I do have an old laptop with Slackware on it...)

- I like the capability to use multiple .config files, but it would be nice if it 
defaulted to a copy of config.defaults instead of config.defaults itself. As it is 
now, it's too easy to accidentally commit your config changes to CVS

- Just something for us all to think about for the future... Might be nice to migrate 
the configuration system from menuconfig to Eric Raymond's CML2 language. 
(http://www.tuxedo.org/~esr/cml2/) PicoGUI seems to have similar configuration needs 
to Linux, just on a smaller scale. The dependancy checking might make it easier to 
have the video drivers automatically select (but still allow overriding) input drivers 
and video base libraries. Less required options means less chance of misconfiguring a 
pgserver, and in general less cruft ;)

Thanks for the build system, Fr�d�ric!

--
To the systems programmer, users and applications server only to provide a 
test load.


_______________________________________________
Pgui-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/pgui-devel

Reply via email to