[Kde-bindings] building smoke

Arno Rehn arno at arnorehn.de
Mon Sep 28 15:51:53 UTC 2009


On Monday 28 September 2009 15:38:35 Helio Chissini de Castro wrote:
> Em Domingo 27 de setembro 2009, às 10:28:35, você escreveu:
> > On Tuesday 22 September 2009 22:50:31 Helio Chissini de Castro wrote:
> > > Em Segunda-feira 21 de setembro 2009, às 14:05:09, você escreveu:
> > > > On 9/21/09 1:28 AM, "Stefano Crocco" <stefano.crocco at alice.it> wrote:
> > > > > On Sunday 20 September 2009, Arno Rehn wrote:
> > > > >> |Yes, the name generator_smoke.so is used on purpose, since it's a
> > > > >> | plugin and  not a real shared library. QLibrary (with which the
> > > > >> | generator is loaded) tries all possibilities, including
> > > > >> | generator_smoke.so. I don't have a clue why it doesn't work for
> > > > >> | you, but on my machine it does. What revision and what distro do
> > > > >> | you use?
> > > > >
> > > > > I tried again this morning with revision 1026229 with the same
> > > > > results. I'm using Gentoo Linux with the live kde ebuilds.
> > > > >
> > > > > Stefano
> > > >
> > > > Dirk's dashboard for the icecream cluster also is listing this error
> > > > as well, so it's not isolated to Gentoo....
> > >
> > > I know the issue. I start to  have it after clean the system.
> > > Arno, you already have a previous installed bindings, with library in
> > > path, that's why you don't have the issue.
> > >
> > > I tried to solve in the Unix side, using this on main CMakeLists.txt:
> > >
> > > if( UNIX )
> > >    # Generator library is used during compilation. If some environment
> > > not # have previous kdebindings installed, will fail, then we need add
> > > local path
> > >    set( ENV{LD_LIBRARY_PATH} ${CMAKE_CURRENT_BINARY_DIR}/generator/bin
> > > ) endif( UNIX )
> > >
> > >
> > > But seens this is not effective in general.
> > > Maybe link static the library in generator will make the whole process
> > >  easier.
> >
> > Btw, what version of Qt are you using? 4.6 tp1?
> 
> Qt 4.6 from gitorius ( origin )
So this could be the problem. I'm pretty sure that 4.5's QLibrary looks for 
libraries in the same directory that the executable is located in (otherwise 
it wouldn't have worked for me).

-- 
Arno Rehn
arno at arnorehn.de



More information about the Kde-bindings mailing list