[cmake-developers] [CMake 0012622]: Unable To Find Freetype On Windows

2011-12-13 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
http://public.kitware.com/Bug/view.php?id=12622 
== 
Reported By:Ryan H. Kawicki
Assigned To:
== 
Project:CMake
Issue ID:   12622
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2011-12-13 03:24 EST
Last Modified:  2011-12-13 03:24 EST
== 
Summary:Unable To Find Freetype On Windows
Description: 
With the default install of Freetype on Windows, CMake is unable to set the
variable FREETYPE_INCLUDE_DIR_ft2build.  This is very similar to 0009780.  This
use to be in.  CMake 2.8.5 use to define PATH_SUFFIXES include, but this is no
longer present in 2.8.6.

Additional Information: 
Also reported in 0009780.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2011-12-13 03:24 Ryan H. KawickiNew Issue
==

--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


[cmake-developers] [CMake 0012625]: FindLAPACK does not find pthreads with MKL

2011-12-13 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
http://public.kitware.com/Bug/view.php?id=12625 
== 
Reported By:tgallagher
Assigned To:
== 
Project:CMake
Issue ID:   12625
Category:   Modules
Reproducibility:always
Severity:   major
Priority:   normal
Status: new
== 
Date Submitted: 2011-12-13 13:37 EST
Last Modified:  2011-12-13 13:37 EST
== 
Summary:FindLAPACK does not find pthreads with MKL
Description: 
When trying to use FindLAPACK with Intel MKL, it does not include the pthreads
library in the libraries required despite the find_package(Threads).
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2011-12-13 13:37 tgallagher New Issue
==

--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


Re: [cmake-developers] Adding macro cmake_print_variables(var1 var2 ... varN) ?

2011-12-13 Thread Alexander Neundorf
On Sunday 11 December 2011, Alexander Neundorf wrote:
 Hi,
 
 I have a small macro/function which I need often during buildsystem
 debugging:
 
 function(PRINT_VARIABLES)
set(msg )
foreach(var ${ARGN})
   if(msg)
  set(msg ${msg} ; )
   endif()
   set(msg ${msg}${var}=\${${var}}\)
endforeach()
message(STATUS ${msg})
 endfunction()
 
 
 it prints the values of the variables given as arguments.
 Example:
 
 print_variables(CMAKE_C_COMPILER
 CMAKE_MAJOR_VERSION
 THIS_ONE_DOES_NOT_EXIST)
 
 Gives:
 -- CMAKE_C_COMPILER=/usr/bin/gcc ; CMAKE_MAJOR_VERSION=2 ;
 THIS_ONE_DOES_NOT_EXIST=
 
 
 Ok to add to git ?
 Or should this better be
 message(VARIABLES CMAKE_C_COMPILER
   CMAKE_MAJOR_VERSION
   THIS_ONE_DOES_NOT_EXIST)
 
 Or not at all ?
 Then I'll put it in extra-cmake-modules, but it seems to generic that I
 think it makes sense to have it in cmake directly.

So, ok to add ?
Or should I wait until after 2.8.7 ?

Alex
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


Re: [cmake-developers] Adding macro cmake_print_variables(var1 var2 ... varN) ?

2011-12-13 Thread Eric Noulard
2011/12/11 Eric Noulard eric.noul...@gmail.com:
 List was dropped intentionally

