The following issue has been SUBMITTED.
==
http://cmake.org/Bug/view.php?id=14766
==
Reported By:Mathieu Malaterre
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14768
==
Reported By:Paul Smith
Assigned To:
Are there any other corner cases I should consider banning as well? What
about behavior that should be allowed that currently isn't?
If this patch is the right place to address this is not clear to me, but I
mention them anyway.
-if a string is quoted, it may still be expanded as a variable
After a bit of research I found out you can create a toolchain file
for Android NDK, however I'm not sure how to plug in the java files.
It looks like it must be done separately after the C++ target is
added, so I was hoping maybe a post-build event could tie in the logic
to build the complete
Thanks very much, Magnus! I will try it out.
(your tag line made me laugh)
Cheers,
Aaron
On Thu, Feb 20, 2014 at 1:21 AM, Magnus Therning mag...@therning.orgwrote:
On Wed, Feb 19, 2014 at 06:24:44PM -0500, Aaron Boxer wrote:
I have cmake two projects, with project 2 added as a git submodule
I've built CMake 3.0.0-rc1 and tested it, and I still see this same bug
with that version of CMake.
Anyone have any ideas? Not having reliable builds is wreaking total
havoc on the Xcode users on our development team.
On Wed, 2014-02-19 at 15:17 -0500, Paul Smith wrote:
Hi all. I'm using
FWIW, I tried making cmake projects that be used in two ways unchanged:
1) build installed libraries that other projects (not just cmake
projects) can use
2) be included in an overarching cmake project that knows about subprojects
but it did not turn out to be practical. Maybe I just hadn't drunk
Have a look here:
http://vtk.org/gitweb?p=VES.git;a=tree;f=CMake/toolchains;h=c09a5c6933cf04fec83fe94afcea2e47afbce9e7;hb=HEAD
Corresponding blog: http://www.kitware.com/blog/home/post/546
- Aashish
On Thu, Feb 20, 2014 at 9:21 AM, Robert Dailey rcdailey.li...@gmail.comwrote:
After a bit
Hi David,
What does your install(...) line look like so we can try to help you debug
the issue?
OK, this is about as simple as it gets:
---
file foo.c:
extern int foo(void)
{
return 0;
}
---
file CMakeLists.txt
cmake_minimum_required( VERSION
david.hag...@gmail.com wrote:
install(TARGETS foo
RUNTIME DESTINATION bin
LIBRARY DESTINATION lib
EXPORT foo-targets
)
The order of arguments is wrong.
Move the 'EXPORT foo-targets' to just after 'TARGETS foo'.
I don't know if this is a behavior change since the wiki was written, but
I think I've have an epiphany.
I've been really struggling to understand how to get my build to work, and
it seems the problem is with the configure step of cmake.
I would like to see some mechanism whereby I can delay the completion of
the configure step of a target until the build (and install
Thanks, this does help with the toolchain part of it (I had already
seen the one you linked), however I'm concerned about actually
building the APK. Do I need to just create a custom target that
invokes 'ant debug' and 'ant release'? Or is there more granular
control I need to have?
On Thu, Feb
On 02/20/2014 11:54 PM, Jack Smith wrote:
I think I've have an epiphany.
I've been really struggling to understand how to get my build to work,
and it seems the problem is with the configure step of cmake.
I would like to see some mechanism whereby I can delay the completion
of the
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 5122fe0a1a823f51f9c88d8a0538557c3383d5f7 (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 cc0c4d8eda8bb9f890142f848cbdec144ff0c96a (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 6f28c4881e26dcecbf5b90d44d5fe755302d6607 (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 e1a66db4d30643d374b16a0a0f15129a4afa516e (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 55dcddb639933cb3790d17462ddd3823637c5d62 (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 f9183eb38efda48630a47e624096fe1a88bc778b (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 1e7dcd0257d1506afae7bdbdb3d4e15e5495 (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 f00a9aa2fb6d587c2db3685b01c8011e270a0db5 (commit)
via
20140220)
+set(CMake_VERSION_PATCH 20140221)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
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 f096cca1b30369b329043030e3583d4ee7c0b455 (commit)
via
23 matches
Mail list logo
