On Wednesday 06 August 2008, Ralf Habacker wrote: ... > > The keywords "general", "optimized" and "debug" are handled in > > ------------ > > cmTargetLinkLibrariesCommand::InitialPass(). > > If there is a way that TARGET_LINK_LIBRARIES() ends up e.g. > > with "general;kdecore;debug;debug;kdeui;", i.e. two keywords behind each > > other, then this might cause the problem. The question is, can that > > happen ? It shouldn't. Can you find out whether that happens there ? > > seems not to be. > > > -------------- > > They are also handled in > > cmComputeLinkDepends::AddVarLinkEntries() and > > cmTarget::GatherDependencies(). These two functions may have the same > > issue, i.e. if the arguments they get contains two of the keywords in a > > row it might happen. > > Can check whether that happens ? > > In this place there is some magic with compatibility I don't understand > yet. As there seems not to be a debug mode like qmake or autotools have > the only way to find what's going wrong is to add debug prints on > several places to see what happens inside -
Yes. > but this need cmake to be compilable :-( Which should be the case tomorrow, probably. Alex _______________________________________________ Kde-windows mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-windows
