[clam-devel] Network compilation problem

David García Garzón david.garcia at barcelonamedia.org
Fri Apr 23 05:47:28 PDT 2010


On Tuesday 20 April 2010 17:00:20 SAn wrote:
> On Tue, Apr 20, 2010 at 11:30, David García Garzón
> 
> <david.garcia at barcelonamedia.org> wrote:
> > On Monday 19 April 2010 20:38:37 SAn wrote:
> >> On Sun, Apr 18, 2010 at 16:16, Greg <gkjoyce at gmail.com> wrote:
> >> > Hi, so I think I followed the wiki's directions for building on Arch
> >> > correctly but I am getting the following error when I try to build:
> >> > 
> >> > EnvironmentError: No tool named 'qt4': not a Zip file:
> >> >  File "/home/dingus/clam-install/network/src/NetworkEditor-1.4.0/S
> >> >  
> >> >    env.Tool('qt4', toolpath=[clam_sconstoolspath])
> >> >  
> >> >  File "/usr/lib/python2.6/site-packages/SCons/Environment.py", lin
> >> >  
> >> >    tool = apply(SCons.Tool.Tool, (tool, toolpath), kw)
> >> >  
> >> >  File "/usr/lib/python2.6/site-packages/SCons/Tool/__init__.py", l
> >> >  
> >> >    module = self._tool_module()
> >> >  
> >> >  File "/usr/lib/python2.6/site-packages/SCons/Tool/__init__.py", l
> >> >  
> >> >    raise SCons.Errors.EnvironmentError, m
> >> > 
> >> > ==> ERROR: Build Failed.
> >> > 
> >> > I do have QT installed and I am exporting the path to QT.
> >> 
> >> Hi greg, i´ve updated clam AUR packages 5 minutes ago, please try them!
> >> clam 1.4 http://aur.archlinux.org/packages.php?ID=7216
> >> NetworkEditor 1.4  http://aur.archlinux.org/packages.php?ID=31997
> >> 
> >> SAn
> > 
> > Cool. So in archlinux QTDIR should be /usr/lib/qt. Perfect. I wonder, by
> > defining QTDIR, is SHCXXFLAGS needed at all (if so, it is a bug on qt4
> > scons tool i should fix).
> 
> Yes, still needed, because it looks wrong for the headers files.
> 
> > Also, the way you define QT4_MOC has no sense at all, it
> > should define a command and not an option. Does it work?
> 
> I dont know what QT4_MOC means but it works that way.
> 
> Take a look to this thread
> http://www.mail-archive.com/clam@iua.upf.es/msg00274.html
> Maciej (the old manteiner of the packages) tryed but without success to
> """
> export QTINC="/usr/include"
> and
> export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/include"
> """
> He ended patching the sources changing
> #include <QtDesigner/QDesignerCustomWidgetInterface>
> for
> #include <QDesignerCustomWidgetInterface>
> 
> 
> So i figured out that adding "/usr/include" to SHCXXFLAGS and QT4_MOC
> works.
> 
> We should find a way to do it right (TM)

Adding that to SHCXXFLAGS has sense, adding to CPPPATH would be even nicer, 
although, as you say, maybe there is a better way based on pkg-config, and/or 
patching qt4.py to work well without this.

But QT4_MOC as defined in the patch has no sense at all. This option is used 
as moc command (tipical value is '/usr/bin/moc'). I cannot find an explanation 
for it working but that the statement has no effect in the place it is patched 
(so build will work without the statement) or that moc generated files were 
generated in previous executions, (so the patch wouldn't work with a clean 
build).

> > I would also like that as most platforms could rely on pkg-config for qt.
> > Did you have problems using it (by undefining QTDIR)?
> 
> Yes. Its not explicit in the dependences but the meta package
> base-devel (with gcc, fakeroot,
> pkg-config) its a must when you use the AUR repositories (its in the
> AUR guide). So it should be
> using pkg-config and it doesnt find QTDIR.

Forgive the tool about the warning on no QTDIR defined. It shouldn't be needed 
if proper pkg-config files for Qt libs is available.

> Withoud using pkg-config
> CLAM doesnt build because
> it cant find libxml++-2.6 (something like
> /usr/include/libxml++/libxml++.h and not
> /usr/include/libxml++-2.6/libxml++-2.6.h)

I can't get the point on what you say. You can (must) use pkg-config for the 
rest of the packages (libxml++...).


David.



More information about the clam-devel mailing list