[Clam-devel] compiling the network editor

[David García Garzón]

I just commited a check on the scons version on the libraries SConstruct file.
Maybe we should do the same with remaining SConstruct files.


On Wednesday 30 May 2007 12:53:59 David García Garzón wrote:
> So it is likely to be just a matter of scons version. Versions up to
> 0.96.90 are known to have problems. On our mac we are using 0.96.92.D0002.
> There is a macport for scons in a up-to-date version.
>
> On Tuesday 29 May 2007 22:27:17 Greg Kellum wrote:
> > Ah, I have version 0.96.1.D001 of scons installed.
> >
> > $ scons --version
> > SCons by Steven Knight et al.:
> >          script: v0.96.1.D001, 2004/08/23 09:55:29, by knight on
> > casablanca
> >          engine: v0.96.1.D001, 2004/08/23 09:55:29, by knight on
> > casablanca
> >
> > Best,
> > Greg
> >
> > On May 29, 2007, at 21:10, David García Garzón wrote:
> > > Sorry i meant 'scons' program version. 0.9X.XX?
> > >
> > > On Tuesday 29 May 2007 20:55:03 Greg Kellum wrote:
> > >> Hi David,
> > >>
> > >> Okay, here's the full back trace:
> > >>
> > >> IndexError: list index out of range:
> > >>    File "SConstruct", line 253:
> > >>      BUNDLE_ICON='resources/CLAM.icns',
> > >>    File "/System/Library/Frameworks/Python.framework/Versions/2.3/
> > >> lib/
> > >> scons/SCons/Environment.py", line 149:
> > >>      return apply(self.builder, (self.env,) + args, kw)
> > >>    File "/System/Library/Frameworks/Python.framework/Versions/2.3/
> > >> lib/
> > >> scons/SCons/Builder.py", line 557:
> > >>      return self._execute(env, target, source, OverrideWarner(kw))
> > >>    File "/System/Library/Frameworks/Python.framework/Versions/2.3/
> > >> lib/
> > >> scons/SCons/Builder.py", line 546:
> > >>      tlist, slist = self._create_nodes(env, overwarn, target, source)
> > >>    File "/System/Library/Frameworks/Python.framework/Versions/2.3/
> > >> lib/
> > >> scons/SCons/Builder.py", line 489:
> > >>      t_from_s = slist[0].target_from_source
> > >>
> > >> Um...  The SConstruct file must be the current file in SVN.  Using
> > >> SVN log, SVN tells me its version r10136 that was checked in by pau
> > >> on 2007-05-23.
> > >>
> > >> Thanks,
> > >> Greg
> > >>
> > >> On May 29, 2007, at 19:59, David García Garzón wrote:
> > >>> On Tuesday 29 May 2007 18:32:38 Greg Kellum wrote:
> > >>>> Hi all,
> > >>>>
> > >>>> I was trying to compile the network editor from the newest SVN
> > >>>> sources
> > >>>> today on my OS-X 10.4 powerbook, but the compile failed.
> > >>>>
> > >>>> After typing in this command:
> > >>>> $ scons install prefix=/Users/greg/Code/CLAM/NetworkEditor/bin
> > >>>> clam_prefix=/usr/local
> > >>>>
> > >>>> I got this error:
> > >>>>
> > >>>> Loading qt4 tool...
> > >>>> Loading nsis tool...
> > >>>> Loading Bundle tool
> > >>>> Lodading dmg tool...
> > >>>> Version:  1.0.1
> > >>>> Package version:  1.0.1~svn10153
> > >>>> IndexError: list index out of range:
> > >>>>   File "SConstruct", line 253:
> > >>>>     BUNDLE_ICON='resources/CLAM.icns',
> > >>>>   File
> > >>>> "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
> > >>>> scons/SCons/E
> > >>>> nvironment.py", line 149:
> > >>>>
> > >>>> Um...  I checked to see whether the file 'resources/CLAM.icns' was
> > >>>> there,
> > >>>> because that's apparently where the compilation failed, and it is
> > >>>> there.
> > >>>> So, I don't know what is happening here...  Does anyone know what
> > >>>> might be
> > >>>> causing this problem?
> > >>>
> > >>> Greg, could you send the full backtrace? Is it interesting to know
> > >>> in which
> > >>> function has failed. The SConstruct version is also interesting to
> > >>> know.
> > >>>
> > >>>> And a more general question:  Why is it that CLAM uses scons
> > >>>> rather than
> > >>>> the ubiquitous make command?
> > >>>
> > >>> We have changed several times of build system. The former were make/
> > >>> autotools
> > >>> based. Belive me, it was a hell. SCons has its pitfalls but we are
> > >>> not having
> > >>> a half of the problems we had. And, besides that it works for
> > >>> Visual in
> > >>> Windows as well as in Mac. We can use python to do the tricky work
> > >>> instead
> > >>> using the obscure m4 macro language. It allows us to keep the
> > >>> platform
> > >>> dependant part very low, and by adding tools we can extend a lot the
> > >>> functionality (qt4, bundles, dmg's...). And last but not least it
> > >>> forces
> > >>> users to give us feedback when they get stuck ;-)
> > >>>
> > >>> David.