On Wed, Jan 22, 2003 at 09:33:24AM +0100, Pascal Bauermeister wrote: ... > > It is a good idea to rearrang a bit the whole project. A few remarks: > > * Some projects people live from (I do not speak only about us...) > rely on the current structure, so we must first meet a consensus > on the transition deadline. For instance, switching from CVS to > Subversion is not a blocker, but would have certainly an impact > on our schedules.
Right. This is the only reason I've hesitated to do the reorganization this long. > * We also have a dependency system (reason why we bother everybody > with our mdl files ;-) ) which is one layer above autoconf and > co. Our dependency system deals with a lot of various components > (kernel, drivers, libs, 3rd party software, etc. etc.) and > pgserver and some pg apps are among. Your proposed dependency > system should be an alternative parallel system. I advise to > build it also on top of autoconf, so that one still can access > the autoconf level, like before (which may be just sufficient > for some people). I will keep the autoconf system in place until the new system is built and tested plus some transition period, but the autoconf system can't coexist with it indefinitely. It would negate a lot of the benefits of going to a new system if you had to maintain the old one also. > * We can give a lot of hints about difficult > ^H^H^H^H^H^H^H^H^Hinteresting points we faced when dealing with > dependency issues. We for instance separated the platform from > the product aspects. I was thinking the configuration system would have separate settings for CPU, operating system, video, and input hardware- then those could be wrapped with more tasks for each platform. > * The new dependency/platform/product management system should > certainly not only deal with dependencies, but hide some > platform-specific options related to cross-compilation. One > would have to bother about these options only when introducing a > new platform. All this above autoconf ! Yep, the largest part of this will probably be building libraries on all the supported platforms. It will need to support at least Linux, IRIX, MacOS X, win32, and SNOW binaries eventually. I won't be using autoconf, automake, libtool, or even the shell. It will all be pure python built on SCons, for maximum portability and ease of integration. > * I find very good to be able to quickly build a (nearly) complete > system, e.g. for several embedded platforms, or for demo > purpose. We should however still be able to just pick necessary > pieces separately. right. There will be 'tasks' for these complete systems, which through dependencies will select all the necessary options. I envision that when you browse those individual options, it would be clear that they are being selected or deselected via the dependency process. You could override those selections. > * You said: > > - The current build system is hard to port to non-linux platforms > Do you mean target platforms or build platforms ? Build platforms. I've got PicoGUI running on MacOS X and IRIX, and others have run it under win32. It always requires a lot of hacking on the build system. The largest piece of this is the dependency on bash, and all the other linuxisms in the current config scripts. > > Regards, > > Pascal > > > -- > Pascal Bauermeister > Head of Software Development > > SMARTDATA > PSE-B / EPFL > CH-1015 Lausanne > > http://www.smartdata.ch > mailto:[EMAIL PROTECTED] > Phone: +41 (21) 693 84 98 > fax: +41 (21) 693 84 91 > mobile:+41 (79) 456 82 05 > > > ------------------------------------------------------- > This SF.net email is sponsored by: Scholarships for Techies! > Can't afford IT training? All 2003 ictp students receive scholarships. > Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. > www.ictp.com/training/sourceforge.asp > _______________________________________________ > Pgui-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/pgui-devel -- Only you can prevent creeping featurism! ------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp _______________________________________________ Pgui-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/pgui-devel
