MantisBT - CMake
View Issue Details
0011346CMakeModulespublic2010-10-21 10:352016-06-10 14:31
Adam J Richardson #2 
Bill Hoffman 
normalmajoralways
closedmoved 
CMake-2-8 
 
0011346: Syntax errors from pkg-config on Win32
The first time I run CMake on this source tree on Win32 I get a lot of error output (see first link below). Subsequent runs produce the (much shorter) output:

"
C:\Users\buildbot\Reu2\bin\bga120\build\Reu2\cmake>cmake .. -G "MinGW Makefiles"

CMake Error at C:/Programs/CMake28/share/cmake-2.8/Modules/FindPackageHandleStan
dardArgs.cmake:70 (MESSAGE):
  Could NOT find LibXslt (missing: LIBXSLT_INCLUDE_DIR)
Call Stack (most recent call first):
  C:/Programs/CMake28/share/cmake-2.8/Modules/FindLibXslt.cmake:44 (FIND_PACKAGE
_HANDLE_STANDARD_ARGS)
  Reu2/CMakeLists.txt:29 (find_package)


-- Configuring incomplete, errors occurred!

C:\Users\buildbot\Reu2\bin\bga120\build\Reu2\cmake>
"

Both libxml2 and libxslt are installed and working. Also, pkg-config is known to work and return correct results on this system.

Could it be a bug in FindPkgConfig.cmake? Or FindLibXslt.cmake maybe? And why do I get different output on the first run?

The second link below is the CMakeLists.txt file throwing the errors. It is included by other CMakeLists.txt files, I can provide links to those if needed.
https://dreamtrack.dnsalias.com/downloads/cmake-errors.txt [^]
http://dreamtrack.dnsalias.com/fossils/reu2.cgi/artifact?name=f36c765b64f3d0ca700466e175592d2882cb6736 [^]
No tags attached.
Issue History
2010-10-21 10:35Adam J Richardson #2New Issue
2011-01-17 16:49David ColeAssigned To => Bill Hoffman
2011-01-17 16:49David ColeStatusnew => assigned
2016-06-10 14:28Kitware RobotNote Added: 0041755
2016-06-10 14:28Kitware RobotStatusassigned => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0041755)
Kitware Robot   
2016-06-10 14:28   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.