Just realized I wrote the opposite of what I meant ...

 -- Forwarded message --
 From: Eric Noulard eric.noul...@gmail.com
 Date: 2011/12/11
 Subject: Re: [cmake-developers] Adding macro
 cmake_print_variables(var1 var2 ... varN) ?
 To: neund...@kde.org


 2011/12/11 Alexander Neundorf neund...@kde.org:
 Hi,

 I have a small macro/function which I need often during buildsystem 
 debugging:

 function(PRINT_VARIABLES)
   set(msg )
   foreach(var ${ARGN})
      if(msg)
         set(msg ${msg} ; )
      endif()
      set(msg ${msg}${var}=\${${var}}\)
   endforeach()
   message(STATUS ${msg})
 endfunction()


 it prints the values of the variables given as arguments.
 Example:

 print_variables(CMAKE_C_COMPILER
                CMAKE_MAJOR_VERSION
                THIS_ONE_DOES_NOT_EXIST)

 Gives:
 -- CMAKE_C_COMPILER=/usr/bin/gcc ; CMAKE_MAJOR_VERSION=2 ;
 THIS_ONE_DOES_NOT_EXIST=

 pretty handy.

 Ok to add to git ?

 May be in a specific separate file like

 CMakeScriptsDebuggingTools.cmake

 (or some less lengthy name)
 one may include ?

 Or should this better be
 message(VARIABLES CMAKE_C_COMPILER
                  CMAKE_MAJOR_VERSION
                  THIS_ONE_DOES_NOT_EXIST)

 Nope I wouldn't vote for that one.
 How would you print

 message(VARIABLES BLAH  CMAKE_C_COMPILER)
 and
 message(VARIABLES BLAH  CMAKE_C_COMPILER)

 what you be nice as a built-in is something like

 trace_var(CMAKE_C_COMPILER)

 which would make the concerned VAR to be traced each time
 it is touched (read or written) by a script.
 That said we are far away from your initial need.

 and... I'm not volunteering to develop that :-(

 Then I'll put it in extra-cmake-modules, but it seems to generic that I think
 it makes sense to have it in cmake directly.
 --
 Erk
 Membre de l'April - « promouvoir et défendre le logiciel libre » -
 http://www.april.org


 --
 Erk
 Membre de l'April - « promouvoir et défendre le logiciel libre » -
 http://www.april.org



-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


Re: [cmake-developers] Adding macro cmake_print_variables(var1 var2 ... varN) ?

2011-12-13 Thread Brad King

On 12/13/2011 3:34 PM, Alexander Neundorf wrote:

So, ok to add ?


The macro is so simple it can easily be included in any project that
needs it.  People will want different formats and custom behavior.
I don't think it belongs upstream.

-Brad
--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


[cmake-developers] [PATCH] Remove the apparently outdated README in Source/QtDialog.

2011-12-13 Thread Raphael Kubo da Costa
Qt has been LGPL-licensed for a few years, so the clause mentioning only
developers with a paid Qt license can change the code seems to be
outdated.
---
 Source/QtDialog/README |3 ---
 1 files changed, 0 insertions(+), 3 deletions(-)
 delete mode 100644 Source/QtDialog/README

diff --git a/Source/QtDialog/README b/Source/QtDialog/README
deleted file mode 100644
index 0701a2b..000
--- a/Source/QtDialog/README
+++ /dev/null
@@ -1,3 +0,0 @@
-This is the Qt interface to CMake.  It has a BSD license compatible with the
-Qt license exception.  Only developers with a paid QT license are permitted
-to make changes to this code.  Small patches and bug fixes can 
-- 
1.7.8

--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


[cmake-developers] [PATCH] QtDialog: Set Ctrl+Q as the shortcut for quitting the program.

2011-12-13 Thread Raphael Kubo da Costa
QKeySequence::Quit does not work on all platforms, and since it
translates to Ctrl+Q on all platforms where it does work, Ctrl+Q was
hardcoded instead.
---
 Source/QtDialog/CMakeSetupDialog.cxx |2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/Source/QtDialog/CMakeSetupDialog.cxx 
b/Source/QtDialog/CMakeSetupDialog.cxx
index 1c058d3..338eaff 100644
--- a/Source/QtDialog/CMakeSetupDialog.cxx
+++ b/Source/QtDialog/CMakeSetupDialog.cxx
@@ -26,6 +26,7 @@
 #include QMimeData
 #include QUrl
 #include QShortcut
+#include QKeySequence
 #include QMacInstallDialog.h
 
 #include QCMake.h
@@ -99,6 +100,7 @@ CMakeSetupDialog::CMakeSetupDialog()
   QObject::connect(this-DeleteCacheAction, SIGNAL(triggered(bool)),
this, SLOT(doDeleteCache()));
   this-ExitAction = FileMenu-addAction(tr(Exit));
+  this-ExitAction-setShortcut(QKeySequence(Qt::CTRL + Qt::Key_Q));
   QObject::connect(this-ExitAction, SIGNAL(triggered(bool)),
this, SLOT(close()));
 
-- 
1.7.8

--

Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers