>After copying the libraries to c:\program files\kdewin32, I get similar
>problems with the other libraries, like libz.lib. They seem to be expected
>in c:\program files\gnuwin32 or something. I have them in
>d:\devel\local\{lib,include}, which are in the default MSVC search paths
>defined by $LIB and $INCLUDE. These directories should also be searched for
>required libraries. Or maybe I'm missing something and there's already some
>env.variable which I can set to tell CMake where additional libraries can 
> be found?

You could:
1.) use cmakesetup and modify the directories for each library location
2.) modify the cmake cache by hand

Is there some reason for treating kdewin32 as a seperate dependency? it
seems like you could add:

IF (WIN32)
   IF (NOT KDEWIN32_FOUND)
      add_subdirectory( win )

before any of the other subdirectories (or perhaps after cmake/) and make
this a bit more straightforward. Unless, of course, there's a good reason
not to.



_______________________________________________
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem

Reply via email to