[cmake-developers] [CMake 0015709]: variables defined state is not reset after using it for iteration in foreach
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15709
==
Reported By:Jan Christoph Uhde
Assigned To:
==
Project:CMake
Issue ID: 15709
Category: CMake
Reproducibility:always
Severity: minor
Priority: normal
Status: new
==
Date Submitted: 2015-08-24 08:39 EDT
Last Modified: 2015-08-24 08:39 EDT
==
Summary:variables defined state is not reset after using it
for iteration in foreach
Description:
When using a prior undefined variable in a foreach(x ${foo}) loop it is still
defined after the loop.
We noticed it due to the following warning:
/usr/share/cmake-3.2/Modules/CheckSymbolExists.cmake:
53 macro(_CHECK_SYMBOL_EXISTS SOURCEFILE SYMBOL FILES VARIABLE)
54 if(NOT DEFINED ${VARIABLE} OR x${${VARIABLE}} STREQUAL x${VARIABLE})
-- Looking for include file pthread.h - found
CMake Warning (dev) at /usr/share/cmake-3.2/Modules/CheckSymbolExists.cmake:54
(if):
Policy CMP0054 is not set: Only interpret if() arguments as variables or
keywords when unquoted. Run cmake --help-policy CMP0054 for policy
details. Use the cmake_policy command to set the policy and suppress this
warning.
Quoted variables like x will no longer be dereferenced when the policy is
set to NEW. Since the policy is not set the OLD behavior will be used.
Call Stack (most recent call first):
/usr/share/cmake-3.2/Modules/CheckSymbolExists.cmake:50 (_CHECK_SYMBOL_EXISTS)
/usr/share/cmake-3.2/Modules/FindThreads.cmake:133 (CHECK_SYMBOL_EXISTS)
5axis/test/exactoutputBTOneFile/CMakeLists.txt:13 (find_package)
This warning is for project developers. Use -Wno-dev to suppress it.
The name x was not a good choice. But the behavior is really unintuitive.
Cheers
Jan
Steps to Reproduce:
cmake_minimum_required(VERSION 3.2)
set(FOO this is borken)
foreach(x ${FOO})
message(mesage: ${x})
endforeach()
if(DEFINED x)
message(x is still defined)
endif()
==
Issue History
Date ModifiedUsername FieldChange
==
2015-08-24 08:39 Jan Christoph UhdeNew Issue
==
--
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
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0015710]: Does not find JNI on x32
The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=15710 == Reported By:Felix Geyer Assigned To: == Project:CMake Issue ID: 15710 Category: Modules Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2015-08-24 10:04 EDT Last Modified: 2015-08-24 10:04 EDT == Summary:Does not find JNI on x32 Description: FindJNI.cmake sets _java_libarch incorrect on the x32 architecture (amd64 kernel + x32 uerland). The attached patch by Thorsten Glaser t...@mirbsd.de fixes this. I'm not sure if there is a better variable to check instead of CMAKE_LIBRARY_ARCHITECTURE. Forwarded from https://bugs.debian.org/792262 == Issue History Date ModifiedUsername FieldChange == 2015-08-24 10:04 Felix GeyerNew Issue 2015-08-24 10:04 Felix GeyerFile Added: findjni_x32.diff == -- 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 information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] FindBZip2.cmake
On 08/23/2015 07:36 AM, Rolf Eike Beer wrote: you introduced in 7c912af2 that this module not only looks into the Windows registry, but also added PATH_SUFFIXES include and lib for find_* calls. Wouldn't CMake automatically append those to all paths given? No. The suffixes are only added after values found in CMAKE_PREFIX_PATH and similar variables, not to every path given. Another thing which I found is that there seems to be an obscure problem in FindBZip2.cmake to not find the library on Windows if the path contains backslashes. Yes, really. Just compare the cmake part of these 2 links (no idea how long they will present, as they are CI logs): https://ci.appveyor.com/project/Mapbox/libosmium/build/1.0.228/job/my1segqcq89k28en https://ci.appveyor.com/project/Mapbox/libosmium/build/1.0.227/job/rnu1e71degn7snwm I have no clue what happens there, why it happens only for that module, and why noone noticed that before. I do not have access to a Windows system where I can test easily, but maybe you can have a look (or find someone to)? I thought that it may be \b, because that would be unique to that module in that build configuration, but if I pass the CMAKE_PREFIX_PATH with forward slash at that point it still fails, while all other modules work. The BZIP2_NEED_PREFIX check generates a CMakeLists.txt file that refers to the raw path given without re-escaping the backslashes. Then the check fails to configure due to the backslashes being interpreted as invalid CMake escape sequences. -Brad -- 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 information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] cmake's built-in support for android using nvidia nsight tegra
On 08/23/2015 04:44 PM, Peter List wrote: How do I tell cmake to include Ant Build in my vcxproj, so that it will package my project into an APK? I can generate vcxproj that builds a Tegra-Android *.so file, but it does not build me an APK, and my vcxproj is missing the Ant Build property section. You need to set the ANDROID_GUI target property on an exe: http://www.cmake.org/cmake/help/v3.3/prop_tgt/ANDROID_GUI.html Additional settings have been added in post-3.3 development: VS: Add more Nsight Tegra generator Android property settings http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8c0afaf4 -Brad -- 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 information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Replace deprecated libarchive functions
On 08/22/2015 12:32 PM, Páder Rezső wrote: cmake requires libarchive3, but uses old, deprecated libarchive functions. The attached patch solves this. Thanks, applied: Use modern libarchive APIs http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e7f93715 -Brad -- 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 information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] PATCH: Add Certificate Thumbprint to VS for Windows Phone and Windows Store projects
On 08/21/2015 06:04 PM, Gilles Khouzam wrote: I would like to submit a new patch to write the PackageCertificateThumbprint tag in VS projects Applied with minor tweaks and merged to 'next' for testing: VS: Windows Store/Phone package cert thumbprint http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bdae9ffe Thanks, -Brad -- 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 information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] FindZLIB module should find debug and, release variants
On 08/23/2015 04:41 PM, Michael Scott wrote: Okay no problem, I've changed the patch to use SelectLibraryConfigurations instead. I've also changed the last bit of the patch, to set the IMPORTED_CONFIGURATIONS target property as well when there's debug and release variants, to be consistent with other Find modules. Let me know if this shouldn't be done in this situation. Please add each of the _DEBUG and _RELEASE configurations if and only if the corresponding variables are set. Grep for mention of IMPORTED_CONFIGURATIONS in other Modules/Find*.cmake files for examples. Thanks, -Brad P.S. Your mailer is breaking threads. -- 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 information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] cmState-definitions topic
Brad King wrote: Steve, I've merged most of this topic: Merge topic 'cmState-definitions' http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2370a994 Great, thanks! I think the last two commits on it: cmLinkedTree: Add API for size query and reserve. http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d7fc7c3a cmState: Reserve the number of cmLinkedTree nodes if known. http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=eb471768 can be dropped. They don't have a noticeable impact on performance in some quick local testing I did (on ParaView). I think saving size estimates persistently is a neat idea for the future if needed. Ok. It might have a bigger impact in the future. Thanks, Steve. -- 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 information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] cmState-definitions topic
Steve, I've merged most of this topic: Merge topic 'cmState-definitions' http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2370a994 I think the last two commits on it: cmLinkedTree: Add API for size query and reserve. http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d7fc7c3a cmState: Reserve the number of cmLinkedTree nodes if known. http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=eb471768 can be dropped. They don't have a noticeable impact on performance in some quick local testing I did (on ParaView). I think saving size estimates persistently is a neat idea for the future if needed. Thanks, -Brad -- 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 information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [CMake 0015669]: XCTest for iOS target has incorrect TEST_HOST
Hi Brad, On 21/08/15 15:36, Brad King wrote: Thanks. I merged to 'next' for testing last night. Please take a look at the failures: https://open.cdash.org/testSummary.php?project=1name=RunCMake.XcodeProjectdate=2015-08-21 It's all green now: https://open.cdash.org/testSummary.php?project=1name=RunCMake.XcodeProjectdate=2015-08-24 Thanks, Gregor -- 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 information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] Xcode 7 tbd library stub support
Hello, Starting with Xcode 7 the OSX and iOS SDKs contain only stub files for dynamic system libraries. These stub files contain some meta data and a list of exported sysbols in plain text. They are handled by the toolchain like regular dylibs. I just pushed a topic branch to add support for Xcode 7 TDB files: http://www.cmake.org/gitweb?p=stage/cmake.git;a=shortlog;h=refs/heads/apple-tbd-stubs Please review and merge if the patch is acceptable. Thanks, Gregor See for example the following posts: https://forums.developer.apple.com/thread/4572 https://forums.developer.apple.com/message/9176 http://stackoverflow.com/questions/30890830/missing-dylib-library-while-opening-in-xcode-7-beta -- 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 information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] Default compile options
In our root CMakeLists.txt file we do this: set(CMAKE_C_FLAGS) set(CMAKE_CXX_FLAGS) set(CMAKE_C_FLAGS_DEBUG -D_DEBUG) set(CMAKE_CXX_FLAGS_DEBUG -D_DEBUG) set(CMAKE_C_FLAGS_RELEASE -DNDEBUG) set(CMAKE_CXX_FLAGS_RELEASE -DNDEBUG) This is to reset the build flags for all platforms, but it doesn't seems to work very well. For instance, if we generate a Visual Studio project, it seems to work just fine, but in a Makefile those flags are not even passed to the compiler. Is this a bug or perhaps we are not doing it right? Why would it work for VS but not makefiles? Any suggestions? Thanks! -- 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 information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] cmake's built-in support for android using nvidia nsight tegra
Per Brad's suggestion, I removed this line from my CMakeLists.txt:
add_library(${PROJECT_NAME} SHARED ${SRC_LIST})
And I added these lines:
set(CMAKE_ANDROID_GUI TRUE)
set(CMAKE_ANDROID_API 19) # Kindle Fire HD 6
set(CMAKE_ANDROID_API_MIN 19) # Kindle Fire HD 6
add_executable(${PROJECT_NAME} ${SRC_LIST})
I am now able to generate a Visual Studio 2010 pemDemos.sln that includes a
pemDemos.vcxproj with a configuration properties section Ant Built. From
inside Visual Studio, I'm able to build an APK and then ctrl+F5 to run it
on my device.
Unfortunately, cmake did not generate AndroidManifest.xml, so I had to
supply my own using the aforementioned execute_process() with android.bat.
At this point my app just displays a Hello World, PemActivity message
that it gets from build-android\android\res\layout\main.xml. So it's not
using android_native_app_glue.c,h to point to my main.cpp code in
libpemDemos.so yet. So maybe cmake doesn't do that part automatically
for me? I also don't see a tutorial or simple hello world demo project for
this... However, I can at least use AndroidNativeApp.vcxproj as a
reference.
thank you best regards
On Mon, Aug 24, 2015 at 9:49 AM, Brad King brad.k...@kitware.com wrote:
On 08/23/2015 04:44 PM, Peter List wrote:
How do I tell cmake to include Ant Build in my vcxproj, so that
it will package my project into an APK? I can generate vcxproj
that builds a Tegra-Android *.so file, but it does not build me
an APK, and my vcxproj is missing the Ant Build property section.
You need to set the ANDROID_GUI target property on an exe:
http://www.cmake.org/cmake/help/v3.3/prop_tgt/ANDROID_GUI.html
Additional settings have been added in post-3.3 development:
VS: Add more Nsight Tegra generator Android property settings
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8c0afaf4
-Brad
--
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
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] FindBZip2.cmake
Brad King wrote: On 08/23/2015 07:36 AM, Rolf Eike Beer wrote: Another thing which I found is that there seems to be an obscure problem in FindBZip2.cmake to not find the library on Windows if the path contains backslashes. Yes, really. Just compare the cmake part of these 2 links (no idea how long they will present, as they are CI logs): https://ci.appveyor.com/project/Mapbox/libosmium/build/1.0.228/job/my1segq cq89k28en https://ci.appveyor.com/project/Mapbox/libosmium/build/1.0.227/job/rnu1e7 1degn7snwm I have no clue what happens there, why it happens only for that module, and why noone noticed that before. I do not have access to a Windows system where I can test easily, but maybe you can have a look (or find someone to)? I thought that it may be \b, because that would be unique to that module in that build configuration, but if I pass the CMAKE_PREFIX_PATH with forward slash at that point it still fails, while all other modules work. The BZIP2_NEED_PREFIX check generates a CMakeLists.txt file that refers to the raw path given without re-escaping the backslashes. Then the check fails to configure due to the backslashes being interpreted as invalid CMake escape sequences. No, this is not the problem. That happens if FPHSA succeeds, but that fails because it can't find the library, which means the problem is actually happen before FPHSA. Eike signature.asc Description: This is a digitally signed message part. -- 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 information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] cmake's built-in support for android using nvidia nsight tegra
I'm now attempting to build a simple SDL2 Android application with CMake's
built-in Android support (uses nvidia tegra nsight for visual studio 2010)
SDL2-2.0.3 does not appear to have a NativeActivity example so I'm
attempting to use its android-project folder that includes
SDL2-2.0.3\android-project\src\org\libsdl\app\SDLActivity.java instead.
I'm able to compile my libpemDemos.so project with SDL2 code this way for
armabi-v7a
I also compiled libSDL2.so for armabi-v7a using ndk-build (not nvidia tegra
nsight), and I'm able to reference it from my pemDemos.vcxproj
I verified my pemDemos.vcxproj linker step does includes this:
-L[path]/SDL2-2.0.3/libs/armeabi-v7a -lSDL2
However, I'm getting a linker error when I try to add SDL_android_main.c to
my build:
1 pemDemos.dir/Debug/SDL_android_main.o: In function
`Java_org_libsdl_app_SDLActivity_nativeInit(_JNIEnv*, _jclass*, _jobject*)':
1 [path]\SDL2-2.0.3\src\main\android\SDL_android_main.c(23): undefined
reference to `SDL_Android_Init(_JNIEnv*, _jclass*)'
1collect2.exe : error : ld returned 1 exit status
If I comment out the following one line then I can build my libpemDemos.so
again:
SDL_Android_Init(env, cls);
However that of course fails when I try to run it.
I don't understand why the linker doesn't see `SDL_Android_Init(_JNIEnv*,
_jclass*)'. I have -lSDL2 (and I know the linker is finding libSDL.so
because it gives an error if I change vcxproj settings to do -lSDLzzz
instead of -lSDL). Plus I even verified that libSDL2.so has
SDL_Android_Init():
readelf -Ws [path]\SDL2-2.0.3\libs\armeabi-v7a\libSDL2.so | grep
SDL_Android_Init
216: 0002f60d 332 FUNCGLOBAL DEFAULT8 SDL_Android_Init
So why doesn't my linker step find SDL_Android_Init()?
thank you for any leads
On Mon, Aug 24, 2015 at 8:20 PM, Peter List pem.l...@gmail.com wrote:
Per Brad's suggestion, I removed this line from my CMakeLists.txt:
add_library(${PROJECT_NAME} SHARED ${SRC_LIST})
And I added these lines:
set(CMAKE_ANDROID_GUI TRUE)
set(CMAKE_ANDROID_API 19) # Kindle Fire HD 6
set(CMAKE_ANDROID_API_MIN 19) # Kindle Fire HD 6
add_executable(${PROJECT_NAME} ${SRC_LIST})
I am now able to generate a Visual Studio 2010 pemDemos.sln that includes
a pemDemos.vcxproj with a configuration properties section Ant Built.
From inside Visual Studio, I'm able to build an APK and then ctrl+F5 to run
it on my device.
Unfortunately, cmake did not generate AndroidManifest.xml, so I had to
supply my own using the aforementioned execute_process() with android.bat.
At this point my app just displays a Hello World, PemActivity message
that it gets from build-android\android\res\layout\main.xml. So it's not
using android_native_app_glue.c,h to point to my main.cpp code in
libpemDemos.so yet. So maybe cmake doesn't do that part automatically
for me? I also don't see a tutorial or simple hello world demo project for
this... However, I can at least use AndroidNativeApp.vcxproj as a
reference.
thank you best regards
On Mon, Aug 24, 2015 at 9:49 AM, Brad King brad.k...@kitware.com wrote:
On 08/23/2015 04:44 PM, Peter List wrote:
How do I tell cmake to include Ant Build in my vcxproj, so that
it will package my project into an APK? I can generate vcxproj
that builds a Tegra-Android *.so file, but it does not build me
an APK, and my vcxproj is missing the Ant Build property section.
You need to set the ANDROID_GUI target property on an exe:
http://www.cmake.org/cmake/help/v3.3/prop_tgt/ANDROID_GUI.html
Additional settings have been added in post-3.3 development:
VS: Add more Nsight Tegra generator Android property settings
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8c0afaf4
-Brad
--
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
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
