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 co
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 20
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
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
It seems the cmake_parse_arguments() function is very slow, performing a
find on the full argument list for each argument, resulting in O(N*N)
performance. Could this function possibly be moved into a C++
implementation rather than a CMake implementation so it will run quickly?
Cheers!
Andrew Hund
> 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
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 wrote:
> After a bit of research I found out y
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
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 CMa
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 wrote:
> 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 in
> > project 1
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 pack
11 matches
Mail list logo
