The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15217
==
Reported By:sudakov_ivan
Assigned To:
On 10/23/2014 10:34 PM, Ben Boeckel wrote:
implies the build isn't getting the include directories plumbed through
properly.
I reproduced it locally far enough to find that kcoreaddons is not
installing headers like include/KF5/KCoreAddons/kpluginfactory.h
when built with 3.1 but is with 3.0.
On 10/24/2014 09:50 AM, Brad King wrote:
With 3.0 we see the list of headers accumulate. With 3.1 just the
first one works and the rest do not.
I bisected it down to:
commit 5abfde6cb8a1ae0b2825797eab6c2e9842eb7c49
Author: Ben Boeckel ben.boec...@kitware.com
Date: Wed Mar 12 14:01:45 2014
On 10/24/2014 10:02 AM, Brad King wrote:
I bisected it down to:
commit 5abfde6cb8a1ae0b2825797eab6c2e9842eb7c49
Author: Ben Boeckel ben.boec...@kitware.com
Date: Wed Mar 12 14:01:45 2014 -0400
cmDefinitions: Don't store parent lookups
When looking up scopes, it is faster to
[ Forward from Ben Cooksley. ]
- Forwarded message from Ben Cooksley bcooks...@kde.org -
Date: Fri, 24 Oct 2014 19:55:23 +1300
From: Ben Cooksley bcooks...@kde.org
To: ben.boec...@kitware.com
Cc: Bill Hoffman bill.hoff...@kitware.com, cmake-developers@cmake.org
On Friday 24 October 2014 10:02:31 Brad King wrote:
On 10/24/2014 09:50 AM, Brad King wrote:
With 3.0 we see the list of headers accumulate. With 3.1 just the
first one works and the rest do not.
I bisected it down to:
commit 5abfde6cb8a1ae0b2825797eab6c2e9842eb7c49
Author: Ben
On Friday 24 October 2014 10:20:42 Brad King wrote:
On 10/24/2014 10:02 AM, Brad King wrote:
I bisected it down to:
commit 5abfde6cb8a1ae0b2825797eab6c2e9842eb7c49
Author: Ben Boeckel ben.boec...@kitware.com
Date: Wed Mar 12 14:01:45 2014 -0400
cmDefinitions: Don't store
On Fri, Oct 24, 2014 at 15:24:57 +0100, Alex Merry wrote:
On Friday 24 October 2014 10:20:42 Brad King wrote:
On 10/24/2014 10:02 AM, Brad King wrote:
commit 5abfde6cb8a1ae0b2825797eab6c2e9842eb7c49
Author: Ben Boeckel ben.boec...@kitware.com
Date: Wed Mar 12 14:01:45 2014 -0400
On Fri, Oct 24, 2014 at 10:54:17 -0400, Ben Boeckel wrote:
On Fri, Oct 24, 2014 at 15:24:57 +0100, Alex Merry wrote:
On Friday 24 October 2014 10:20:42 Brad King wrote:
On 10/24/2014 10:02 AM, Brad King wrote:
commit 5abfde6cb8a1ae0b2825797eab6c2e9842eb7c49
Author: Ben Boeckel
On Fri, Oct 24, 2014 at 11:36:40 -0400, Ben Boeckel wrote:
So after discussion with Brad, this commit breaks other subtle behaviors
as well, so the plan is to just revert it instead and defer its
optimizations until after 3.1 once proper tests are in place (more under
development now).
There
Documentation added, authorship fixed, a couple of commits squashed.
2014-10-21 16:50 GMT+04:00 Brad King brad.k...@kitware.com:
On 10/20/2014 12:53 PM, Evgeny Kalishenko wrote:
The final patch version with erroneous spelling fixes.
Thanks. Please configure your git 'user.name' so that
On Sat, Oct 25, 2014 at 08:50:12 +1300, Ben Cooksley wrote:
On Sat, Oct 25, 2014 at 5:44 AM, Stephen Kelly steve...@gmail.com wrote:
Is build.kde.org now using the release branch of cmake.git instead of the
next branch? When/why did that change?
This was changed around about
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15218
==
Reported By:Zach Mullen
Assigned To:
On Friday 24 October 2014 11:49:55 AM Sahil Sehgal wrote:
Hello,
I was trying to build Okular (KDE application) in IDE (QT-creator and Kdevelop
both). I did the following steps:
1.) clonned the source code of Okular
2.) loaded the source code in IDE
3.) click on the build command.
Thanks for finding the broken link, I have correct the url and everything
should be working now.
On Thu, Oct 23, 2014 at 8:23 PM, David Cole via CMake cmake@cmake.org
wrote:
The new CMake web site looks fantastic! Even on my phone... Kudos to
everybody involved in making it look pretty after
Hi,
I am building some Fortran sources and on Mac I want to make the
resulting executable portable back to 10.7.
So I have:
if (APPLE)
set (CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS} -stdlib=libc++)
set (CMAKE_OSX_DEPLOYMENT_TARGET 10.7) # Earliest version we can
support with C++11 libc++
A small correction:
On 24/10/2014 16:31, Bill Somerville wrote:
Hi,
I am building some Fortran sources and on Mac I want to make the
resulting executable portable back to 10.7.
So I have:
if (APPLE)
set (CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS} -stdlib=libc++)
set
Please suggest the possible solution
Regards
Sahil Sehgal
-- next part --
An HTML attachment was scrubbed...
URL:
http://public.kitware.com/pipermail/cmake/attachments/20141024/e8173598/attachment.html
-- next part --
A non-text attachment
the possible solution
Regards
Sahil Sehgal
-- next part --
An HTML attachment was scrubbed...
URL:
http://public.kitware.com/pipermail/cmake/attachments/20141024/b62f04c8/attachment-0001.html
-- next part --
A non-text attachment
On 24/10/2014 18:39, Zaak Beekman wrote:
Hi Bill,
Hi Zaak,
thanks for the detailed suggestions, more comments in line below.
I feel your pain. I suspect a CMake bug is hidden away somewhere
causing this behavior, and have struggled with this quite a lot.
I think you are correct.
I *think*
On 10/24/2014 11:31 AM, Bill Somerville wrote:
So what am I missing? A brief scan of the CMake sources looks like it
should be doing this right for GNU compilers as the compiler tests
should check for those options being supported and supply them.
It looks like a couple of lines are missing
On 24/10/2014 19:11, Brad King wrote:
HI Brad,
On 10/24/2014 11:31 AM, Bill Somerville wrote:
So what am I missing? A brief scan of the CMake sources looks like it
should be doing this right for GNU compilers as the compiler tests
should check for those options being supported and supply them.
On 10/24/2014 02:15 PM, Bill Somerville wrote:
Can I just put the patched module in my project Modules directory or do
I have to build the whole CMake project?
No need to recompile. You can just add the two lines directly in your
Modules directory.
-Brad
--
Powered by www.kitware.com
I'm test-driving CMake for a new project I've just started and I'm
currently trying to set up a unit test framework. The project is a
dynamic library written in C++, the unit tests are based on Boost test,
and the project tree is organized essentially as follows:
.
├── CMakeLists.txt
├──
On 24.10.2014 20:28, Zé wrote:
I'm test-driving CMake for a new project I've just started and I'm
currently trying to set up a unit test framework. The project is a
dynamic library written in C++, the unit tests are based on Boost
test, and the project tree is organized essentially as
As far as I am aware the Boost find module doesn't support writing out
import targets.
As far as setting up interface libraries for imported tagets you want to
use the
IMPORTED_LINK_INTERFACE_LIBRARIES and
IMPORTED_LINK_INTERFACE_LIBRARIES_CONFIG properties.
Here is an example:
On 24/10/2014 19:16, Brad King wrote:
Hi Brad,
On 10/24/2014 02:15 PM, Bill Somerville wrote:
Can I just put the patched module in my project Modules directory or do
I have to build the whole CMake project?
No need to recompile. You can just add the two lines directly in your
Modules
On Friday, October 24, 2014 11:49:55 Sahil Sehgal wrote:
Hello,
I was trying to build Okular (KDE application) in IDE (QT-creator and
Kdevelop both). I did the following steps:
1.) clonned the source code of Okular
2.) loaded the source code in IDE
3.) click on the build command.
I got
So I may be taking on too much.. but I am migrating to Qt5 and Cmake 3.0 on my
project (from Qt4.8 and CMake 2.8)
I have minimized the project to a simple testcase that will represent the
problem, and it still exists.
My project, has multiple executables and multiple libraries for each exec.
What is the Filters target here? How is it created? Would I just
create a target called Boost and configure it as needed?
On Fri, Oct 24, 2014 at 2:43 PM, Robert Maynard
robert.mayn...@kitware.com wrote:
As far as I am aware the Boost find module doesn't support writing out
import targets.
As
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 e5cde94df65918cf4d51ef7b8747732a02a3bdaf (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 ab5e5a6292dbf461c3e53f57fe76bf0932dc50b1 (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 e3db575e2e29789127fa40b2a7690aabd873a0b4 (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 aac38f88d4016191dbddc65a4ad5d1bb3fd8c9dd (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 33a603aa5558bd107a5d018daeb78659810a8183 (commit)
via
20141024)
+set(CMake_VERSION_PATCH 20141025)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
36 matches
Mail list logo
