Re: CinePaint SCons Packager

On Fri, Feb 29, 2008 at 06:21:30PM +0100, Kai-Uwe Behrmann wrote:
> Hello Teoh,
> 
> 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 alloca... yes
> > 
> > PKG_CONFIG_PATH =
> > 
> > checking fd_set and sys/select... yes
> > checking for yywrap in -lfl... yes
> > checking for pthread_create in -lpthread... yes
> > checking pthread.h usability... yes
> > checking pthread.h presence... yes
> > checking for pthread.h... yes
> > 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.


[...]
> > 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??)


[...]
> > 3) What's the convention for checking stuff into CVS? I guess it
> > must at least be compilable, and maybe somewhat well-tested as well?
> > (Also, I don't have commit access yet.)
> 
> You can easily provide patches in the time being.

OK, cool.


> 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.


--T

-------------------------------------------------------------------------
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/