On 2012-12-11 08:35, Brad King wrote:
Another idea is to simply not allow both commands to be used on a given
target. Since the new command does not yet exist this cannot break any
existing projects. One must either specify everything by the new command
or everything by the old command.
How
Hi Jakub,
On Fri, Dec 7, 2012 at 4:46 PM, Jakub Zakrzewski jzakrzew...@e2e.ch wrote:
Hi
Did you think about something like this:
ADD_DEFINITIONS (-DBOOST_ALL_NO_LIB)
SET (BOOST_ROOT $ENV{BOOST_ROOT})
SET (Boost_NO_SYSTEM_PATHS ON)
SET (Boost_USE_MULTITHREADED ON)
SET
You can't do it with CMake as-is on a per configuration basis.
On Mon, Dec 10, 2012 at 11:18 PM, Matt Campbell ma...@nvidia.com wrote:
Hi,
** **
In Visual Studio, I can have a project set to build as a static lib in one
configuration and a dynamic lib in another configuration. I
John Drescher wrote:
I emailed before about reviewing Config files that are being shipped with
Qt 5 and got great feedback:
http://thread.gmane.org/gmane.comp.kde.devel.buildsystem/7165/focus=41551
Now that Qt 5 beta 2 is out, I'd like to ask for feedback again on
anything that can still
On Tue, Dec 11, 2012 at 12:02 PM, Stephen Kelly steve...@gmail.com wrote:
John Drescher wrote:
I emailed before about reviewing Config files that are being shipped with
Qt 5 and got great feedback:
http://thread.gmane.org/gmane.comp.kde.devel.buildsystem/7165/focus=41551
Now that Qt 5
Ok, that's the conclusion I came to as well. That being said, CMake's approach
is fine too.
Thanks.
-Matt
From: David Cole [mailto:david.c...@kitware.com]
Sent: Tuesday, December 11, 2012 10:41 AM
To: Matt Campbell
Cc: cmake@cmake.org
Subject: Re: [CMake] static and dynamic libraries based on
On Tue, Dec 11, 2012 at 2:24 PM, John Drescher dresche...@gmail.com wrote:
My goal is to a specific definition to the Debug and RelWithDebInfo
configurations for all targets in the project but not to the Release
configuration when using VisualStudio. I believe that
COMPILE_DEFINITIONSCONFIG
Hello,
I've been using the WinGDB Visual Studio plugin to develop for an embedded
linux board we're making in house. We've got a hacked-together set of CMake
files that generate:
* Make files (which are run using an arm cross-compiler)
* Visual Studio project/solution files
* a WinGDB
Dear CMake experts,
I appreciate your efforts resulting into the introduction of the
CMAKE_[C|CXX]_COMPILER_VERSION variables from CMake version 2.8.10
( http://www.cmake.org/pipermail/cmake/2012-January/048596.html ).
However, I would need also the CMAKE_Fortran_COMPILER_VERSION variable.
John Drescher wrote:
I had some trouble building a x64 version of Qt 5.0 beta2 but then
after getting past that I found out that vtk-5.10.X would not work
with Qt5 so it pretty much ended what I wanted to test since pretty
much all of my current code uses vtk.
I see. I just tried building
In VTK 'master' -- if you turn on the VTK_Group_Qt CMake option, either
in the gui, or by -D on the command line, then all the Qt-related modules
will be enabled.
In VTK 5.10, there were some other configure time options (I'd have to go
look them up or try it out) to control building the
In VTK 5.10, there were some other configure time options (I'd have to go
look them up or try it out) to control building the Qt-related bits...
In vtk-5.X you needed to enable VTK_USE_GUISUPPORT then that gave you
the ability to enable VTK_USE_QT
John
--
Powered by www.kitware.com
Visit
I took a peek at building it earlier with Qt5.
I started making changes and one of the more surprising ones was that
#include QtGui/QWidget
pulled in my Qt4 QWidget from /usr/include/QtGui/QWidget.
Instead of Qt5's QtWidgets/QWidget. That led to confusing linker errors.
I got as far as trying
Question for the VTK list
On Tue, Dec 11, 2012 at 5:34 PM, Clinton Stimpson clin...@elemtech.comwrote:
I took a peek at building it earlier with Qt5.
I started making changes and one of the more surprising ones was that
#include QtGui/QWidget
pulled in my Qt4 QWidget from
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via b575eadcdaf55fa4fe9a9d2dd8cb5e530365eae9 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 7b20f893c28c63a756dfb8a32bf55e964d9b5e8f (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via bc9dcadf19d44173bcc0b6cb99eac4cf5fdae4f0 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via d0369a980c1e9974edd2f6c74b870ac65163 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via e26c1f7fd713e6637e1b487fad601638ef503fb1 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via a88b8c7c587923b76896dd68a1cd8a7479ddaa61 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 716eed936f2429ac3218d20608a7e16bc63c2961 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 0941fe962dedbb5395d336e4c2221df6640f594e (commit)
via
22 matches
Mail list logo
