Re: [cmake-developers] Create subdirectories in Resource directory for Frameworks and Application bundle.
On 11/12/15 22:16, Clinton Stimpson wrote:
>> To enable iOS build, I'm using following settings in CMakeLists.txt:
>> >
>> >
>> > set(APPLE_PLATFORM "iphonesimulator")
>> > set(CMAKE_OSX_SYSROOT
>> > "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platf
>> > orm/Developer/SDKs/iPhoneSimulator.sdk")
> set(CMAKE_C_FLAGS "-isysroot
>> > ${CMAKE_OSX_SYSROOT} -mios-version-min=7.0") set(CMAKE_CXX_FLAGS "-isysroot
>> > ${CMAKE_OSX_SYSROOT} -mios-version-min=7.0")
>> > Do you think it should be documented?
As far as I see one should create a Toolchain file for all Apple SDKs
(also macosx) because one has to modify header and library lookup paths
to not look into /usr. See for example
https://cmake.org/gitweb?p=cmake.git;a=blob;f=Tests/RunCMake/XcodeProject/osx.cmake;hb=HEAD
I planned to create an official macosx, iphone, etc. Toolchain files for
CMake but did not find the time to work on it.
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
Re: [cmake-developers] Create subdirectories in Resource directory for Frameworks and Application bundle.
On 11/12/15 20:21, clin...@elemtech.com wrote: > - On Dec 11, 2015, at 11:44 AM, Bartosz Kosiorek > wrote: >> Because there is difference between OS X and iOS Bundles directory structure >> (see: Apple specification >> https://developer.apple.com/library/mac/documentation/CoreFoundation/Conceptual/CFBundles/BundleTypes/BundleTypes.html >> ), >> in trunk (In CMake 3.5) RESOURCE property create corresponding directory >> structure. >> I have already fix that with: >> https://public.kitware.com/Bug/view.php?id=15848 > > Ok. I hadn't been following all your work. > Also, I didn't see a toggle in the CMake code you sent to choose an iOS > bundle instead of OS X bundles. How is that toggled? See cmMakefile::PlatformIsAppleIos() https://cmake.org/gitweb?p=cmake.git;a=blob;f=Source/cmMakefile.cxx;h=1b0a99ae84932af665360f63bf8bba8d7663ef8e;hb=HEAD#l2404 Basically it's looking at the CMAKE_OSX_SYSROOT variable. -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] CMakeFindDependencyMacro limitations
I've run into a few limitations in find_dependency. I'm not sure if
these are by design or could be fixed, so this is really a request for
further explanation or design rationale.
The first issue is this:
if (NOT ${dep}_FOUND)
This seems to be making the assumption that the found variable matches
the dependency name, but the case used varies between modules and the
name is case sensitive, from my reading of cmake-language. Is this
correct? Even if so, should this optimisation be put here rather than
in find_package itself? If case sensitivity/naming is an issue, could
the _FOUND variable be passed in as an argument, leaving the existing
behaviour as the default if unspecified?
The reason for stripping EXACT isn't clear. If my package has a strict
requirement on another package, whether the caller has an exact
requirement for the version of my package has no bearing on the
requirements I have for my dependencies as far as I understand. What's
the reason for the existing behaviour?
Support for find_package arguments is limited to the dependency name and
optionally the version. I can understand why REQUIRED and related
arguments are omitted--that is why find_dependency exists--but I'd quite
like to be able to specify COMPONENTS where needed e.g. with FindBoost,
and this is not currently possible.
I was wondering if we could perhaps make find_dependency handle and pass
through /all/ find_package arguments, minus REQUIRED/QUIET, so that
find_dependency can expose the additional functionality offered by
find_package. Some may not be useful, in which case they could be
omitted, but some like COMPONENTS may be required for the find_package
call to be useful.
Regards,
Roger
--
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
