Re: CinePaint SCons Packager
Kai-Uwe Behrmann <[email protected]>
| Newsgroups | gmane.comp.video.cinepaint.devel |
|---|---|
| Message-ID | <[email protected]> |
Am 29.02.08, 09:18 -0800 schrieb H. S. Teoh: > On Fri, Feb 29, 2008 at 06:21:30PM +0100, Kai-Uwe Behrmann wrote: > > Am 29.02.08, 07:34 -0800 schrieb H. S. Teoh: > > > Yes, in fact. I've checked out the latest(?) CVS code for CinePaint from > > > sourceforge, but when trying to configure it, I get this: > > > > > > -----snip----- > > > checking for pkg-config... /usr/bin/pkg-config > > > ./configure: line 23300: syntax error near unexpected token `1.2.8,,' > > > ./configure: line 23300: ` AM_PATH_GTK(1.2.8,,' > > > > > > -----snip----- > > > > > > Am I missing something? > > > > configure --enable-gtk2 > > I just tried that, and I still get the same error. Maybe it's an > autoconf version conflict? It seems a bit strange that it should get a > syntax error if it's just a missing flag. Hmm, another possibility is that the GTK1 macros are missed. Newer systems dont have them. I still maintained Gtk1 versions. For instance to support the gtk-osx builds. The Gtk2 on osX version did not work. > [...] > > > Anyway, in spite of configure not working, I've gone ahead to write > > > SConstruct and SConscript's, and so far, I managed to get libhalf, > > > lib/wire, lib/fl_i18n, and libgimp to compile. Most of app/ compiles as > > > > libgimp? > > There's a subdirectory called 'libgimp' in the source...? (Am I looking > at the right source tree??) This name should not be used for libraries of this project. The libgimp directory contains only headers. There should no object code compile. > > For configure. If in the end a configure; make; make > > install/rpm/dist-gz works this would be really appreciated as many > > users still know these commands. Even if you provide only wrappers. > > Scons is one of many tools. Make is very well known. > [...] > > After some thought, I was thinking, maybe it's better to leave configure > alone for now, and get SCons to work with the build part first. If that > works well, then maybe we can look at replacing autoconf. As far as I > can tell, though, that would take quite a bit of effort. As for > supporting 'configure; make; make install', this should be quite easy > (at least for the last 2 steps); we just wrap them in the Makefile to > call scons to do the real work. Fine. kind regards Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/