Brad King wrote:
Is this a bug in CMake? It seems there is enough information given that
CMake could notice the dependency. But maybe it can't quite do it
because its a separate directory? Maybe cmake can do the
add_dependencies() automatically?
This is expected. You need to do
Stephen Kelly wrote:
but sometimes I
still get build failures due to the dbus xml stuff that I haven't
tracked
down and which are resolved on the next build.
I think this is because I was missing some
add_dependencies(foo dbus_interfaces_xml)
in my app, so hopefully that's resolved
J.S. van Bethlehem wrote:
Dear CMake users,
This week I started to investigate possibilities to move my build-system
over to CMake after hearing a lot of good stories about it. To be
honest, so far I'm still not quite convinced. The learning (I find at
least) is rather steep and the
Hi,
I came up with an idea to simplify the creation of export headers for hidden
visibility by using configure_file.
After implementing it I saw that the idea has come up before :)
http://www.mail-archive.com/cmake@cmake.org/msg27058.html
Please see the attached proof of concept. Could we
Hendrik Sattler wrote:
Really why? There is no dynamic content in such a header file.
I'm not sure what you mean? Could you be more specific?
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
Hi,
The FindQt4 module has this to say about QT_USE_IMPORTED_TARGETS:
If QT_USE_IMPORTED_TARGETS is enabled, the QT_QTFOO_LIBRARY variables are
set to point at these imported targets. This works better in general, and
is also in almost all cases fully backward compatible. The only issue is
Hi,
Thanks for the response. I've got a few followups.
Clinton Stimpson wrote:
The part that is not clear to me is this:
This
means when a project B then uses project A, these imported targets must
be created again, otherwise e.g. Qt4__QtCore will be interpreted as
name of a library
Clinton Stimpson wrote:
#
http://mail.kde.org/pipermail/kde-windows/2007-December/001692.html
#
http://lists.trolltech.com/pipermail/qt-interest/2009-July/009829.html
# qt is always compiled with QT_NO_DEBUG under mingw,
# so we need to compile stuff linked against it
# the same or
Clinton Stimpson wrote:
It means the target must be created again with something like
add_library(Qt4::QtCore UNKNOWN IMPORTED)
If GrantleeConfig.cmake were to do this:
SET(QT_USE_IMPORTED_TARGETS 1)
find_package(Qt4 REQUIRED)
then the imported targets would satisfy the Qt4::QtCore
Wups, sent a moment to early...
Stephen Kelly wrote:
Clinton Stimpson wrote:
It means the target must be created again with something like
add_library(Qt4::QtCore UNKNOWN IMPORTED)
If GrantleeConfig.cmake were to do this:
SET(QT_USE_IMPORTED_TARGETS 1)
find_package(Qt4 REQUIRED
Hi,
In my GrantleeConfigVersion.cmake.in I can use ${PACKAGE_FIND_VERSION} which
I presume is filled from the find_package command (I just copied the file
from elsewhere).
Is there an equivalent for COMPONENTS so that if someone does a
find_package(Grantlee COMPONENTS Foo Bar)
my config
Alexander Neundorf wrote:
On Wednesday 22 June 2011, Stephen Kelly wrote:
Hi,
In my GrantleeConfigVersion.cmake.in I can use ${PACKAGE_FIND_VERSION}
which I presume is filled from the find_package command (I just copied
the file from elsewhere).
Is there an equivalent for COMPONENTS so
Clinton Stimpson wrote:
On Wednesday, June 22, 2011 10:01:37 am Stephen Kelly wrote:
Hi,
In my GrantleeConfigVersion.cmake.in I can use ${PACKAGE_FIND_VERSION}
which I presume is filled from the find_package command (I just copied
the file from elsewhere).
Is there an equivalent
Hi Alex, thanks for the more detailed explanation. It is indeed more clear.
However, I still don't think there is a linker error if I omit
QT_USE_IMPORTED_TARGETS from the config file. I tried to re-create the error
condition with a trivial project and could not re-create it.
Alexander
Clinton Stimpson wrote:
Yeah, I just looked again to verify what you are seeing... you don't need
to do this SET(QT_USE_IMPORTED_TARGETS 1)
in GrantleeConfig.cmake, but you can still do
find_package(Qt4 REQUIRED)
to create the imported targets.
Clint
Cool, I'll just do a find_package(Qt4
Clinton Stimpson wrote:
And all unit tests then fail with MinGW. The errorString() reported is:
QDEBUG : TestBuiltinSyntax::testInsignificantWhitespace(insignificant-
whitespace43) Object QObject(0x0) The plugin
'C:/software/grantlee/qtcreator-
build/grantlee/0.1/grantlee_defaulttags.dll
'
Clinton Stimpson wrote:
The output is attached, but I'm not certain it's very helpful. Let me
know if anything else would be useful. I can maybe try to create a
smaller plugin using qt example for easy reproduction of the issue.
What is CMAKE_BUILD_TYPE set to?
I think it should be the
Clinton Stimpson wrote:
On Wednesday, June 22, 2011 01:47:33 pm Stephen Kelly wrote:
Clinton Stimpson wrote:
The output is attached, but I'm not certain it's very helpful. Let me
know if anything else would be useful. I can maybe try to create a
smaller plugin using qt example for easy
Stephen Kelly wrote:
As a workaround, you can enforce a value for CMAKE_BUILD_TYPE if on
Windows
and CMAKE_CONFIGURATION_TYPES is empty. If you enforce that, then you
don't need to have the add_definition(-DQT_NO_DEBUG).
Thanks for the pointer. I'll try setting that in the cache before
Hi,
I'd like to be able to write a macro like this:
macro(my_macro SOME_TARGET)
if (isStaticLibraryTarget(${SOME_TARGET})
message(FATAL This macro can only be used with shared libraries)
endif()
endmacro()
add_library(libshared SHARED shared.cpp)
my_macro(libshared) # Works
David Cole wrote:
The target property TYPE tells you what the type of the library is:
http://cmake.org/cmake/help/cmake-2-8-docs.html#prop_tgt:TYPE
Use:
get_property(type TARGET ${SOME_TARGET} PROPERTY TYPE)
message(type='${type}')
to retrieve the value of the TYPE property.
Tim Gallagher wrote:
Hi,
I asked about this awhile back and haven't had any luck with it, so I'll
try again.
What we are trying to do is have a project (called Utilities) that has a
bunch of targets (the actual utility executables). Let's say there are 4
utils: pre, post, grid, and
NoRulez wrote:
Hi,
i'm trying to convert a qmake project to CMake.
How can i translate CONFIG to CMake or what is the CMake's way of using
the CONFIG variable?
e.g. CONFIG += mylib
Is this the CMake equivalent: SET(mylib TRUE)
No, probably not.
What does CONFIG += mylib do for a
David Cole wrote:
On Tue, Nov 1, 2011 at 4:33 PM, Robert Dailey
rcdai...@gmail.com wrote:
On Tue, Nov 1, 2011 at 3:32 PM, David Cole
david.c...@kitware.com wrote:
Not yet
Meaning there are plans in the works to add such functionality in the
near future?
For now I guess I could actually
David Demelier wrote:
Hello,
I'm creating a library that use a lot of internal code (not static
because it should be visible by other compilation units) so I would like
to don't export any symbols but only the one I want.
Usually you use __declspec(dllexport) for windows but on unix and
Hi,
I didn't time it, but I was able to use ninja with kdelibs and grantlee (my
smaller Qt project).
Clifford Yapp wrote:
In case anybody else wants to give ninja a spin, here's what I did to
test it (using bash as a shell):
git clone git://github.com/martine/ninja.git
git clone -b
Alfa Omega wrote:
Hi everyone,
I'm not quite sure what the correct procedure is for becoming a CMake
contributor, but from what I've read I should send a email here if I want
to add a new module to cmake.
Hi Tomasz,
This page should have all you need to know:
David Cole wrote:
Replies requested. Short replies only. Read on. Just a short reply
with bug numbers or links to the bugs is all we need here. Please move
specific discussions into the bugs themselves or start a new thread to
talk about it... Replies on this thread should just be a collector
Just forwarding to the cmake users list.
Stephen Kelly wrote:
Hi there,
Qt5 generates its own CMake files, which you will be able to use to find
Qt5 and build with it.
That is, you will port from, eg
find_package(Qt4 REQUIRED Core Gui Xml)
to
find_package(Qt5Widgets
Hi,
The documentation says
A package-specific list of components may be listed after the REQUIRED
option or after the COMPONENTS option if no REQUIRED option is given.
http://www.cmake.org/cmake/help/cmake-2-8-docs.html#command:find_package
But it doesn't say why you would want to do that.
Hi,
I've just tagged and tarballed a release candidate of Grantlee version
0.1.0. Grantlee is a Free Software string template system written in Qt and
using CMake for its build system.[1]
Most of my CMake knowledge is about writing simple CMakeLists.txt files to
consume other libraries.
Michael Wild wrote:
On 9. Apr, 2010, at 20:20 , Alexander Neundorf wrote:
[...]
which will create IMPORTED targets with the same names as in the
Grantlee project. So you can then set the variables
set(Grantlee_CORE_LIBRARIES grantlee_core ${QT_QTCORE_LIBRARIES})
Michael Hertling wrote:
Suppose the Qt folks decide that Qt5's core module doesn't need to
be explicitly requested because it is prerequisite for everything
else.
Just to disseminate information here, this is already the case.
You can currently do this:
find_package(Qt5Declarative)
Rolf Eike Beer wrote:
Michael Hertling wrote:
My main conclusion from the above-noted mess among CMake's current
component-aware find modules is that we urgently need a convention
how such modules and config files are intended to work. Hopefully,
we can take a step forward; Qt5's advent is
Michael Hertling wrote:
* Currently there is no Qt5Config.cmake.
Such a thing could probably exist and use the FIND_COMPONENTS to find
what was requested. [...]
Hi there,
Thank you for your insights on this issue. Do you have any other insights
into other issues I raised in the original
Andreas Mohr wrote:
I'd like to add one more dimension to it:
Thanks for the review.
I'd think that Debug/Release isn't all that matters -
what discussions all too conveniently leave out (possibly even the KDE
Wiki-side target config discussion!) is platform-specific handling,
too (Win32 /
Robert Dailey wrote:
http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/3615
This looks like an interesting discussion but seems like it would be a lot
of work to complete. You're really targetting this for 2.8.9?
It's likely to be partly complete by 2.8.9, but I don't know
Michael Jackson wrote:
Linux really wants to have -fPIC for some of my code and I am trying to
detect linux and then add this flag for my project but I am having no
luck.
if (LINUX)
set(CMAKE_CXX_FLAGS ${CMAKE_CSS_FLAGS} -fPIC)
endif()
Is this NOT the way I should be doing this? It
Hi,
For Qt 5 I'm creating IMPORTED targets for all the libraries, which has
several benefits.
I'm not sure if there are any benefits to creating IMPORTED targets for the
executables too? Currently I just create variables with the full paths to
the executables (moc, uic, rcc) instead.
Is
Stephen Kelly wrote:
Hi,
For Qt 5 I'm creating IMPORTED targets for all the libraries, which has
several benefits.
I'm not sure if there are any benefits to creating IMPORTED targets for
the executables too? Currently I just create variables with the full paths
to the executables (moc
' in the cmake files in Qt either.
However, there are issues, see below:
On Tuesday, August 21, 2012 16:52:19 Stephen Kelly wrote:
On Tuesday, August 21, 2012 08:21:01 Clinton Stimpson wrote:
On Tuesday, August 21, 2012 01:32:33 PM Stephen Kelly wrote:
This means adding a string of -L and -l
/libQtCore.so when using QtGui.
To clarify here too, we're talking only about static libraries, not .so files.
Thanks,
Steve.
--
Stephen Kelly stephen.ke...@kdab.com | Software Engineer
KDAB (Deutschland) GmbH Co.KG, a KDAB Group Company
www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46
/development/2012-August/005998.html
Thanks,
--
Stephen Kelly stephen.ke...@kdab.com | Software Engineer
KDAB (Deutschland) GmbH Co.KG, a KDAB Group Company
www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090
KDAB - Qt Experts - Platform-Independent Software Solutions
Robert Dailey wrote:
Could we get a list of all the new generator expressions? Is there
2.8.10 documentation online somewhere that might have them documented?
I don't think there's generated html docs, but here's the new addition to
the INCLUDE_DIRECTORIES target property documentation:
Robert Dailey wrote:
Could we get a list of all the new generator expressions? Is there
2.8.10 documentation online somewhere that might have them documented?
I don't think there's generated html docs, but here's the new addition to
the INCLUDE_DIRECTORIES target property documentation:
Rolf Eike Beer wrote:
$TARGET_PROPERTY:prop = The value of the property prop on
the target on which the generator expression is evaluated.
Then tell me on which target an include_directories is evaluated on ;)
Each of them:
add_executable(foo ${foo_SRCS})
add_library(bar ${bar_SRCS})
Gregoire Aujay wrote:
Hello,
I want to create a module with two symbols exported with visual:
startPlugin
stopPlugin
I wish I could use the convenient GENERATE_EXPORT_HEADER function to do
so. Is there any reason why the GENERATE_EXPORT_HEADER function is
disabled for the MODULE
dcrespol wrote:
Hi, norulez.
With @Thiago: QT_STATICPLUGIN does the trick , what do you mean? How and
where did you use this?
If possible, can you please include both your final plugin and application
CMakeLists.txt files?
It was probably a response to Thiago on the Qt mailing list.
Use
David Doria wrote:
When using automoc, I still have to do:
include_directories(${CMAKE_CURRENT_BINARY_DIR})
so that the compiler can find the MOCed files that get created in the
build directory. Should this be done automatically so there is one
less thing the user has to worry about?
Hi there,
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 be changed
Hi there,
I'm attempting to write a unit test for the Qt 5 ActiveQt module:
https://codereview.qt-project.org/#change,41554
The problem is that I don't have any prior experience with ActiveQt, and in
particular ActiveQt with CMake.
It seems that as part of the build, qmake is invoking the
Pau Garcia i Quiles wrote:
On Tue, Dec 4, 2012 at 11:28 AM, Stephen Kelly
steve...@gmail.com wrote:
Hi there,
I'm attempting to write a unit test for the Qt 5 ActiveQt module:
https://codereview.qt-project.org/#change,41554
The problem is that I don't have any prior experience
Pau Garcia i Quiles wrote:
I would say most people are not using ActiveQt and CMake together, plain
and simple.
For the very few who do, they are probably only using the Qt application
as a client (i. e. load an ActiveX component), not to write servers.
Aha, and the implication is that in
Pau Garcia i Quiles wrote:
On Wed, Dec 5, 2012 at 5:00 PM, Stephen Kelly
steve...@gmail.com wrote:
Pau Garcia i Quiles wrote:
I would say most people are not using ActiveQt and CMake together,
plain and simple.
For the very few who do, they are probably only using the Qt
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
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
be
similar if you wish to try it.
Thanks,
Steve.
From 5dfdb36e378ed81967faae18c0d5ef60bbfde426 Mon Sep 17 00:00:00 2001
From: Stephen Kelly stephen.ke...@kdab.com
Date: Wed, 12 Dec 2012 17:42:53 +0100
Subject: [PATCH] Build with Qt 4 and 5.
---
CMake/ECMQt4To5Porting.cmake| 98
is
attached.
Thanks,
Steve.
From e825f9f4da012bdf4e129aeb238b808c0e714fc4 Mon Sep 17 00:00:00 2001
From: Stephen Kelly stephen.ke...@kdab.com
Date: Wed, 12 Dec 2012 17:42:53 +0100
Subject: [PATCH] Build with Qt 4 and 5.
---
CMake/ECMQt4To5Porting.cmake| 98
Stephen Kelly wrote:
Note that an RC1 was released in the mean-time:
http://qt-project.org/downloads
That does not change anything with regard to the CMake files however.
Qt 5.0 final has now been released :).
http://blog.qt.digia.com/blog/2012/12/19/qt-5-0/
It also does not change
Alan W. Irwin wrote:
If/when that python.org bug is fixed I will look into the
Is it reported? If not it won't get fixed.
I assume you saw this?
http://thread.gmane.org/gmane.comp.science.paraview.user/10956/focus=11019
I wonder if that David reported it either.
Thanks,
Steve.
--
Bill Hoffman wrote:
On 1/5/2013 3:49 PM, Óscar Fuentes wrote:
With the `Unix Makefiles' generator, a foo.i target is generated for
foo.cpp. That's very convenient. However, ninja doesn't list such
targets under `ninja help' and `ninja foo.i' complains about unknown
target.
Is this feature
Óscar Fuentes wrote:
Stephen Kelly steve...@gmail.com writes:
While at it, you comb this thread to see if there are other feature
requests there which are not in the bug tracker:
http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/3471/focus=3475
Good idea.
Apart from
Gregoire Aujay wrote:
Hello,
I am using cmake 2.8.10.2 on windows.
I want a library A to link to a 3rdParty library B. I thought that using
LINK_PRIVATE version of the target_link_libraries function should avoid B
to be in the link interface of A. But if I export A, B's full path is in
Hi,
In Qt 5, we create CMake Config files and ship them with the Qt installation
to make it possible to use Qt 5 with CMake.
Qt on Windows and Mac is packaged with both a debug configuration and a
release configuration, so an IMPORTED library is created with both a DEBUG
location and a
Bogdan Cristea wrote:
Le vendredi 18 janvier 2013 à 15:22 +, Laszlo Papp a écrit :
What is wrong about Stephen's post? It has been working for me in
several projects.
A line like this
find_package(Qt5Declarative)
generates a warning about missing FindQt5Declarative.cmake which is
John Drescher wrote:
The suggestion in the bug report looks somewhat reasonable to me, but
then again, we don't actually create separate debug info, and the
'Release' configuration would be no different to the 'RelWithDebInfo'
configuration, so it's sort of a 'lie'.
The real need for it
Nicolas Tisserand wrote:
Hi,
snip
Hope that helps!
Could you try this instead?
diff --git a/Modules/FindQt4.cmake b/Modules/FindQt4.cmake
index 078c031..4c98a6d 100644
--- a/Modules/FindQt4.cmake
+++ b/Modules/FindQt4.cmake
@@ -965,13 +965,17 @@ if (QT_QMAKE_EXECUTABLE AND QTVERSION)
Nicolas Tisserand wrote:
Hi,
Date: Tue, 26 Feb 2013 20:25:42 +0100
From: Stephen Kelly steve...@gmail.com
Subject: Re: [CMake] QT4 Module Patch Request
To: cmake@cmake.org
Message-ID: kgj27j$m0m$1...@ger.gmane.org
Content-Type: text/plain; charset=ISO-8859-1
Could you try this instead
Orion Poplawski wrote:
In current Fedora, /sbin,/bin, and /lib are symbolic links to /usr/sbin,
/usr/bin, and /usr/lib. This causes problems such as the one outlined
here: https://bugzilla.redhat.com/show_bug.cgi?id=917407
where find_package(PKG NO_MODULE) will find PKGConfig.cmake in
Matthew Woehlke wrote:
Now that 2.8.11 supports interface include_directories on targets, is
there a way to create a library target that can be exported that has no
actual library, but *does* define interface include_directories?
That won't be possible in 2.8.11, but will be possible in the
Alexander Neundorf wrote:
On Thursday 14 March 2013, Robert Maynard wrote:
These changes will be in 2.8.11 RC1 for you to test out.
Cool :-)
Before I merge it into next, could you have a look at the TI_DSP_to_TI
branch, I had some git trouble and I'm not quite sure everything is in
this
Yuchen Deng wrote:
hi, there!
I was reading the release log in here:
http://www.kitware.com/news/home/browse/CMake?
2012_11_07CMake+2.8.10+Just+Released
Add see the parts:
Generator expressions, which are used to introduce conditional statements
at generate time rather than at CMake
Matthew Woehlke wrote:
See subject. I have a target that is the compiled sources from some
stuff generated by Google Protobuf, which means using the headers also
depend on ${PROTOBUF_INCLUDE_DIRS}. I would like to have this be a
SYSTEM include... is this supported?
Nope. It would be possible
Alok Govil wrote:
Hi all,
I had Qt4 functional with CMake, but cannot get Qt5 to work (have upgraded
to the latest version of CMake). I have tried everything I could find
including a prior post on the Cmake mailing list, to no avail.
Here's another relevant link :) :
Jean-Christophe Fillion-Robin wrote:
Hi Folks,
I would like to discussed the usable of export(PACKAGE ...) statement.
Based on my experience, it turns out that exporting the build tree in the
system package registry is a bad idea when building the same package
multiple time as it is done
David Cole wrote:
Two rules:
- Project config files can only go *with* the project.
(VTK and ITK have them. Qt 5 has one. KDE uses them... All the cool
projects have one. :-)
There is an additional note for this rule:
- If a Config file is created, it must be created independent of
clin...@elemtech.com wrote:
I'm playing with some of the new cmake 2.8.11 features and an example I
saw had this:
set_property(TARGET foo PROPERTY
INTERFACE_INCLUDE_DIRECTORIES
$BUILD_INTERFACE:${CMAKE_CURRENT_BINARY_DIR};
${CMAKE_CURRENT_SOURCE_DIR}
Stephen Kelly wrote:
Where did you see the
example above? In an old commit message? It doesn't seem to be in the
code:
Ah, I found and fixed it on the wiki page:
http://community.kde.org/Frameworks/Epics/CMake_target_usage_requirements
Thanks,
Steve.
--
Powered by www.kitware.com
Brad King wrote:
On 04/24/2013 09:11 AM, Paul Smith wrote:
On Wed, 2013-04-24 at 09:02 -0400, John Drescher wrote:
I installed it and it ran one time and I didn't see the error, but it's
intermittent so that's not definitive. Unfortunately one of my cmake
files failed (later on; this is a
Brad King wrote:
$ cmake .. -GXcode
...
CMake Error at CMakeLists.txt:5 (target_link_libraries):
Error evaluating generator expression:
$TARGET_PROPERTY:$$CONFIG:DEBUG:A,INTERFACE_INCLUDE_DIRECTORIES
$TARGET_PROPERTY:tgt,prop expression requires a non-empty target name.
...
I
Brad King wrote:
On 04/25/2013 03:34 AM, Stephen Kelly wrote:
I haven't had time to investigate fully, but this patch should 'fix' the
problem:
[snip]
I'll investigate later to see if it's the right fix and why.
Great! I've turned that patch into this commit:
http://cmake.org/gitweb
Lloyd wrote:
Hi,
I am studying to compile an application using CMake in Cygwin. I am
installing a file using the install command based on the value of
CONFIGURATIONS variable.
May I know the default configuration (debug, release) in cygwin
I get Debug folders in the build directory
Matthias Kretz wrote:
On Thursday 25 April 2013 10:30:14 Bill Hoffman wrote:
On 4/25/2013 10:05 AM, Matthias Kretz wrote:
I'm not sure we're talking about the same thing. I'm talking about
ctest_configure - i.e. before build or tests. IIUC you're talking about
regex matching at
Hi,
I am investigating
https://bugreports.qt-project.org/browse/QTBUG-30938
and I wanted to see what cmake exports when it export() is used with a
framework target. I created a shared library and ran cmake with -GXcode,
then cmake --build ., but it seems to only create a release library. I
Stephen Kelly wrote:
and I wanted to see what cmake exports when it export() is used with a
framework target. I created a shared library and ran cmake with -GXcode,
then cmake --build ., but it seems to only create a release library. I
thought Xcode generated rules for multiple configurations
Stephen Kelly wrote:
or --config Release to build a particular configuration. However, the
debug and release names are the same. I also ran cmake with
-DCMAKE_DEBUG_POSTFIX=Debug
but that didn't make any difference.
This makes a difference for non-frameworks, but does not make
Stephen Kelly wrote:
Is it possible to build multi-config frameworks with cmake at all?
I also notice that the Framework unit test uses
set_target_properties(foo PROPERTIES
FRAMEWORK TRUE
DEBUG_POSTFIX -d
)
but the debug file is called 'foo', not 'foo-d'. If I use
cmake --build
clin...@elemtech.com wrote:
- Original Message -
Stephen Kelly wrote:
Is it possible to build multi-config frameworks with cmake at all?
I also notice that the Framework unit test uses
set_target_properties(foo PROPERTIES
FRAMEWORK TRUE
DEBUG_POSTFIX -d
clin...@elemtech.com wrote:
- Original Message -
clin...@elemtech.com wrote:
- Original Message -
Stephen Kelly wrote:
Is it possible to build multi-config frameworks with cmake at all?
I also notice that the Framework unit test uses
clin...@elemtech.com wrote:
Or
Release/foo.framework/foo
Debug/foo.framework/foo-d
Ok, but the framework version of the linker flags -L,-l are used like
this: -F/path/to/framework -framework foo
which result in the linker would look for this file
/path/to/framework/foo.framework/foo
Bogdan Cristea wrote:
Hi
I have noticed that the latest cmake release, 2.8.11, does not detect
sgemm using check_function_exists macro from mkl_rt.lib library. The error
message says;
Cannot find C:\Program.obj
It seems to me that the paths with spaces are no longer handled correctly.
Bill Hoffman wrote:
On 5/23/2013 1:48 PM, Stephen Kelly wrote:
Hi
I have noticed that the latest cmake release, 2.8.11, does not detect
sgemm using check_function_exists macro from mkl_rt.lib library. The
error message says;
Cannot find C:\Program.obj
It seems to me that the paths
Brad King wrote:
On 05/24/2013 04:24 PM, Brad King wrote:
It does not individually re-quote the library names so when the
generated CMakeLists.txt file is parsed it separates on spaces.
Fixed:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e65ef08b
Great, thanks!
--
Powered by
Brad King wrote:
On 05/24/2013 04:24 PM, Brad King wrote:
It does not individually re-quote the library names so when the
generated CMakeLists.txt file is parsed it separates on spaces.
Fixed:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e65ef08b
This commit causes the build of
Alexander Neundorf wrote:
On Tuesday 20 August 2013, Robert Maynard wrote:
Introduced CMake Policy 21:
It is now an error to use relative paths to include_directories.
Why is this necessary ?
The documentation for this policy says:
The base path for such relative entries is not well
Giordano Khouri wrote:
I'm surprised to see that there's no configuration specific COMPILE_FLAGS.
Please correct me if I'm wrong.
Correct, but not the whole story. When you upgrade to CMake 2.8.12 you can
use the COMPILE_OPTIONS target property.
Jed Brown wrote:
I just upgraded from cmake-2.8.11.2 to 2.8.12 and now get errors when a
comma ',' appears in a linker flag. Test case below. Note that this is
but one of many reasons for a comma to appear in linker flags.
I've pushed a fix candidate:
Jed Brown wrote:
Stephen Kelly steve...@gmail.com writes:
Jed Brown wrote:
I just upgraded from cmake-2.8.11.2 to 2.8.12 and now get errors when a
comma ',' appears in a linker flag. Test case below. Note that this is
but one of many reasons for a comma to appear in linker flags.
I've
Clinton Stimpson wrote:
I have a target where I do this:
SET_TARGET_PROPERTIES(mytarget PROPERTIES LINK_INTERFACE_LIBRARIES )
to hide 3rd party libraries from the link interface.
When I do
if(APPLE)
CMAKE_MINIMUM_REQUIRED(VERSION 2.8.12)
endif()
I get an error at generate time.
Clinton Stimpson wrote:
I'm trying to point out that I did not get a warning when I was using
cmake_minimum_required(VERSION 2.8)
set_target_properties(mytarget PROPERTIES LINK_INTERFACE_LIBRARIES )
with
CMake 2.8.12.
That looks like a bug.
The policy warning is only issued if
1) Both
1 - 100 of 3503 matches
Mail list logo
