Ben Boeckel wrote:
I'm seeing considerable performance impact of this feature, even when it
isn't used:
Can you create an sscce?
Are there many static libraries involved?
Thanks,
Steve.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14963
==
Reported By:Brad King
Assigned To:
On 06/08/2014 09:12 AM, o.k...@gmx.de wrote:
I deleted the additional include/ in FindLua51.cmake and it worked.
I think that is the correct fix. I do not know why they were there
in the first place. They appear in FindLua50, FindLua51, and the
version-agnostic FindLua module. Eike, did you
Steve,
On 06/08/2014 06:56 PM, Ben Boeckel wrote:
9) Performance
Ben's concerns are more important than the following, but I also
wonder if we can reduce the startup time by combining the ABI
and Feature checks:
# Try to identify the ABI and configure it into CMakeCCompiler.cmake
Am Montag, 9. Juni 2014, 10:00:35 schrieben Sie:
On 06/08/2014 09:12 AM, o.k...@gmx.de wrote:
I deleted the additional include/ in FindLua51.cmake and it worked.
I think that is the correct fix. I do not know why they were there
in the first place. They appear in FindLua50, FindLua51, and
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14964
==
Reported By:Linus
Assigned To:
On Mon, Jun 09, 2014 at 07:46:42 -0400, David Cole wrote:
Can you create an sscce?
Not really. The wall time impact is only really visible on sizeable
projects and the jitter in the time can be masked in smaller projects.
The smallest you're probably going to get is VTK without searching for
Hi,
So add_compile_options exists now, but is still not a 100% replacement
for CMAKE_CXX_FLAGS_${config} because the flags are only used for the
.c - .o step and not for linking. Some flags need to be passed to the
linker as well (in my case, profiling flags, but I imagine other tooling
flags,
Steve W,
On 06/09/2014 11:46 AM, Brad King wrote:
See thread here:
push of LinkOptionsCommand topic branch
http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/9203
IIRC there were a couple of minor unresolved issues but it is mostly
just waiting for someone to have time to
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14965
==
Reported By:sdough
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14966
==
Reported By:Christopher Yeleighton
Assigned To:
Hi Jameson,
Glad to know you sorted out the issue.
By any chance, do you think you could share a link to a github repository
with your project ? That would allow us to review how you integrated
ExternalProjectDependency and improve it.
Thanks
Jc
On Sun, Jun 8, 2014 at 9:39 PM, jmerkow
Jc,
I'm working on an open source project, but we're no quite ready to release it
to the world yet. We will likely post it on github or another hosting website
(publicly) in the coming months and I'll be sure to let you know. We are
looking at an early fall release date.
Jameson
—
Sent
Hi all,
Does anybody can share a cmak file used for dashboard submission(cdash) via
ctest script mode. ctest -S cmake file
I tried cmake and for my project cmake builds fine. But when using ctest it
gives error on pthreads library.
--
Regards,
Rashad
--
Powered by www.kitware.com
Hello,
What is returned if string(FIND) matches a substring, and what is returned
if it doesn't match anything?
Abid K.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the
What is returned if string(FIND) matches a substring, and what is
returned if it doesn't match anything?
The documentation says:
http://cmake.org/cmake/help/v2.8.12/cmake.html#command:string
http://www.cmake.org/cmake/help/v3.0/command/string.html
string(FIND string substring output variable
Is it possible to invoke a script function as part of a target? I have a
build step where I need to process a bunch of variable values before
building a particular target. All of the custom targets require a COMMAND,
not a function. I thought maybe I could push this off to a script invoked
by
Is it possible to invoke a script function as part of a target?
No, because the variable values are all gone after CMake finishes
running. And the custom build targets do not run until later at build
time.
I have a build step where I need to process a bunch of variable
values before
Hello All,
I have a source folder(Src) as below:
Src/Application/
Src/Middleware/
Src/Etc/
I create a build folder above Src/
mkdir build
cd build
cmake ../
This makes the binary under build/ with CMakeLists.txt under Src/, so I have
Src/
build/
However, when I need to browse/debug code using
On Fri, Jun 6, 2014 at 3:55 PM, Adam adam707b...@gmail.com wrote:
I think the CMAKE_COMPILER variable you're referring to is just a custom
variable passed to your external project, which it uses to build the
standard variables CMAKE_C_COMPILER CMAKE_CXX_COMPILER. This is why
your not
Hello,
I am having trouble using find_package along with PATHS or HINTS. If I
include a PATHS or HINTS path which does not contain the searched-for
package, I always get an error such as this:
CMake Error at CMakeLists.txt:182 (find_package):
Could not find module FindGLEW.cmake or a
On 09.06.2014 22:31, R. Keith Morley wrote:
Hello,
I am having trouble using find_package along with PATHS or HINTS. If I
include a PATHS or HINTS path which does not contain the searched-for
package, I always get an error such as this:
CMake Error at CMakeLists.txt:182 (find_package):
On 09.06.2014 12:58, Rick McGuire wrote:
Is it possible to invoke a script function as part of a target? I
have a build step where I need to process a bunch of variable values
before building a particular target. All of the custom targets
require a COMMAND, not a function. I thought maybe I
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 cf56e032eb6afef5a0fc8b974e6a4820b8cb9711 (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 0c6d0cc151a17bf9ecd00d7f98881e56810e6325 (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 8c29d8d1e79ba5538368171bf89e8c55b5a58e54 (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 074ac5dbe9380ff462fd6767b5428a30fe82af69 (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 bf022b79633d5976df32a868fa65611e4679a6af (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 81ddcaa67b28a80f2dca18df3f0a6a96be169587 (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 d20792f30204a5bf9a34da13104f40f2026060cf (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 a0861931ead8cdcb6401e204ca4072c60af46101 (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 3c0652f8bf8974fde8b8313738272f2714b0f62b (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 d1502b34a3f0bb7c7fc0ffeae60c56e056a5d052 (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 84904906b77cbb58ae976aab8466deda4e6426db (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 f56e74ef563bea59b5fc62db18164341f797ad07 (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 f8020b0c5036bbd7bc349cb72134a44c5ce38c82 (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 e385dfe1f50e8161ea77a134ee88e89dadc59f24 (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 cfa0012b5924ee309dfa8bd1d5459487f8b27be8 (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 51775851f10ff2f5b74da1c8dceffe0ae88a3f15 (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 55a3c4cbc0f68e00bfd05b21a6bc6f063529e784 (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, release has been updated
via f25a301f3a8acc694e8c9d6f04733bfbffb1fd3c (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 9e8fa1043ce9bfcffdcfa395f618dd7958ef4251 (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 4ab4054c6faba93b8891197beecf6887011a6409 (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 e03f83f5efd8d0b0d7d9ab8a7140b1de3d7fc528 (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 f93a85c96a332146137defdd3cd062d7b18b0133 (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 a3935db5a260943aada7f9a6f2b01f7160a992d5 (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 606ce07c62ea524526982afb56e7e3e868cc4e2e (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 5f18b28916d3132d6e459e1cc4f08f6525aa74ed (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 36327498c9f9b3c87ab077368bbc3438566d0395 (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 4474f75af686960f332a91ff28dbcffa1975655b (commit)
via
20140609)
+set(CMake_VERSION_PATCH 20140610)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
51 matches
Mail list logo
