On 11/22/2011 9:31 AM, Stephen Kelly wrote:
CMake Error: INSTALL(EXPORT twoDeps ...) includes target libtwo which
requires target libone that is not in the export set.
How can we resolve this?
http://public.kitware.com/Bug/view.php?id=12588
Brad asked to bring this up on the list for
Brad King wrote:
On 11/22/2011 9:31 AM, Stephen Kelly wrote:
CMake Error: INSTALL(EXPORT twoDeps ...) includes target libtwo
which requires target libone that is not in the export set.
How can we resolve this?
http://public.kitware.com/Bug/view.php?id=12588
Brad asked to bring this up on
On 11/22/2011 10:03 AM, Stephen Kelly wrote:
Brad King wrote:
We will have to require that the install(EXPORT)
commands be invoked in dependency order (ex. A before B). That way when
the command installing ExportB is writing library B's dependency on A, it
can transform the name using the
On Tuesday 22 November 2011, Stephen Kelly wrote:
On 11/10/2011 10:16 PM, Alexander Neundorf wrote:
On Wednesday 02 November 2011, David Faure wrote:
On Monday 31 October 2011 21:47:31 Alexander Neundorf wrote:
On Monday 31 October 2011, David Faure wrote:
This is a typical (kde) case
On Tuesday 22 November 2011, Brad King wrote:
On 11/22/2011 10:03 AM, Stephen Kelly wrote:
Brad King wrote:
We will have to require that the install(EXPORT)
commands be invoked in dependency order (ex. A before B). That way when
the command installing ExportB is writing library B's
On 11/22/2011 06:20 PM, Alexander Neundorf wrote:
Using Qt5 or Qt4 ?
Qt4.
There seems to be several problems:
* KDE does include foo.moc if it wants the header file to be moc'd.
This is 'incorrect' compared to what qmake expects, which would be a
moc_foo.cpp include.
Yes.
* Some places
On Tuesday 22 November 2011, Stephen Kelly wrote:
On 11/22/2011 06:20 PM, Alexander Neundorf wrote:
Using Qt5 or Qt4 ?
Qt4.
There seems to be several problems:
* KDE does include foo.moc if it wants the header file to be moc'd.
This is 'incorrect' compared to what qmake expects,
Alexander Neundorf wrote:
On Tuesday 22 November 2011, Brad King wrote:
On 11/22/2011 10:03 AM, Stephen Kelly wrote:
Brad King wrote:
We will have to require that the install(EXPORT)
commands be invoked in dependency order (ex. A before B). That way
when the command installing ExportB
On 11/22/2011 07:10 PM, Alexander Neundorf wrote:
find #include (.*).moc - generate moc for \\1.cpp
Was there a reason for preventing this?
We can do that, but how can that work ?
I mean, this will generate code for a class which is declated in a different
source file, so it is unknown in
On Tuesday 22 November 2011, Alexander Neundorf wrote:
On Tuesday 22 November 2011, Stephen Kelly wrote:
...
This is not uncommon in both KDE and in Qt itself, or any other project
where it makes sense to put a QObject-inherited class in the _p.h as an
internally used class. See for
On 11/22/2011 07:37 PM, David Faure wrote:
On Tuesday 22 November 2011 14:33:25 Stephen Kelly wrote:
I think in many cases,
fixing KDE will just be removing the explicit include foo.moc which is
intended to run moc on foo.h, and let the automatic moc'ing do the work.
No, to include
On 2011-11-17, at 3:59 PM, Brad King wrote:
On 11/17/2011 3:19 PM, Alexandru Ciobanu wrote:
I was able to make CMake use TRE, by changing the
RegularExpression.{cxx,hxx.in} files.
Those are down in Source/kwsys which is a directory shared by
projects other than just CMake. We cannot
On Tuesday 22 November 2011, Stephen Kelly wrote:
Alexander Neundorf wrote:
On Tuesday 22 November 2011, Brad King wrote:
On 11/22/2011 10:03 AM, Stephen Kelly wrote:
Brad King wrote:
We will have to require that the install(EXPORT)
commands be invoked in dependency order (ex. A
On Tuesday 22 November 2011, Stephen Kelly wrote:
On 11/10/2011 10:16 PM, Alexander Neundorf wrote:
...
Please give the RestoreAutmocKDECompatibility branch on cmake stage a
try. It should work again, but print a warning if a file includes a
moc_foo.cpp, but no foo.moc, and contains a
On Mon, Nov 14, 2011 at 08:18:16AM +0100, Rolf Eike Beer wrote:
diff --git a/Modules/Compiler/GNU.cmake b/Modules/Compiler/GNU.cmake
index 8d6f5df..bdcaf9d 100644
--- a/Modules/Compiler/GNU.cmake
+++ b/Modules/Compiler/GNU.cmake
@@ -24,6 +24,15 @@ macro(__compiler_gnu lang)
On Tuesday 22 November 2011, Peter Collingbourne wrote:
On Tue, Nov 15, 2011 at 06:54:01PM +0100, Nicolas Desprès wrote:
On Tue, Nov 15, 2011 at 5:29 PM, Bill Hoffman
bill.hoff...@kitware.comwrote:
On 11/11/2011 9:36 PM, Peter Collingbourne wrote:
Note that this generator is *nix only
Alexander Neundorf wrote:
Test added, works.
What is not working right now is including someotherfile.moc. I could add
special handling for including thisfile_p.moc (as opposed to
moc_thisfile_p.cpp, which works).
Yes, this is the issue that makes the build break in the frameworks branch.
On 11/22/2011 08:43 PM, Alexander Neundorf wrote:
On Tuesday 22 November 2011, Stephen Kelly wrote:
On 11/10/2011 10:16 PM, Alexander Neundorf wrote:
...
Please give the RestoreAutmocKDECompatibility branch on cmake stage a
try. It should work again, but print a warning if a file includes a
On Tuesday 22 November 2011, Stephen Kelly wrote:
On 11/22/2011 08:43 PM, Alexander Neundorf wrote:
On Tuesday 22 November 2011, Stephen Kelly wrote:
On 11/10/2011 10:16 PM, Alexander Neundorf wrote:
...
Please give the RestoreAutmocKDECompatibility branch on cmake stage a
try. It
On 11/22/2011 1:50 PM, Alexandru Ciobanu wrote:
As Brad King suggested, instead of changing the files in Source/kwsys/,
I created a wrapper class and made all the calls go through it.
Thanks.
I also added the TRE library to Utilities/cmtre, and added CMAKE_USE_SYSTEM_TRE.
I added the patch
On 11/22/2011 10:03 PM, Alexander Neundorf wrote:
Now when I try to build the frameworks branch using the cmake next
branch, I get:
AUTOMOC: error:
/home/stephen/dev/src/kf5/tier1/libkcoreaddons/src/io/kdirwatch.cpp: The
file includes the moc file kdirwatch_p.moc, which seems to be the moc
file
I also added the TRE library to Utilities/cmtre, and added
CMAKE_USE_SYSTEM_TRE.
I added the patch to the bug tracker:
http://public.kitware.com/Bug/view.php?id=12381
Please add a note there indicating the CMake version (git commit sha1)
on which the patch was based. Otherwise I
On 21.11.11 17:37:14, Robert Dailey wrote:
On Mon, Nov 21, 2011 at 5:32 PM, John Drescher dresche...@gmail.com wrote:
Yes it is 100% reproducible.
I don't know if telling someone to send reports to Microsoft and have
them
fix the problem is the most reasonable solution.
Isn't
On 11/22/2011 09:28 AM, Mikhail Artemiev wrote:
I don't see a BUILD_CursesDialog entry in my CMakeCache.txt file.But a
CURSES_NCURSES_LIBRARY entry exists, and it point to
/usr/lib/libncurses.so (which exists too).When I try to add a string
BUILD_CursesDialog:BOOL=ON intoCMakeCache.txt by hand
In your bootstrap log, do you see something like the following?
Curses libraries were not found. Curses GUI for CMake will not be built.
Yes. But I don't understand. The curses library was installed.
My LD_LIBRARY_PATH is
$echo $LD_LIBRARY_PATH
/usr/lib
What's wrong?
Mikhail
--
Powered by
On 11/22/2011 10:58 AM, Mikhail Artemiev wrote:
In your bootstrap log, do you see something like the following?
Curses libraries were not found. Curses GUI for CMake will not be built.
Yes. But I don't understand. The curses library was installed.
My LD_LIBRARY_PATH is
$echo
Hi,
I'm trying to create an OSX Application Bundle but like to include the
documentation in a separate directory outside the app bundle but still in the
dmg. Currently cpack installs all components into the app
(CPACK_BUNDLE_COMPONENT_INSTALL ignored). Now for this to work I guess I would
Hi Community,
In the large project we a having periodic taks which build a couple of
projects and store the result of the build in one specific place.
Once it's build the rest of the team can use this artifacts becouse
those are exported by using of export(TARGETS ...)
Since the others refer
Hi Community,
I could not found any other possibilites to set some global variable
than using a cache variable. Even if this is not nice sometimes you
need to have a global variable.
So I would like to ask about advice in this area:
1) Is this the real use case for cache, so to use it as a
Am 22.11.2011 11:42, schrieb t m:
Hi Community,
In the large project we a having periodic taks which build a couple
of
projects and store the result of the build in one specific place.
Once it's build the rest of the team can use this artifacts becouse
those are exported by using of
On 11/22/2011 11:51 AM, t m wrote:
Hi Community,
I could not found any other possibilites to set some global variable
than using a cache variable. Even if this is not nice sometimes you
need to have a global variable.
So I would like to ask about advice in this area:
1) Is this the real
Hi,
I am currently generating sub projects with cmake using the add_subdirectory
command together with the Xcode generator. It works, but the top level Xcode
project includes the sources and targets of all the sub projects. Is it
possible to make it reference the actual Xcode sub projects
Hi,
CMake doesn't support Xcode workspaces like it does Visual Studio solutions.
But you can still define multiple PROJECT()'s that will all be visible and
buildable (via the scheme selector) in the IDE.
In our setup, we have a bunch of apps and a library, in the top level
CMakeLists.txt we
I'm sorry if that sounded flippant... but I'm 100% serious. I used to
work there, and they take the crash reports very seriously, and they
actually do get the majority of them fixed eventually. But if you
don't send them in, then they don't know about them.
Also: I've simply never heard this
Use the cache only if the values need to be persistent. Otherwise I
recommend using a GLOBAL property. See set_property() and get_property().
Michael
Thank you Michael. Looks good. So let me summarize. The workflow
should looks like follow:
1. Top Level CMakeLists.txt:
add_subdirectory( foo
No problem. I'll send a crash report to MS and see what I can figure out. I
assume I need to report the crash on the MSDN forums? Never reported a MS
bug before so not sure.
Thanks for the help everyone.
-
Robert Dailey
On Tue, Nov 22, 2011 at 6:52 AM, David Cole david.c...@kitware.com
How can I get the cmake xcode generator to add a /include folder to
generated projects? The cmakelists contain these directives:
SET(${this_target}_HEADER_FILES ./a.h ./b.h)
SET_SOURCE_FILES_PROPERTIES(${this_target}_HEADER_FILES PROPERTIES
HEADER_FILE_ONLY TRUE)
LIST(APPEND
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Robert Dailey
Sent: Dienstag, 22. November 2011 14:33
To: David Cole
Cc: CMake ML
Subject: Re: [CMake] VC2010 Express crashing
No problem. I'll send a crash report to MS and see what I can figure out. I
assume I need
I have my own macro that I use for this:
MACRO (cmp_IDE_SOURCE_PROPERTIES SOURCE_PATH HEADERS SOURCES INSTALL_FILES)
if (${INSTALL_FILES} EQUAL 1)
INSTALL (FILES ${HEADERS}
DESTINATION include/${SOURCE_PATH}
COMPONENT Headers
)
On 11/22/2011 02:14 PM, t m wrote:
Use the cache only if the values need to be persistent. Otherwise I
recommend using a GLOBAL property. See set_property() and get_property().
Michael
Thank you Michael. Looks good. So let me summarize. The workflow
should looks like follow:
1. Top
Hello @everyone,
I want to use cmake and make from the command line (without Xcode) to
build an Mac OS X app which make use of the new sandboxing feature.
I added the following lines, but in the activity monitor the app is still
not sandboxed:
IF(APPLE)
excellent suggestion, i will try it out. thank!
On 22/11/2011 14:29, Michael Jackson wrote:
I have my own macro that I use for this:
MACRO (cmp_IDE_SOURCE_PROPERTIES SOURCE_PATH HEADERS SOURCES INSTALL_FILES)
if (${INSTALL_FILES} EQUAL 1)
INSTALL (FILES ${HEADERS}
I have not heard of anybody building a Sandboxed app using CMake yet.
What are the requirements for a Sandboxed app? Is there a
documentation page from Apple that describes what needs to be in the
Info.plist to support Sandboxing?
Thx,
David
On Tue, Nov 22, 2011 at 10:44 AM, NoRulez
On Tue, 22 Nov 2011 11:45:29 -0500, David Cole said:
What are the requirements for a Sandboxed app? Is there a
documentation page from Apple that describes what needs to be in the
Info.plist to support Sandboxing?
The main doc is here:
Hi Sean,
did you know if I also need special compiler and/or linker flags?
Best Regards
-Ursprüngliche Nachricht-
Von: Sean McBride [mailto:s...@rogue-research.com]
Gesendet: Dienstag, 22. November 2011 17:56
An: David Cole; NoRulez
Cc: CMake MailingList
Betreff: Re: [CMake] CMake and
On Tue, 22 Nov 2011 18:35:42 +0100, NoRulez said:
did you know if I also need special compiler and/or linker flags?
That's more of an Xcode question than a CMake question... IIRC, no you don't.
You just need to add your entitlements file and codesign. But it's been a few
months since I
IIRC, no you don't
Thanks
This means that I only have to add the following parameters to my codesign
call: --entitlements MyEntitlements.plist
Is this correct? Because I already tried this but then if I launch my app
the application crashes.
The file MyEntitlements.plist contains:
?xml
Hi everyong:
I wanted to learn C++ programming with ITK under linux, does any tell me what
softwares/packages that I need to install?
I am running a Centos 64-bit linux system.
Thanks,
ping wang --
Powered by www.kitware.com
Visit other Kitware
http://nobiofuel.com/affiliate/plugins/SignupActionCommissions/smmfkro.htm
--
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
As we pointed out in the bug thread located at
https://bugs.launchpad.net/ubuntu/+source/phonon/+bug/893170
the FindPhonon script is not portable to Windows. I agree with André's
comment: the source of the problem is the Ubuntu way of distributing
Qt4 and Phonon.
We also have to keep in mind
On Tuesday, November 22, 2011 02:34:55 pm Félix C. Morency wrote:
As we pointed out in the bug thread located at
https://bugs.launchpad.net/ubuntu/+source/phonon/+bug/893170
the FindPhonon script is not portable to Windows. I agree with André's
comment: the source of the problem is the
Hi all,
I don't know if anybody would find this useful or not, but I thought I'd let
everybody know about it and if somebody would like to use it, I can figure out
the best way to get it out there.
We have a fairly extensive python library that we use to setup our code and
manipulate our
Hello!
Thank you for the help.
Here is a part of my CMakeCashe.txt:
// ---
//Path to a file.
CURSES_CURSES_H_PATH:PATH=/usr/include
//Path to a library.
CURSES_CURSES_LIBRARY:FILEPATH=/usr/lib/libcurses.so
//Path to a library.
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 3bbe46daa27a2f405bf97622ad30fd6090e2958e (commit)
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, next has been updated
via a4d31477cfb1cc371e5d7387d742dbe6df838005 (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 31a9140041a1dd89a02f5aeef9e1ca8785f7 (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 2e84d8e613c22677e30414c236dd4f106fdc9a97 (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 d7cb90e1bb3747876c53f2f006d6b5ce5399c22f (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 fe18977b5f4e12e07dd4693a038b5b407ee0a0c2 (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 e8fc3bc8d04c8cf64f4c7ed3816126777925660b (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 636740c478068685727ffe03f6e469418ca42282 (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 e9547efa96ab8f1b28914749fd80dfa7d43ca998 (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 f4e266f41fd0bf390f9e344dd14f870116f6b772 (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 f0419b439a0ae8945cc39fbae22ea83ad7f0af74 (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 7db42fc2559ec2692c36cf25f781f50dd48b7f44 (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 4d5ece3c047ec2a5d56e03888116a430ecf2a4cc (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 99966be1f7e2497bfca909db9232e64351687865 (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 07992233965dc71ab03bfccc79179176996454b3 (commit)
via
68 matches
Mail list logo
