The FindKDE3.cmake module doens't find all that is needed to build a program. This is because it looks in the following dirs: $ENV{KDEDIR}/include /opt/kde/include /opt/kde3/include /usr/local/include /usr/include/ /usr/include/kde /usr/local/include/kde Possible solutions: 1. Add /usr/kde/3.{3,4,5}/include to FindKDE3.cmake (Note: there are some other dirs which should be added too.) 2. Make a kde session set the $ENV{KDEDIR} (This isn't done at my system, could be my fault. I'd then like to here how to solve that).
what app do you try to build? And why does it not use the kde eclass that sets the correct environment variable?
Ah that's the problem =). I'm not using an ebuild. I'm working on kpilot-trunk and kde4 so there are no ebuilds for that *yet*. I edited the file so that's working for now. IMHO that CMake *also* should work when no ebuild is used. It's a build tool after all =)
well, ask the cmake developers for help :) I would also appreciate it working out of the box
(In reply to comment #3) > well, ask the cmake developers for help :) > > I would also appreciate it working out of the box > I'm not sure if this is cmake-dev thing. Gentoo did choose to install kde in a *non-standard* dir.
what other way is there to make it properly slottable so that 3.4 can be installed and 3.5 be tested?
(In reply to comment #5) > what other way is there to make it properly slottable so that 3.4 can be > installed and 3.5 be tested? > CMake has a function called $ENV{somevar} which looks up some var from the environment vars. If for example KDEDIR is set to /usr/kde/3.5 as environment var everything should just work fine. But i don't know how to handle this var when more than one KDE version is installed.
have a kde3 app that I can test this against?
No response, works for me and "working on kpilot-trunk and kde4" isn't exactly something we support currently. :-)