summaryrefslogtreecommitdiffstats
path: root/Tests/RunCMake/Framework
Commit message (Collapse)AuthorAgeFilesLines
* Tests: Fix clang -Wstrict-prototypes warningsBrad King2023-10-265-5/+5
|
* macOS: GNU toolchain: ensure framework, marked as SYSTEM, can be linkedMarc Chevrier2023-09-212-9/+15
| | | | Fixes: #25263
* macOS: IMPORTED framework: Honor SYSTEM target property in all casesMarc Chevrier2023-08-271-0/+12
| | | | When IMPORTED_LOCATION holds a framework folder, SYSTEM property must be respected.
* macOS: Allow IMPORTED_LOCATION to be a framework folderKyle Edwards2023-06-233-1/+21
| | | | Issue: #24946
* Apple Frameworks: honor SYSTEM target propertyMarc Chevrier2023-05-111-0/+12
| | | | Fixes: #24109
* Xcode: Fix missing Frameworks search pathsMarc Chevrier2023-03-062-3/+16
| | | | Fixes: #24541
* Tests/RunCMake: Update cmake_minimum_required versionsBrad King2023-02-113-4/+1
| | | | | | | | For policy-specific tests, use the version before the policy was introduced. Otherwise, use 3.5 where possible. Also, remove `cmake_minimum_required()` and `project()` calls from individual cases where they are handled by `CMakeLists.txt`.
* Xcode: ensure framework with custom output directory can be consumedMarc Chevrier2022-10-142-0/+27
| | | | Fixes: #24046
* Apple: Fix regression when linking a framework with postfixMarc Chevrier2022-09-141-0/+5
| | | | | | | Fix a regression caused by commit 40178f3c90 (cmGlobalGenerator: Add helper to split framework path, 2022-02-10, v3.24.0-rc1~661^2~1). Fixes: #23961
* Ensure targets which are frameworks can be used freelyMarc Chevrier2022-03-295-0/+43
| | | | | | | Ensure flag -F/path/to/framework is specified during compilation step of consumers of the framework. Fixes: #23336
* Xcode: Properly identify frameworks with system includesGregor Jasny2021-12-225-0/+33
| | | | | | | | Check the complete include path for being a system include, not the derived framework search path. The code for Ninja and Makefile generators does exactly the same. Fixes: #23011
* Framework: Fix $<TARGET_SONAME_FILE:...> for imported frameworksKyle Edwards2021-05-203-0/+23
|
* Add support for FRAMEWORK_MULTI_CONFIG_POSTFIX_<CONFIG>Alexandru Croitor2020-03-043-0/+106
|
* Tests: Match file command output for older macOS (Framework test)Craig Scott2019-10-272-4/+2
|
* Tests: Prevent CMP0012 policy warnings in Framework test outputCraig Scott2019-10-271-1/+1
|
* Add variable CMAKE_FRAMEWORKRuslan Baratov2019-05-212-6/+17
|
* macOS: Restore compatibility for setting FRAMEWORK after install()Brad King2019-01-303-0/+14
| | | | | | | | | | | | | | | | | The `FRAMEWORK` target property affects the way the `install()` command treats the target and so should be set first. Our implementation assumed that this was always the case and led to an assertion failure. Prior to CMake 3.12 this was visible only when using an explicit `LIBRARY ... NAMELINK_ONLY` option, but commit 0212d7c762 (install: add NAMELINK_COMPONENT argument, 2018-04-18, v3.12.0-rc1~139^2~3) made it possible with a simple `LIBRARY DESTINATION`. Fully supporting out-of-order specification will require non-trivial refactoring to defer install generator creation to generate time. For now simply restore the old behavior of installing the framework to the library destination and warn about the case. Fixes: #18848
* Tests: Fix RunCMake.Framework ios arch for Xcode 9Brad King2017-10-031-1/+11
| | | | | Xcode 9 comes with the iPhoneOS 11.0 SDK that does not support the `armv7` architecture. For this SDK version and newer, use `arm64`.
* Tests: Fix RunCMake.Framework expected output on macOS 10.13Brad King2017-10-031-2/+2
| | | | | | The archiver output in the case of universal binaries has changed slightly. Update our expected output to match. While at it, drop unnecessary leading and trailing `.*`.
* Tests: Use full output paths in file(GENERATE) callsBrad King2017-06-081-1/+1
| | | | | We don't define behavior for relative paths to the OUTPUT argument. Fix our tests to use full paths.
* Tests: Fix RunCMake.Framework expectation for universal binariesBrad King2017-05-082-2/+5
| | | | | While at it, replace `\n` in with a real newline because such escape sequences are not processed in this context.
* Xcode: Execute RunCMake.Framework also for Xcode generatorGregor Jasny2017-03-304-9/+11
|
* Apple: Add test for bundle resource layoutGregor Jasny2017-03-236-1/+37
| | | | Closes: #16680
* Apple: Add support for static frameworksGregor Jasny2017-01-314-5/+31
| | | | Closes: #16432
* Xcode: Refactor RunCMake.Framework test to prepare for static frameworksGregor Jasny2017-01-261-31/+17
|
* Tests: Fix RunCMake.Framework on case sensitive file systems.Chaoren Lin2016-08-091-1/+1
| | | | The file is lowercase: Tests/RunCMake/Framework/osx.cmake
* Revise C++ coding style using clang-formatKitware Robot2016-05-161-1/+4
| | | | | | | | | | | | | Run the `Utilities/Scripts/clang-format.bash` script to update all our C++ code to a new style defined by `.clang-format`. Use `clang-format` version 3.8. * If you reached this commit for a line in `git blame`, re-run the blame operation starting at the parent of this commit to see older history for the content. * See the parent commit for instructions to rebase a change across this style transition commit.
* iOS: Fix framework resource directory layout (#15848)Bartosz Kosiorek2015-12-035-4/+41
| | | | | | | | A typical iOS application bundle (also Framework Bundle) contains the application executable and any resources used by the application (for instance, the application icon, other images, and localized content) in the top-level bundle directory. The same rule applies to Framework Bundles.
* Add test for OSX/iOS Framework directory structure (#15833)Gregor Jasny2015-11-138-0/+125
generated by cgit v0.12 at 2024-09-22 08:41:47 (GMT)