Has anyone used GetPrerequisites[1] when cross-compiling a shared
library with Android NDK toolchain? I'd like some way to get dependent
*.so files (located in the NDK itself and specified on the linker
command line when building) so I can copy them to my android java
project dir under "libs" so
So I'm working with DanAlbert over on the NDK github project regarding
some issues I've hit with NDK r15b using CMake 3.9.0-rc5. He's already
identified one bug that I can help fix located in
`Modules/Platform/Android/ndk-stl-c++.cmake` related to platform
support. He also mentions something a bit
have made it available as a gist:
https://gist.github.com/rcdailey/ae336b48b8681897c747524a5713c6c6
Hope this helps others that have similar questions. Thanks again Brad.
On Tue, Jun 27, 2017 at 11:07 AM, Brad King <brad.k...@kitware.com> wrote:
> On 06/27/2017 11:36 AM, Robert Dailey wro
it provides.
I'm guessing this is supported behavior. If so, I'll rely on it.
On Fri, Jul 7, 2017 at 1:20 PM, Robert Dailey <rcdailey.li...@gmail.com> wrote:
> I actually confused myself a bit... I think the issue is not that
> finding happens when including it, but that doxygen_add_docs()
it provides.
I'm guessing this is supported behavior. If so, I'll rely on it.
On Fri, Jul 7, 2017 at 1:20 PM, Robert Dailey <rcdailey.li...@gmail.com> wrote:
> I actually confused myself a bit... I think the issue is not that
> finding happens when including it, but that doxygen_add_docs()
include FindDoxygen to get access to the
function?
On Fri, Jul 7, 2017 at 1:13 PM, Robert Dailey <rcdailey.li...@gmail.com> wrote:
> When I do this:
>
>
> message( "blah1" )
> include( FindDoxygen )
>
> message( "blah2" )
> find_package( Doxygen
include FindDoxygen to get access to the
function?
On Fri, Jul 7, 2017 at 1:13 PM, Robert Dailey <rcdailey.li...@gmail.com> wrote:
> When I do this:
>
>
> message( "blah1" )
> include( FindDoxygen )
>
> message( "blah2" )
> find_package( Doxygen
When I do this:
message( "blah1" )
include( FindDoxygen )
message( "blah2" )
find_package( Doxygen 1.8.6 OPTIONAL_COMPONENTS dot )
message( "blah3" )
I get this output:
blah1
-- Found Doxygen: C:/Program Files/doxygen/bin/doxygen.exe (found
version "1.8.13") found components: doxygen
This is a continuation of the discussion I had with Brad here:
https://gitlab.kitware.com/cmake/cmake/merge_requests/1019#note_286609
Hopefully we can continue the discussion here, but I'm happy to hear
from others as well.
It was stated that VERBATIM is not necessarily useful in all cases.
Are
a separate function provided by FindDoxygen.cmake.
I'll follow up later. Thanks for your advice.
On Fri, Jun 30, 2017 at 9:48 PM, Craig Scott <craig.sc...@crascit.com> wrote:
>
>
> On Thu, Jun 29, 2017 at 11:14 AM, Robert Dailey <rcdailey.li...@gmail.com>
> wrote:
>&
Doxygen supports linking external documentation together:
https://www.stack.nl/~dimitri/doxygen/manual/external.html
Using doxygen_add_docs(), it doesn't provide built-in support for tag
files. I'm thinking this would be beneficial since the way the
function is designed encourages modular
On Tue, Jun 27, 2017 at 10:22 AM, Brad King <brad.k...@kitware.com> wrote:
> On 06/27/2017 11:14 AM, Robert Dailey wrote:
>> Also at $DAYJOB, we all work on the same code base. Our product is
>> tested and verified to work on a distinct set of configurations. Why
>> woul
On Mon, Jun 26, 2017 at 3:32 PM, Brad King <brad.k...@kitware.com> wrote:
> On 06/26/2017 11:58 AM, Robert Dailey wrote:
>> Why does this only work in the toolchain file?
>
> 1. It needs to be set early.
>
> 2. It needs to propagate into try_compile projects.
>
>
On Mon, Jun 26, 2017 at 10:25 AM, Brad King <brad.k...@kitware.com> wrote:
> On 06/23/2017 03:18 PM, Robert Dailey wrote:
>> enable_language(ASM)
>>
>> CMake appears to find clang.exe in the wrong place
>
> Add a `Modules/Platform/Android-Determine-ASM.cmake` mo
Hi,
I tried setting CMAKE_ANDROID_NDK_DEPRECATED_HEADERS in a common CMake
script of mine (set during configuration but before any targets are
created). I also tried making it a cache variable, but in each case it
isn't working. I set like this:
set( CMAKE_ANDROID_NDK_DEPRECATED_HEADERS 1 )
And
Oh I'm using CMake 3.9.0 RC3
On Fri, Jun 23, 2017 at 2:18 PM, Robert Dailey <rcdailey.li...@gmail.com> wrote:
> So I have two environment variables:
>
> ANDROID_NDK = E:\android\ndk
> ANDROID_NDK_72 = E:\android\ndk_72
>
> In my toolchain file, I do this:
>
>
>
So I have two environment variables:
ANDROID_NDK = E:\android\ndk
ANDROID_NDK_72 = E:\android\ndk_72
In my toolchain file, I do this:
set( CMAKE_SYSTEM_NAME Android )
set( CMAKE_SYSTEM_VERSION 15 ) # API level
set( CMAKE_ANDROID_ARCH_ABI armeabi-v7a )
set( CMAKE_ANDROID_STL_TYPE c++_shared )
In my toolchain file for Android NDK, I specify the following *.so
paths manually:
set( ANDROID_PREBUILT_LIBRARIES
${CMAKE_ANDROID_NDK}/sources/cxx-stl/gnu-libstdc++/4.9/libs/x86/libgnustl_shared.so
${CMAKE_ANDROID_NDK}/platforms/android-15/arch-x86/usr/lib/libz.so
)
However, I'd like a
So I have a series of common CMake scripts I use:
pre-setup.cmake
post-setup.cmake
I include pre-setup.cmake at the beginning of the root CMakeLists.txt
and post-setup.cmake is included at the bottom. add_subdirectory() and
other target stuff is done inbetween.
One issue I run into is that
ork properly? What if
> stuff that depends on that individualTarget also needs to rebuild
> before packaging? Shouldn't you have to do a build all to guarantee
> that packaging the results works properly?
>
>
>
>
>
>
> On Thu, May 18, 2017 at 12:16 PM, Robert Dailey
to run: build "all" or
> explicitly build it after you build the other individual thing you
> want?
>
>
>
>
> On Thu, May 18, 2017 at 10:24 AM, Robert Dailey
> <rcdailey.li...@gmail.com> wrote:
>> David,
>>
>> Thanks for your help. So if I
t depend on all other targets. (Or at least all other "leaf" targets,
> which further depend on others, ... the sum of which is "all other
> targets" besides the new "last" target.)
>
> So it's not pretty, but it's possible.
>
>
> HTH,
> David C.
&
I have a custom target that must meet the following requirements:
* It must always run, regardless of what subset of other targets are being built
* It must always be the very last thing run. In parallelized builds,
it must wait until all other targets are done building before
starting, so that
Forgot to mention, I'm using CMake 3.8.1
On Thu, May 4, 2017 at 10:47 AM, Robert Dailey <rcdailey.li...@gmail.com> wrote:
> How can I get a list of target dependencies of a target? For example,
> if I have 3 library targets that depend on each other like this:
>
> A ->
How can I get a list of target dependencies of a target? For example,
if I have 3 library targets that depend on each other like this:
A -> B -> C
When I ask for the target dependencies for A, I should get a list back
with B in it. Basically this would be the same list I pass to
I am seeing hints of ANT / JAVA support for Android in 3.8.1
documentation. Essentially there is a whole list of properties that
have unexplained use cases under Properties for Targets. I see
ANDROID_JAVA_SOURCE_DIR, for example. What are these for? Will CMake
actually do the "ant release" command
; wrote:
> On 24/04/2017 15:54, Robert Dailey wrote:
>>
>> Sorry to bump; any info on this? I'm completely blocked :-(
>>
>> On Fri, Apr 21, 2017 at 4:48 PM, Robert Dailey <rcdailey.li...@gmail.com>
>> wrote:
>>>
>>> I'm running CMake 3.8.
libraries now, so I am happy. Should
CMAKE_SYSTEM_PROCESSOR be i386 or i686?
On Mon, Apr 24, 2017 at 12:22 PM, Robert Dailey
<rcdailey.li...@gmail.com> wrote:
> The output is:
>
> x86_64-linux-gnu
>
> How can I tell CMake to look for 32-bit libraries? I would like to
> forc
d on your system? What's the value of
> CMAKE__LIBRARY_ARCHITECTURE?
>
>
> Since you're on a 64-bit system, I'd expect CMake to be looking for 64-bit
> libraries unless you've told it otherwise.
>
>
> From: CMake <cmake-boun...@c
On Mon, Apr 24, 2017 at 10:02 AM, Ben Boeckel <ben.boec...@kitware.com> wrote:
> On Mon, Apr 24, 2017 at 09:54:18 -0500, Robert Dailey wrote:
>> On Fri, Apr 21, 2017 at 4:48 PM, Robert Dailey <rcdailey.li...@gmail.com>
>> wrote:
>> > I'm running CMake 3.8.0
On Mon, Apr 24, 2017 at 10:02 AM, Ben Boeckel <ben.boec...@kitware.com> wrote:
> On Mon, Apr 24, 2017 at 09:54:18 -0500, Robert Dailey wrote:
>> On Fri, Apr 21, 2017 at 4:48 PM, Robert Dailey <rcdailey.li...@gmail.com>
>> wrote:
>> > I'm running CMake 3.8.0
Sorry to bump; any info on this? I'm completely blocked :-(
On Fri, Apr 21, 2017 at 4:48 PM, Robert Dailey <rcdailey.li...@gmail.com> wrote:
> I'm running CMake 3.8.0 on Ubuntu 14. I invoke the following:
>
> find_package(PNG REQUIRED)
>
> Which gives me the output in CMak
Sorry to bump; any info on this? I'm completely blocked :-(
On Fri, Apr 21, 2017 at 4:48 PM, Robert Dailey <rcdailey.li...@gmail.com> wrote:
> I'm running CMake 3.8.0 on Ubuntu 14. I invoke the following:
>
> find_package(PNG REQUIRED)
>
> Which gives me the output in CMak
I'm running CMake 3.8.0 on Ubuntu 14. I invoke the following:
find_package(PNG REQUIRED)
Which gives me the output in CMake:
Could NOT find PNG (missing: PNG_LIBRARY) (found version "1.2.50")
The CMakeCache.txt file has these variables set:
absolute paths to items in the NDK.
On Tue, Apr 18, 2017 at 9:45 PM, Robert Dailey <rcdailey.li...@gmail.com> wrote:
> I'm trying to follow best practices where I can, but the trouble is
> I'm not aware of any. So I want to post my android.toolchain.cmake
> file here, with the hope that
> latest changes soon next week!
>
> /Florent
>
> On Apr 20, 2017 10:10 PM, "Robert Dailey" <rcdailey.li...@gmail.com> wrote:
>>
>> I may pick this up, because right now it's impossible to use libc++
>> (LLVM) with an API less than 21 since that's when
wrote:
> On Thu, Apr 20, 2017 at 14:31:58 -0500, Robert Dailey wrote:
>> Google is supporting unified headers for sysroot as of NDK r14:
>>
>> https://android.googlesource.com/platform/ndk/+/master/docs/UnifiedHeaders.md
>>
>> Is there a plan to add support for this na
Google is supporting unified headers for sysroot as of NDK r14:
https://android.googlesource.com/platform/ndk/+/master/docs/UnifiedHeaders.md
Is there a plan to add support for this natively into CMake?
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
I'm trying to follow best practices where I can, but the trouble is
I'm not aware of any. So I want to post my android.toolchain.cmake
file here, with the hope that I can get some pointers.
The main thing I want to understand is when it is appropriate to
require cache variables be set via command
When I execute a CMake script as a custom command, message() logs are
not shown in stdout from that script.
Is there a way to make it pipe out messages?
--
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
( BUILD_VERSION CACHE )
else()
set( BUILD_VERSION 7.1.1.2 )
endif()
On Mon, Apr 10, 2017 at 1:32 PM, Robert Dailey <rcdailey.li...@gmail.com> wrote:
> Actually this seems to work:
>
> if( BUILD_VERSION )
>
> set( version_override ${BUILD_VERSION} )
> un
, and doesn't require
configure_file(). Maybe there is a way to clean this up even more?
I noticed that unset( BUILD_VERSION CACHE ) actually unsets non-cache
versions of a variable too, so I had to use the temporary variable to
transfer the value.
On Mon, Apr 10, 2017 at 1:15 PM, Robert Dailey
, Bruce Stephens
<bruce.r.steph...@gmail.com> wrote:
> On Mon, Apr 10, 2017 at 5:04 PM, Robert Dailey <rcdailey.li...@gmail.com>
> wrote:
>> Actually I think your idea does work. Why do you think it won't? I'm
>> using it right now and so far it seems OK.
>
> I
Actually I think your idea does work. Why do you think it won't? I'm
using it right now and so far it seems OK.
1. On build server, if it overrides it with -D, then it does not set
it by hand. If it doesn't override, it will use the fixed version in
the file
2. On work machines, it's never
I have a file called version.cmake that my root CMakeLists.txt
includes. There is only a single line in this file:
set( BUILD_VERSION 1.2.3.4 CACHE STRING "Version of the product" )
I have two scenarios where this version number setting needs to work
slightly differently from a CMake
t;
>>add_custom_command( TARGET zApp_zip POST_BUILD
>>COMMAND ${CMAKE_COMMAND} -E echo "test2"
>>COMMAND ${CMAKE_COMMAND} ARGS ...snip...
>>)
>>
>>
>>
>>On Fri, Apr 7, 2017 at 11:40 PM, Robert Dailey
>><rcdailey.li...@gmai
a bit more complicated to implement as you need to
> transition from Ant to Gradle, but I remember the ant tooling being
> deprecated now, so it should improve the situation a little bit.
>
> /Florent
>
>> On 7 Apr 2017, at 14:32, Robert Dailey <rcdailey.li...@gmail.com> w
So I probably am not understanding how this works.
I have a custom target, that I later add multiple custom commands to.
Each custom command has a COMMENT set, but the target itself does too:
add_custom_target(zApp_zip COMMENT "test1")
add_custom_command( TARGET zApp_zip POST_BUILD
4/06/2017 04:43 PM, Robert Dailey wrote:
>> Even worse, they seem to acknowledge this problem and created "proxy"
>> macros for the use by the host OS (code at the bottom)
>
> Interesting. That approach depends on all projects using their
> macros instead of the n
NLY )
set( CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY )
set( CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY )
endmacro()
On Thu, Apr 6, 2017 at 3:41 PM, Robert Dailey <rcdailey.li...@gmail.com> wrote:
> Unsetting these at the bottom of the toolchain file fixes it:
>
> unset( CMAKE_FIND_ROOT_PATH )
> unset( CMAKE
re is a reason for it, but I'd never
want this personally, and I find it concerning that a toolchain file
can break this for the whole project.
What should I do?
On Thu, Apr 6, 2017 at 3:28 PM, Robert Dailey <rcdailey.li...@gmail.com> wrote:
> Brad,
>
> I debugged
/arm-linux-androideabi-4.9/prebuilt/windows/bin/Python35/
The real location of it (and what is visible in PATH itself) is:
E:/Python35/
On Mon, Mar 20, 2017 at 9:20 AM, Brad King <brad.k...@kitware.com> wrote:
> On 03/20/2017 10:17 AM, Robert Dailey wrote:
>> What can I do to help you g
I have CMake setup to build native shared libraries (*.so) that are
included in an APK built for Android. The "ant release" command is
invoked by a custom target I define in CMake, which handles building
the java pieces as well as packaging the final app into an APK file.
So the build pipeline
On Thu, Mar 30, 2017 at 3:42 AM, Tamás Kenéz wrote:
> An alternative to the CMake superbuild: leave your actual project intact.
> Simply create a separate shell script which builds all the dependencies (by
> running cmake commands). Or, if you do like the ExternalProject
On Wed, Mar 29, 2017 at 9:32 PM, Florent Castelli
<florent.caste...@gmail.com> wrote:
> On 30/03/2017 03:54, Robert Dailey wrote:
>>
>> On Wed, Mar 29, 2017 at 8:18 PM, Florent Castelli
>> <florent.caste...@gmail.com> wrote:
>>>
>>> This is kno
On Wed, Mar 29, 2017 at 8:18 PM, Florent Castelli
wrote:
> This is known as "super build".
> Yes, this is exactly why I made my Boost CMake build scripts, which you use
> unless you changed your mind today :)
You mean this?
https://github.com/Orphis/boost-cmake
It's
This fails:
include( foo/bar/myscript.cmake )
But this works:
include( ${CMAKE_CURRENT_LIST_DIR}/foo/bar/myscript.cmake )
Why are relative paths not working?
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware
Interested in hearing everyone's thoughts on this idea of mine.
Right now I have several third party libraries: openssl, boost,
libpng, zlib, etc. List goes on. I need to support these libraries on
at least 3 different platforms: ARM android, x86 linux, x86 windows.
It's a real pain in the rear
is located here:
${CMAKE_ANDROID_NDK}/sources/crystax/libs/${ANDROID_ABI}
Is there a way I can add this to the linker search path from the
toolchain file? Or is there a better way?
On Thu, Mar 23, 2017 at 3:22 PM, Robert Dailey <rcdailey.li...@gmail.com> wrote:
> Update:
>
> U
Update:
Using the x86_64 version of the Crystax NDK worked. Meaning, the
directory name aligned with what CMake was expecting. However, the
question now is: Why didn't changing
CMAKE_ANDROID_NDK_TOOLCHAIN_HOST_TAG work?
On Thu, Mar 23, 2017 at 3:14 PM, Robert Dailey <rcdailey.li...@gmail.
-androideabi-4.9
-DANDROID_ABI=armeabi-v7a -DANDROID_TOOLCHAIN_VERSION=4.9
-DANDROID_STL=gnustl_static
On Thu, Mar 23, 2017 at 3:03 PM, Robert Dailey <rcdailey.li...@gmail.com> wrote:
> So I'm having no luck getting the Crystax NDK setup using built-in
> android support in CMake 3.
So I'm having no luck getting the Crystax NDK setup using built-in
android support in CMake 3.8.
I have the following toolchain file:
set( CMAKE_SYSTEM_NAME Android )
set( CMAKE_SYSTEM_VERSION ${ANDROID_API} )
# set( CMAKE_ANDROID_NDK $ENV{ANDROID_NDK} )
set( CMAKE_ANDROID_NDK
On Thu, Mar 23, 2017 at 10:50 AM, Brad King <brad.k...@kitware.com> wrote:
> On 03/23/2017 11:35 AM, Robert Dailey wrote:
>> Thanks Brad. For future reference, are these changes documented
>> anywhere? I searched for "enable_language" in the 3.6 release note
On Thu, Mar 23, 2017 at 10:33 AM, Brad King <brad.k...@kitware.com> wrote:
> On 03/23/2017 11:16 AM, Robert Dailey wrote:
>> I remember around cmake v3.6, the behavior of enable_language()
>> changed so that if you did it too many times, you'd get the error:
>>
>>
I remember around cmake v3.6, the behavior of enable_language()
changed so that if you did it too many times, you'd get the error:
Language 'C' is currently being enabled. Recursive call not allowed.
I need to implement some backward compatibility code to check of CMake
version less than 3.6
On Mon, Mar 20, 2017 at 9:20 AM, Brad King <brad.k...@kitware.com> wrote:
> On 03/20/2017 10:17 AM, Robert Dailey wrote:
>> What can I do to help you guys diagnose this problem? I could try
>> getting a reproducible script for you, but this is so dependent on
>&g
On Mon, Mar 20, 2017 at 8:40 AM, Brad King <brad.k...@kitware.com> wrote:
> On 03/17/2017 05:38 PM, Robert Dailey wrote:
>> find_program(GIT_EXECUTABLE git)
>
> The steps it follows are documented here:
>
> https://cmake.org/cmake/help/v3.8/command/find_program.html
&
So I have Git 2.11.1 installed and it's located in E:\Git\cmd\git.exe.
I ticked the option in the installer to add it to path.
I tried using the FindGit module via find_package() to find Git, but
it's not working. So I tried a simpler case:
find_program(GIT_EXECUTABLE git)
However it cannot
At the moment, with CMake 3.0 and on, I can use this syntax for
multi-line strings:
option( ZIOSK_ENABLE_ZPAY_DIAGNOSTICS "\
Enable additional diagnostic logs for zPay related code. \
Should not be enabled for production due to the sensitivity \
and volume of logs that will be printed." )
The
At the moment, with CMake 3.0 and on, I can use this syntax for
multi-line strings:
option( ZIOSK_ENABLE_ZPAY_DIAGNOSTICS "\
Enable additional diagnostic logs for zPay related code. \
Should not be enabled for production due to the sensitivity \
and volume of logs that will be printed." )
The
The latter.
On Thu, Jan 5, 2017 at 3:39 PM, Robert Maynard
<robert.mayn...@kitware.com> wrote:
> Do you mean you don't see where the static library is created or where
> the static library is listed on the link line for the dynamic library?
>
> On Thu, Jan 5, 2017 at 11:30
I have two targets in CMake: a static library and a shared library.
The shared library specifies the static library as a target link
library.
When I generate for Ninja, and I run:
$ ninja -v
During the link command for the shared library, I do not see the
static library specified to g++. I do
When I define my targets (custom, library, executable), does the order
of their declaration matter when it comes to using those targets in
dependencies? It's difficult to explain, so I'll show an example:
add_executable(foo main1.cpp)
target_link_libraries(foo abc)
add_library(abc main2.cpp)
Visual C++ PM Lead
>
> -Original Message-----
> From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Robert Dailey
> Sent: Tuesday, November 22, 2016 10:58 AM
> To: CMake <cmake@cmake.org>
> Subject: [CMake] VS2017 + CMake integration
>
> First of all, I pe
First of all, I personally find the CMake integration in Visual Studio
just absolutely amazing. Granted I am not doing any cross-compiling
with Android yet, but for just building on Windows it's phenomenal.
I noticed that Visual Studio 2017 RC is actually packaging its own
version of CMake:
ne and I hope you'll find the
> solution to your issues!
>
> As for CMake 3.7, when I asked about it in this mailing list, someone said
> there will be
> a compatibility layer to the toolchain to reuse the upstream support when
> it's available
> if I remember correctly.
>
> /Flor
ne and I hope you'll find the
> solution to your issues!
>
> As for CMake 3.7, when I asked about it in this mailing list, someone said
> there will be
> a compatibility layer to the toolchain to reuse the upstream support when
> it's available
> if I remember correctly.
>
> /Flor
I'm sorry but that doesn't really answer my questions.
On Mon, Oct 31, 2016 at 8:55 AM, Cong Monkey <congzhan...@gmail.com> wrote:
> Try to update your Android SDK from android studio?
>
>
> 2016年10月31日 21:31,"Robert Dailey" <rcdailey.li...@gmail.com>写道:
&
I'm sorry but that doesn't really answer my questions.
On Mon, Oct 31, 2016 at 8:55 AM, Cong Monkey <congzhan...@gmail.com> wrote:
> Try to update your Android SDK from android studio?
>
>
> 2016年10月31日 21:31,"Robert Dailey" <rcdailey.li...@gmail.com>写道:
&
support to test CMAKE support!
>
> You can follow https://code.google.com/p/android/issues/detail?id=212007
> to get the details.
>
> 2016-10-28 5:48 GMT+08:00 Robert Dailey <rcdailey.li...@gmail.com>:
>> I'm at a bit of a loss on finding more information. Can anyone at
&
support to test CMAKE support!
>
> You can follow https://code.google.com/p/android/issues/detail?id=212007
> to get the details.
>
> 2016-10-28 5:48 GMT+08:00 Robert Dailey <rcdailey.li...@gmail.com>:
>> I'm at a bit of a loss on finding more information. Can anyone at
&
I'm at a bit of a loss on finding more information. Can anyone at
least confirm that this isn't a reliable place to find the answers I'm
looking for? Does anyone have real experience with android + gradle +
cmake integration and can provide some pointers?
On Tue, Oct 25, 2016 at 8:48 AM, Robert
I'm at a bit of a loss on finding more information. Can anyone at
least confirm that this isn't a reliable place to find the answers I'm
looking for? Does anyone have real experience with android + gradle +
cmake integration and can provide some pointers?
On Tue, Oct 25, 2016 at 8:48 AM, Robert
I'm not sure if the CMake mailing lists are the right place to ask
this question but I thought I'd ask just in case someone has gone down
this path or has experience with what Google/Gradle is actually trying
to accomplish with what seems to be a hand-built version of CMake with
custom patches
I'm not sure if the CMake mailing lists are the right place to ask
this question but I thought I'd ask just in case someone has gone down
this path or has experience with what Google/Gradle is actually trying
to accomplish with what seems to be a hand-built version of CMake with
custom patches
On Thu, Oct 20, 2016 at 2:51 PM, Brad King <brad.k...@kitware.com> wrote:
> On 10/20/2016 03:35 PM, Robert Dailey wrote:
>> So using takanome's cmake toolchain, he had support for native app
>> glue. Does CMake offer support for this now? I was able to generate
>&g
So using takanome's cmake toolchain, he had support for native app
glue. Does CMake offer support for this now? I was able to generate
but I'm not able to load in native app glue from the NDK.
On Tue, Oct 18, 2016 at 10:05 AM, Mikhail Filimonov
wrote:
> Hi Brad,
> It looks
On Tue, Sep 27, 2016 at 10:39 AM, Brad King wrote:
> On 09/27/2016 11:28 AM, Florent Castelli wrote:
>> Is there any plan on having their toolchain in CMake directly at some point?
>
> No. Their toolchain files are designed to be loaded from the NDK. They
> compute things
Currently nightly builds are tagged 3.6.2. Are there no nightly builds
for 3.7 or am I missing something?
On Fri, Aug 12, 2016 at 10:26 AM, Robert Goulet
wrote:
> That's super awesome Brad!
>
> Looking forward to try this out!
>
> -Original Message-
> From:
On Fri, Aug 12, 2016 at 4:58 PM, Roger Leigh wrote:
> You can simplify this to two steps:
>
> 1. Clone the superbuild repository
> 2. Build the third-party and first-party packages
>
> This is the approach we take with the OME super-build
>
anks, Ruslo
>
>
> On 12-Aug-16 22:59, Robert Dailey wrote:
>>
>> Hello,
>>
>> There is an internal C++ product at the company I work for which I
>> have written a series of CMake scripts for. This project actually has
>> dependencies on several open sourc
pack and other meta builders do. See http://github.
> com/llnl/spack
>
> On Aug 12, 2016 3:59 PM, "Robert Dailey" <rcdailey.li...@gmail.com> wrote:
>>
>> Hello,
>>
>> There is an internal C++ product at the company I work for which I
>> have writte
pack and other meta builders do. See http://github.
> com/llnl/spack
>
> On Aug 12, 2016 3:59 PM, "Robert Dailey" <rcdailey.li...@gmail.com> wrote:
>>
>> Hello,
>>
>> There is an internal C++ product at the company I work for which I
>> have writte
Hello,
There is an internal C++ product at the company I work for which I
have written a series of CMake scripts for. This project actually has
dependencies on several open source libraries, such as boost,
freetype, openssl, etc.
Right now what we do is build each of these third party libraries
Hello,
There is an internal C++ product at the company I work for which I
have written a series of CMake scripts for. This project actually has
dependencies on several open source libraries, such as boost,
freetype, openssl, etc.
Right now what we do is build each of these third party libraries
On Tue, Jul 19, 2016 at 9:38 AM, Robert Dailey <rcdailey.li...@gmail.com> wrote:
> Hello,
>
> I'd like to define an INTERFACE library that has header files only but
> still generates its own project in Visual Studio. The only way to add
> headers to an interface
Hello,
I'd like to define an INTERFACE library that has header files only but
still generates its own project in Visual Studio. The only way to add
headers to an interface target that I'm aware of is
target_source_files(), which instead of creating a project it will
cause the header files
On Fri, Jul 15, 2016 at 9:05 AM, Brad King wrote:
> VS: Add a VS_TOOL_OVERRIDE source file property
> https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ed05f11d
Nice, I wasn't aware that there was already a feature in place to
support this. Given that this exists, is
Hello CMake devs,
I'm writing code to support Natvis files in Visual Studio 2015
(earlier versions support this as well, I think).
I found an issue regarding this here (is Kitware officially using
github or gitlab? CMake exists on both):
https://gitlab.kitware.com/cmake/cmake/issues/16043
On Sun, Jul 10, 2016 at 1:23 PM, Robert Dailey <rcdailey.li...@gmail.com> wrote:
> I am exporting/installing a header-only INTERFACE library and I run
> into difficulty with target_sources() because I can't use relative
> paths to the files. So I do this:
>
>
>
> set(
101 - 200 of 878 matches
Mail list logo