[cmake-developers] Fwd: Bug#414188: cmake 2.4.4 shouldn't be shipped with Etch

Alexander Neundorf neundorf at kde.org
Sat Mar 10 04:08:30 EST 2007


On Friday 09 March 2007 22:44, Andy Cedilnik wrote:
> From: Andreas Pakulat <apaku at gmx.de>
> Package: cmake
> Version: 2.4.4-1
> Severity: grave
> Justification: renders package unusable
> Hi,
> this bugreport is meant to make clear that CMake 2.4.4 shouldn't be
> shipped with Etch as that release contains some serious bugs. CMake
> 2.4.5 was released shortly after 2.4.4 to fix those bugs and should be
> moved to Etch before the release.
> See
> http://www.cmake.org/pipermail/cmake/2006-November/012110.html
> http://lists.kde.org/?l=kde-core-devel&m=117346555019037&w=2
> for more information about the bugs.

I didn't follow 2.4.4 to closely, for me it seemed to work.
How critical were these bugs ?

* Fix problem with LIBRARY_OUTPUT_PATH and linking to a dll foo.dll.lib
  instead of foo.lib

Killer on windows AFAIK, that's why KDE can say 2.4.4 is the minimum required 

* Do not depend on optimized libraries for a debug build and visa versa.

Did this affect all OSs ? In which way, did it fail if I wanted to do a 
release build and the debug libs were not there ?

* Fix target name matching custom command output conflict.

This sounds like a real problem for all platforms, right ?


Maybe one of you can go there and explain in detail what was broken in 2.4.4 ?

Work: alexander.neundorf AT jenoptik.com - http://www.jenoptik-los.de
Home: neundorf AT kde.org                - http://www.kde.org
      alex AT neundorf.net               - http://www.neundorf.net

More information about the cmake-developers mailing list