Hi,
it seems there's an issue with using $ENV{something} under windows, as
can be read here and followups:
http://mail.kde.org/pipermail/kde-buildsystem/2006-February/001083.html
The problems is that if the environment variable contains backslahes (and
maybe spaces), it breaks the dependency scanning of cmake, i.e.
dependencies are not scanned. This has been reported for nmake.
A workaround is to replace all backslahes to forward slashes using
string(regex replace ...)
Is this a bug or a feature ?
Bye
Alex
--
DSL-Aktion wegen großer Nachfrage bis 28.2.2006 verlängert:
GMX DSL-Flatrate 1 Jahr kostenlos* http://www.gmx.net/de/go/dsl
_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake
