[Kde-imaging] Problem Building from SVN

[Angelo Naselli]

> > > make[3]: Entering directory
> > >
> > >> /usr/lib -R /usr/lib -R /usr/lib/qt-3.3/lib -R /usr/X11R6/lib -L/usr/lib
> > >> -L/usr/lib/qt-3.3/lib -L/usr/X11R6/lib plugin_printwizard.lo
> > >> frmprintwizard.lo cropframe.lo tphoto.lo utils.lo
> > >> frmprintwizardbase.lo../../libkipi/libkipi/libkipi.la -lkparts
> > >> -lkdeprint -lkdeui -lkdecore .libs/plugin_printwizard.o(.text+0x2f): In
> > >> function
> > >> `Plugin_PrintWizard::Plugin_PrintWizard(QObject*, char const*,
> > >> QStringList
> > >>
> > >> const&)':
> > >> : undefined reference to `KIPI::Plugin::Plugin(KInstance*, QObject*,
> > >> : char
> > >>
> > >> const*)'
> >
> > did the libkipi get built correctly before the compilation stepped into
> > the kipi-plugins directory?
> >
> 
> Yes libkipi is correctly compiled. The problem come with the first plugin to 
> build.
> 
> Note that if you try to build manually another plugin, this problem exist 
> too !
> 
Hi guys, I had a similar problem compiling (well linking) gwenviev from svn
(mandriva 2005 LE i.e. 10.2).
Now we saw it's a -fvisibility problem.
If you use somewhere KDE_EXPORT you probably has this problem.
Mandriva kde version is a 3.2 patched. so visibilty works, but the test on
kde version could fail.
Now it seems kde developers give a good way to test
gcc visibility (have a look at __KDE_HAVE_GCC_VISIBILITY
into admin/acinclude.m4.in).
If you test the definition of __KDE_HAVE_GCC_VISIBILITY to use
KDE_EXPORT or not should work.
The only dubt i have is for kde version < 3.2 where if I remember well
the KDE_EXPORT was wrongly defined.

HTH,
   Angelo



	

	
		
___________________________________ 
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
http://mail.yahoo.it