On Tue, May 6, 2014 at 5:54 PM, Michael Oldfield <
sag_mal_plue...@yahoo.com.au> wrote:
> On 07/05/14 00:25, Rick McGuire wrote:
> > Working on converting an existing project to cmake, which is going
> > fairly well. I've found answers to most of questions with some quick
> > google searches, but
On 07/05/14 00:25, Rick McGuire wrote:
> Working on converting an existing project to cmake, which is going
> fairly well. I've found answers to most of questions with some quick
> google searches, but I've run into an issue where I've not managed to
> find any answers yet.
>
> One part of the
So I have 4 examples I actually tried to document.
These all use my fork/derivative of the Android-CMake toolchain, which
I believe comes from OpenCV. (It had grown stale with later NDKs and I
hit problems). All of these rely heavily on the external NDK module
system (NDK_MODULE_PATH).
The first a
This is a page on building to android; mostly it's about my library, but
names can be replaced where required
https://code.google.com/p/c-system-abstraction-component-gui/wiki/BuildingForAndroid
I went wit the separate cmake projects because I end up with multiple
android projects from the same li
'after copying to the correct location'
in mine the sources are 'installed' and then when I start the android
packaging, it first updates local copies in lib/armeabi/ and assets
openCV project produces a lot of target architectures in /lib/...
so really I have my normal project which builds
Well to be clear, the NDK libraries are compiled in eclipse after I
generate eclipse makefiles in CMake. Ideally, I want the CMake script
to also configure "ant" execution so that it builds java and links in
the NDK libraries. You say "just use the libraries", but I'm not sure
what this looks like
Yes, I believe this is still a problem in the current development version
of cmake, in that /MANIFESTUAC:NO is not correctly processed. (And, by the
way, my previous comment about this potentially being fixed by a
restructuring was probably due to my mis-reading of the code.)
Ultimately, however,
If you've built the sources into libs, you can just use the lib; my sources
are much too complex of a tree for ndk to support to build as sources..
The java sources are compiled at the 'ant wrote:
> There is also the question of how to handle the NDK sources and
> integrate them into the eclipse
There is also the question of how to handle the NDK sources and
integrate them into the eclipse workspace. For example, I believe NDK
sources must be under the 'jni' directory, but they won't be
structured that way in the source tree. So I'm not sure if the jni
directory is required. I realize ther
You can look at what we did for VES:
http://www.kitware.com/blog/home/post/642
-Bill
--
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 CMake community. For more
inform
I've overcome this by using the COMPILE_FLAGS source file property
http://www.cmake.org/cmake/help/v2.8.11/cmake.html#prop_sf:COMPILE_FLAGS
Those flags will be appended to the rest of the compiler flags, so you can
make them override the debug flags. For instance, if your debug flags are
"-UNDEBUG
Hi Robert,
If you want, check out the excellent "android-cmake" project for some tips.
It covers a lot of different scenarios for Android:
https://code.google.com/p/android-cmake/
I put together a simple function to generate an APK from CMake:
https://github.com/arpg/rpg-cmake/blob/master/def_apk
Working on converting an existing project to cmake, which is going fairly
well. I've found answers to most of questions with some quick google
searches, but I've run into an issue where I've not managed to find any
answers yet.
One part of the project generates two executables with the same name.
Hi,
I'm reinstalling a machine that got a new OS (W2K8R2), and now cmake 2.8.4
refuses to serve me like it does on Windows 7.
$ cmake . -DUSE_LOCAL_BUILD=ON -DLOCAL_BIN_DIR="$LOCAL_BIN_DIR"
-- Building for: Visual Studio 9 2008
CMake Error: CMake was unable to find a build program corresponding t
once you have your libraries and java souces... need to put them in an
arrangement like the ndk-build script expects (in libs, src, res) and have
a build.xml and a androidManifest.xml
then just call
ant
this does the packaging, and results in a bin/-.apk
the next useful commands are
adb install
Hello,
I have been working on getting CMake working for Android projects. So
far, I have a custom toolchain file to build NDK libraries. I am also
able to generate makefiles for Eclipse, import those projects into
eclipse, and build from eclipse. All seems to be working fine from
that aspect.
The
Dear All,
We currently have a FORTRAN library we’re building with CMake (around 1000
files of FORTRAN).
ADD_LIBRARY(
My_Fortran_Lib
…….
)
For the release build we set the release compilation flags with
“CMAKE_Fortran_FLAGS_RELEASE” and set “CMAKE_BUILD_TYPE” to “Release” for
those flags to b
One solution is to use the following:
if ( AS_USE_SCALASCA )
set(CMAKE_C_COMPILER alias_scalasca)
set(CMAKE_CXX_COMPILER alias_scalasca)
file(WRITE alias_scalasca
"#!/bin/bash
the_whole line with all arguments and this_as_is \"$@\"
")
file(INSTALL alias_scalasca
DESTINATION ${PRO
18 matches
Mail list logo
