At 17:00 16.03.2002 +0100, Frederic Gobry wrote: >Indeed, I was wondering if you had some magic script or so to ensure >there was no incoherence between the two...
Maybe this magic script would be an easier solution. I remember that the linuxvideo.org people were using some CVS magic to keep libmpeg2 in sync for the mpeg2dec and open media system projects. I'm not sure how it was done, but I could image that it would be enough to symlink the include directories of the CVS repository. > > The advantage of this method is that cli_c and themetools don't need > > a copy of pgserver's headers, only the new headers for cli_c. The > > disadvantage is that you have to install pgserver before you can > > build cli_c. > >It depends on what you expect: if there is a need for installing both >everytime, then it's maybe simpler to put everything in a common >project (from the autoconf point of view). On the other hand, if you >insist on the separation, maybe a third part containing the protocol >only could solve the problem: cli_c depends on proto, pgserver depends >on proto, and everybody can install what is needed... The RPM build script I wrote for SSV depends on being able to build all the picogui-* rpms at once and then installing everything, and I would prefer to keep that possible. Adding another 'proto' package might even make this worse, although it probably is the cleanest solution in terms of package management. There is also another problem with different versions of server and library headers. Image someone wants to upgrade his/her picogui installation and compiles the new cli_c package while the old server package is still installed. The least that needs to be done is that configure can detect this and aborts with a proper error message. IMHO, configure in cli_* should get the correct header files by looking at the output of 'pgserver-config --version' and 'pgserver-config --cflags', where pgserver-config would be created by pgserver/configure. cli_*/configure should look for pgserver-config (in this order) in 1. The user-specified path (--with-pgserver=) 2. The default source directory ($PWD/../pgserver/) 3. The installation directory ($prefix/bin) 4. The system path Of course, if CVS can syncronize the headers itself as described above, we don't need this. Arnd <>< _______________________________________________ Pgui-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/pgui-devel
