On Thursday 04 June 2009, Andreas Pakulat wrote: > On 04.06.09 15:11:04, Chris Bruner wrote: > > Andreas Pakulat wrote: > >> On 04.06.09 13:34:48, Chris Bruner wrote: > >>> I'm new to this list so sorry if I'm tramping over old ground, > >>> (didn't see it in the archives) > >>> > >>> Things seem to work fine until: > >>> Linking CXX shared module ../../lib/kdevgdb.so > >>> > >>> /usr/lib/gcc/i686-pc-linux-gnu/4.3.3/../../../../i686-pc-linux-gnu/bin/ > >>>ld: cannot find -lKDE4Workspace__processui > >>> collect2: ld returned 1 exit state > >>> > >>> > >>> This is with gcc 4.3.3-r2 under gentoo. > >>> > >>> Does anyone know what it is looking for and how to provide it? > >> > >> Gentoo broke its kdebase/workspace stuff (no idea how thats called). But > >> they already updated it in the live stuff - or so I heard. > > > > Are you saying that there is actually a file called > > KDE4Workspace__processui in kde but normally under a different name? > > No. Gentoo broke the FindKDE4WorkspaceLibs.cmake file or something > related to that. That file is installed as part of kdebase/workspace and > creates a CMaket target called "KDE4Workspace__processui" that is in > CMake "IMPORT" target and points to the actual library installed > somewhere in your system.
Do you think the error would be easier to understand if the imported target wouldn't be called "KDE4Workspace__processui" but just "processui" ? I added the "KDE4Workspace__" as a prefix for the imported targets to make it clearer where they should come from and also to make it obvious that this is an imported target and not a file on disk. But maybe this actually makes it more confusing for people who don't know the details how it works ? What do you think ? Alex _______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
