Yes, that’s pretty much the workflow I’m implementing, with the exception
that Gradle drives everything, including CMake; not the other way around.
Gradle is, in my opinion, somewhat more general purpose than CMake, which
is laser-focused on dealing with native code, so I have structured our
multi-
Honestly I hadn't set any expectations for the response I was going to
get here. Your response is surprisingly hopeful IMHO.
So basically the goal is to treat C++ completely separate from Java
from a development, workflow, and build system perspective. In other
words, if we need to debug native co
Hi Robert,
This will be a bit long-winded, so bear with me. I¹m also cross-compiling
for Android with CMake, and am currently using Eclipse ADT for much of my
development. I have tried hard to make Eclipse work for both the Java and
the C++ portions of my libraries and applications, but gave up af
On Wed, Mar 11, 2015 at 11:42 AM, Robert Dailey
wrote:
> I am implementing support for Android in my CMake scripts by using
> custom commands to invoke 'ant' to build the final APK. If I do it
> this way, and I generate for eclipse, how can I make sure it will
> integrate with the ADT plugin?
>
>
I am implementing support for Android in my CMake scripts by using
custom commands to invoke 'ant' to build the final APK. If I do it
this way, and I generate for eclipse, how can I make sure it will
integrate with the ADT plugin?
Basically I want to be able to right-click my project in Eclipse
(g
