Hello,
On 20.10.19 19:25, Robert Maynard via cmake-developers wrote:
I am proud to announce the second CMake 3.16 release candidate.
https://cmake.org/download/
CMake 3.16.0-rc2 successfully builds and tests our two large mono-repos.
I'm looking forward to the release!
Thanks,
Gregor
--
Hello,
in the past when building CMake (itself) I spent long times waiting for
configuration of the embedded libraries. Mostly libcurl send / receive
signature detection. Today I had the idea of using system libraries
installed with Homebrew and the speedups are quite noticeable:
You first
Hello,
I'm wondering if there is a specification for the XML test output file
produced by CTest?
Some background: For a dashboard we'd like to know in which
CMakeLists.txt a test was created. For that we use the Path tag. Here
the baz test was declared in subdir/CMakeLists.txt
Hello,
On 01.03.19 20:28, Robert Maynard via cmake-developers wrote:
I am proud to announce the third CMake 3.14 release candidate.
All problems observed with -rc1 and -rc2 have been solved. The rc3 works
as expected for our multi-platform mono repository.
Thanks for all your hard work!
Hello,
On 14.02.19 04:39, Timothy Wrona wrote:
Okay so I dug a little deeper into this and it definitely looks like
sphinx is the correct tool to use, but I still have one problem.
I would like sphinx to be able to extract ".rst" formatted comments
directly out of my cmake source files to
Hello,
On 20.08.18 19:10, Brad King wrote:
On 08/15/2018 01:30 PM, Rolf Eike Beer wrote:
My dislike against these functions is probably known, and now I would like to
bring this to a new level: I would like to formally deprecate these functions.
I don't think they serve any useful purpose
Hi,
On 1/16/18 11:19 AM, Gregor Jasny wrote:
> I created a CMake branch where I attempt to provide an easy way to
> configure CMake projects for iOS (and all other Xcode SDKs).
I have a second revision of the patches.
Issue: https://gitlab.kitware.com/cmake/cmake/issues/17870
Branch:
Hi,
I created a CMake branch where I attempt to provide an easy way to
configure CMake projects for iOS (and all other Xcode SDKs).
All you need to build for iOS is:
cmake -DCMAKE_SYSTEM_NAME=Darwin -DCMAKE_OSX_SYSROOT=iphoneos -GXcode .
In case you build code that must be code signed also
Hello,
In issue #16752 [1] a hanging xcodebuild during try_compile is reported.
Currently I cannot manage to find the spare time it takes to handle all
CMake issues in a timely manner.
Is anyone willing to help debugging this issue and/or filing a rdar://
report? Maybe someone also knows someone
Hello,
I wonder if a nightly (or on-demand) build of the CMake release branch
is available somewhere as it is for the master branch. That would help
me testing those snapshots within our companies projects.
Thanks,
Gregor
--
Powered by www.kitware.com
Please keep messages on-topic and
Hello,
while walking through old bug reports contacting the reporters by email
would be helpful sometimes. Is there a way for me access this
information in Mantis?
Thanks,
Gregor
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
Hello,
I just noticed that the Xcode generator creates one xcode project per
project() call:
> $ find _build_xcode -name "*.xcodeproj" |grep -v CMakeFiles |grep -v Tests
> _build_xcode/CMake.xcodeproj
> _build_xcode/Source/CursesDialog/form/CMAKE_FORM.xcodeproj
>
Hello,
I noticed cmake.org is quite slow on serving release files. I seldom get
more than 300KB/s. So I wonder if it would make sense to publish the
CMake release tarballs and binaries not only on cmake.org but also on
github as part of the release process. (From GitHub I currently get 9 MB/s)
Hello Daniel,
I wonder what's the idea behind the require-tr1 topic? Some still
supported platforms like macOS with Xcode 3.x seem to fail now.
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
Hello,
On 27/12/2016 13:20, Roger Leigh wrote:
> I opened the following merge request to add support for the
> newly-released Boost 1.63:
>
> https://gitlab.kitware.com/cmake/cmake/merge_requests/361
I wonder what's the reason for stating explicitly all the released
versions? It they are
Hello,
it looks like that during Generator Target refactoring the
cm(Generator)Target::IsFrameworkOnApple and similar got duplicated. Is
there a reason for this or could the GeneratorTarget simply query the
Target?
Do you have by any chance some high level design documentation about the
most
Hello,
I wonder what's the recommended workflow for CMake developers with
commit access to stage? I'd like to use feature branches in gitlab but
wonder how those are best merged into 'next'?
Could you please advise or point me to some documentation?
Thanks,
Gregor
--
Powered by
On 31/10/2016 00:03, Gregor Jasny wrote:
> On 30/10/2016 18:33, Jack Howarth wrote:
>> Gregor,
>> Your commit of...
>>
>> https://cmake.org/gitweb?p=cmake.git;a=log;h=540815eec2b83a8b43689580c54e8950d9f5868b
>>
>> has caused a major regression
On 30/10/2016 18:33, Jack Howarth wrote:
> Gregor,
> Your commit of...
>
> https://cmake.org/gitweb?p=cmake.git;a=log;h=540815eec2b83a8b43689580c54e8950d9f5868b
>
> has caused a major regression in cmake 3.7.0 as it no longer properly
> honors the combination...
>
>
On 30/10/2016 20:23, Jack Howarth wrote:
> Gregor,
> While I still think your hack to obtain the versioned SDK is
> wrong because it relies on passing invalid arguments to 'xcodebuild
> -sdk', the following change restores the expected behavior for
> -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING=""
On 30/10/2016 20:37, Jack Howarth wrote:
> Proposed fix to restore functionality for
> -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" -DCMAKE_OSX_SYSROOT:STRING=/
> while retaining the current hack when CMAKE_OSX_DEPLOYMENT_TARGET is
> not set to an empty string.
Thanks for the patch but it is breaking
Hello Howarth,
I'm sorry that I broke your use case with that patch. The problem I have
with maintaining the Xcode / Darwin code is that it is full of backward
compatibility and unknown, undocumented use cases. That makes it
sometimes hard to foresee consequences.
On 30/10/2016 19:04, Jack
On 09/08/16 22:01, Brad King wrote:
> On 08/09/2016 03:47 PM, Chaoren Lin via cmake-developers wrote:
>> The file is lowercase: Tests/RunCMake/Framework/osx.cmake
>
> Thanks, applied:
>
> Tests: Fix RunCMake.Framework on case sensitive file systems.
>
Hello,
in the past (with Mantis) I found it quite helpful to see new bugs
posted here on this mailing list. Is it planned to restore that
functionality?
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
On 21/06/16 18:48, Ruslan Baratov wrote:
> Is the patch applied? Let me know if there are any questions left about it.
Pushed into next. Sorry for the delay.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware
Hello,
Thanks for the patch!
On 15/06/16 16:41, Ruslan Baratov wrote:
> Sending some fixes found by testing with Xcode 7.3
We were chasing some errors regarding the unified build some time ago.
But it appeared some for of heisenbug: the more I looked the less likely
it happened.
Is the error
I'm away from keyboard until June 8th. everything written is from the top
of my head.
AFAIR the warning goes away if you properly set the OSX SYSROOT. Setting it
to macosx without version number should be sufficient (maybe you have to
insert a xcrun --showsdk-path there).
As far as I see the
Hello,
On 11/05/16 21:22, Roman Wüger wrote:
> I got the following error when linking the iOS bundle:
>
> clang: error: cannot specify -o when generating multiple output files
>
> I didn’t found anything about the error in the internet, so maybe someone
> has already solved such error?
>
>
Hallo Daniel,
On 09/04/16 00:31, Daniel Pfeifer wrote:
> I implemented the integration of `clang-tidy` along the lines of the
> `include-what-you-use` integration.
> There is a new `_CLANG_TIDY` target property that is initialized
> with the value of the `CMAKE__CLANG_TIDY` variable.
> It
Hello,
On 31/03/16 16:30, Harry Mallon wrote:
> This became an annoyance in our Cmake build system so here is a barebones
> xcscheme creator.
> https://github.com/hm1992/CMake/commit/5345881861a4b510d3a3283825584ec90f8d2061
>
> Current situation:
> * It seems to work for the executable targets
On 25/03/16 19:28, Brad King wrote:
> On 03/25/2016 01:46 PM, Gregor Jasny via cmake-developers wrote:
>> Does anyone see a reason to *not* prepend all with a ?
>
> I'm not particularly familiar with the ASM tooling landscape but
> that prepend step is exactly what was
Hello,
On 22/03/16 17:10, Mantis Bug Tracker wrote:
> Starting with CMake 3.4 the ASM_NASM language does not pass forward
> include_directories(XYZ) to the nasm compiler line.
>
> As far as I can see is missing for other assemblers as well.
When I grep for CMAKE_ASM * _COMPILE_OBJECT I get the
On 27/02/16 06:11, Mantis Bug Tracker wrote:
> Summary:Xcode generator's ReRunCMake.make fails if
> dependencies have been deleted
> Description:
> Currently, if a file that a CMake script previously had a dependency on is
> deleted, the Xcode generator's ReRunCMake.make
Hello Robert,
On 19/02/16 20:12, Robert Goulet wrote:
> I did this refactoring of the function that writes the XCode blocks in the
> project files, that adds support for any number of nested blocks. And it also
> makes the code easier to expand in the future.
>
> One of the areas that required
Hello,
On 19/02/16 00:34, Davy Durham wrote:
Actually we have to keep an os x 10.8 box up with the 10.7 sdk using
xcode 4.2 targeting 10.6. Apple long ago stopped allowing you to target
such old APIs in more recent xcodes.
At my company we build 10.6 compatible software using Xcode 6.3.
What
Hello,
I'd like to get your feedback on deprecating or dropping support for
older Xcode versions. During changes on the Xcode generator it gets
harder and harder to test against old and very old Xcode versions like 3
and 4.
Are there still users around for these versions of Xcode?
PS: I'm
Hello,
some time ago I started a project to make the CMake generated pbxproj
identical to the one Xcode writes. Some patches of that effort are
already in master, some lack some cleanup.
It would be great working with you on individual patches to 'modernize'
generated pbxproj files. Patches
Hello,
On 13/01/16 12:13, Marko Kylmämaa wrote:
> I would like to propose the following fix for bug 15183 (
> https://cmake.org/Bug/view.php?id=15183)
>
> For some reason the XcodeGenerator seemed to be setting the INSTALL_PATH
> variable regardless of if it was initialized or not (which is done
Hello,
I wonder if any of you CMake Developers go to FOSDEM [1] this year?
Thanks,
Gregor
[1] https://fosdem.org/2016/
--
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
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
>> >
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
>>
Hello,
On 09/12/15 10:21, Ruslan Baratov wrote:
IOS_INSTALL_COMBINED_BINARY
Just to clarify you want to leave only one variable
IOS_INSTALL_COMBINED_BINARY for the device + simulator on iOS platforms.
Other platforms (in future) will be controlled by using *_ARCHITECTURES
variables, right?
Hello Axel,
On 08/12/15 01:53, Huebl, Axel wrote:
My problem: I found that in the last step of linking ccmake against a
static (pre-compiled, ubuntu 12.04) ncurses library leads to linker
errors such as:
/usr/lib/x86_64-linux-gnu/libncurses.a(lib_mouse.o): In function
`_nc_mouse_event':
Hello,
On 02/12/15 13:44, Bartosz Kosiorek wrote:
> I would like to propose to rename property name to INSTALL_IOS_UNIVERSAL_LIBS.
My thoughts about the property name:
I added the necessary functionality to also combine Frameworks and App
Bundles. So the _LIBS suffix now got misleading. And I
Hello,
During the last days I worked on the iOS Universal Install topic which
now would benefit from a review. Especially the core changes could need
a third pair of eyes:
https://cmake.org/gitweb?p=stage/cmake.git;a=commit;h=8fb23b42cfc2fb7490e8645fff328add9c231713
I will now concentrate on
Hello,
I often run into the problem that I have to create a more complex
regular expression with several captures. Usually it takes some time and
many iterations.
Inspired by the emacs regex mode I added a dialog to the cmake gui where
one can experiment with regular expressions. Code is
On 12/11/15 09:25, Bartosz Kosiorek wrote:
> With this tiny little patch, the correct directory structure for iOS
> Frameworks is created.
I made the patch even smaller and pushed it into the
non-xcode-framework-layout topic branch. There I also added a test.
Thanks,
Gregor
--
Powered by
On 11/11/15 02:19, Bartosz Kosiorek wrote:
> Hi
>
> Generally I created this cmake scripts to to able to test creating iOS/OSX
> Application Bundle and iOS/OSX Dynamic Framework Bundle.
> By default it produces iOS application Bundle and iOS Framework Bundle.
>
> Steps to reproduce:
> 1.
On 11/11/15 05:48, Bartosz Kosiorek wrote:
Hello.
I think before release CMake 3.4.0 the documentation needs to be updated, to
reflect last changes in CMake regarding Apple platform.
I have created bug report for that issue:
https://public.kitware.com/Bug/view.php?id=15843
I also updated
Hello,
On 10/11/15 16:22, Bartosz Kosiorek wrote:
> My name is Bartosz Kosiorek and I'm TomTom developer and Open Source
> enthusiast.
I'm Gregor a part time contributor to CMake. During the last months I
mostly worked on Xcode support.
> Last time in our products, we notice that cmake is not
On 08/10/15 02:37, Ruslan Baratov wrote:
>>> export CORRESPONDING_DEVICE_PLATFORM_NAME=iphoneos
>>> export CORRESPONDING_DEVICE_SDK_NAME=iphoneos9.0
>>> export SDK_NAME=iphonesimulator9.0
>> Could you use those variables to avoid hardcoding iphoneos/simulator in
>> the module?
> I see
On 15/10/15 19:16, Davy Durham wrote:
> Bug filed here: https://cmake.org/Bug/view.php?id=15794
> Patch file against git master HEAD attached to this email.
>
> Acceptable?
I responded to the bug report itself:
https://cmake.org/Bug/view.php?id=15794#c39625
Two questions for the CMake
Hi Francesco,
On 10/10/15 14:34, Gregor Jasny wrote:
> On 06/10/15 16:00, Brad King wrote:
>> Okay, that looks like the underlying issue. The
>> Modules/Platform/Darwin-Initialize.cmake module will have
>> to be taught about this case to do the right thing by default
>
On 06/10/15 16:00, Brad King wrote:
> Okay, that looks like the underlying issue. The
> Modules/Platform/Darwin-Initialize.cmake module will have
> to be taught about this case to do the right thing by default
> if it does not already.
>
> Gregor, do you mind taking a look at this?
Sure.
Hello,
thank you for working on this. This is really hairy stuff.
On 24/09/15 11:10, Ruslan Baratov via cmake-developers wrote:
> Patches help to install universal iOS (device + simulator) libraries by
> triggering some extra instructions (build + fuse) after "regular"
> library installation
Hi,
On 15/09/15 20:24, Stephen Kelly wrote:
> I have merged a Konsole output compute-default-dialect to next for
> testing which implements the automatic detection. Please test it to see
> if it works with xcode 7.
The CompileFeatures test does pass:
$ git describe
v3.3.1-3005-gf1591ef
I
Hello,
from time to time the CMake Dashboard at
http://www.cdash.org/CDash/index.php?project=CMake
is very slow. Right now I cannot access it at all.
Does anyone know what's wrong?
Thanks,
Gregor
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
Hallo,
On 13/08/15 12:56, Ruslan Baratov wrote:
On 13-Aug-15 08:46, Gregor Jasny wrote:
On 13/08/15 01:44, Ruslan Baratov via cmake-developers wrote:
Sending patches with fix. Now it's possible to install simulator
libraries by:
cmake --build _builds --config Release --target install
On 25/08/15 19:01, Brad King wrote:
On 08/24/2015 04:43 PM, Gregor Jasny via cmake-developers wrote:
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
Thanks. Please merge to 'next' when
Hi Eric Brad,
On 15/07/15 12:16, Eric Wing wrote:
On 7/7/15, Brad King brad.k...@kitware.com wrote:
On 07/02/2015 07:54 PM, Eric Wing wrote:
Thank you Brad. When you are ready, let me know how I can help next.
I have basic support with the Xcode generator done.
Please try out this commit:
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:
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
Hello,
On 29/05/15 20:56, Mantis Bug Tracker wrote:
Summary:Issues with the 'Eclipse CDT4 - NMake Makefiles'
Generator
Description:
The project compiles and links in Eclipse but the preprocessor symbols are not
defined by the .cproject file. As a result, sections with
On 15/08/15 21:00, Gregor Jasny wrote:
On 13/08/15 12:56, Ruslan Baratov wrote:
This looks great! I've spent several hours trying to figure out how
'$(EFFECTIVE_PLATFORM_NAME)' can be set to Xcode and some CMake friendly
string to cmake_install.cmake script. I didn't know Xcode understand
On 13/08/15 12:56, Ruslan Baratov wrote:
This looks great! I've spent several hours trying to figure out how
'$(EFFECTIVE_PLATFORM_NAME)' can be set to Xcode and some CMake friendly
string to cmake_install.cmake script. I didn't know Xcode understand
`${VAR}` syntax (probably it didn't, it's
Hi,
On 13/08/15 01:44, Ruslan Baratov via cmake-developers wrote:
Sending patches with fix. Now it's possible to install simulator
libraries by:
cmake --build _builds --config Release --target install -- -sdk
iphonesimulator
and device libraries by:
cmake --build _builds --config Release
Hi,
On 07/08/15 00:43, Ruslan Baratov via cmake-developers wrote:
Hi,
I'm thinking about fixing bug
http://public.kitware.com/Bug/view.php?id=12506 and before I go deeper
in CMake internals just want to ask is there any work-in-progress
attempts already or hints/directions of how it can be
and iOS.
Attached you'll find my proposed patch.
Do you have a better idea to detect the usage of iphone/simulator SDK?
Maybe we should handle this in the platform Darwin modules?
Thanks,
Gregor
From fdbef203172af5d5603de9383077fbb503661f3f Mon Sep 17 00:00:00 2001
From: Gregor Jasny gja
On 07/07/15 10:10, Gregor Jasny wrote:
one of my colleagues is unable to generate a VS2013 solution. He gets
the following error:
Please disregard. This was a vc12 vs. VS2012 confusion.
Sorry for the noise.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
Hello,
one of my colleagues is unable to generate a VS2013 solution. He gets
the following error:
F:\CitrixLibs\ExternalLibs\CMake\3.1.3\Tools_Windows\bin\cmake.exe -G
Visual Studio 12 -T v120_xp -A Win32 -DWITH_COPY_PREBUILT_CACHE=ON
-DWITH_COPY_PREBUILT=ON
Hello Nils,
thank you for the pointers.
On 24/04/15 21:30, Nils Gladitz wrote:
On 24.04.2015 20:55, Gregor Jasny wrote:
Hello,
would it be possible to add generator expression support to CPack
so that I can use $CONFIG within CPACK_PACKAGE_FILE_NAME? I'm
using the CPack module from within my
Hello,
would it be possible to add generator expression support to CPack
so that I can use $CONFIG within CPACK_PACKAGE_FILE_NAME? I'm
using the CPack module from within my CMakeLists.txt.
I'm trying to generate unique file names per architecture and
configuration but multi config generators
Move indent factor change behind indention of start-of-line.
---
Source/cmXCodeObject.cxx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Source/cmXCodeObject.cxx b/Source/cmXCodeObject.cxx
index 33ce8cc..519545a 100644
--- a/Source/cmXCodeObject.cxx
+++
---
Source/cmXCode21Object.cxx | 2 +-
Source/cmXCodeObject.cxx | 5 ++---
2 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/Source/cmXCode21Object.cxx b/Source/cmXCode21Object.cxx
index 855e1ad..96f7b0f 100644
--- a/Source/cmXCode21Object.cxx
+++ b/Source/cmXCode21Object.cxx
@@
This suppresses the extra space that would be generated if the
separator is a space. The conditional block is also used in this
form elsewhere.
---
Source/cmXCodeObject.cxx | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/Source/cmXCodeObject.cxx b/Source/cmXCodeObject.cxx
$ and . do not need to be quoted, but brackets and * must be to
not confuse the Xcode parser.
---
Source/cmXCodeObject.cxx | 2 +-
Tests/RunCMake/XcodeProject/XcodeFileType-check.cmake | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git
---
Source/cmGlobalXCodeGenerator.cxx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Source/cmGlobalXCodeGenerator.cxx
b/Source/cmGlobalXCodeGenerator.cxx
index 2e13692..4d98359 100644
--- a/Source/cmGlobalXCodeGenerator.cxx
+++ b/Source/cmGlobalXCodeGenerator.cxx
@@ -3386,7
Xcode keeps the objects ordered by the object id.
Because cmake stores them into an unordered container
at creation time they must be sorted before writing the
pbxproj file.
---
Source/cmGlobalXCodeGenerator.cxx | 16
Source/cmGlobalXCodeGenerator.h | 1 +
2 files changed, 17
diff after this series was applied.
I have more unfinished patches which further reduce the delta.
Thanks,
Gregor
Gregor Jasny (9):
Xcode: Indent using tabs
Xcode: Sort Xcode objects by Id
Xcode: Add comment after root object
Xcode: Remove extra space in PBXProject comment
Xcode: Properly
---
Source/cmXCode21Object.cxx | 4
Source/cmXCodeObject.cxx | 5 +
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/Source/cmXCode21Object.cxx b/Source/cmXCode21Object.cxx
index 96f7b0f..f30f700 100644
--- a/Source/cmXCode21Object.cxx
+++ b/Source/cmXCode21Object.cxx
@@
---
Source/cmXCodeObject.cxx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Source/cmXCodeObject.cxx b/Source/cmXCodeObject.cxx
index 5a90fd9..33ce8cc 100644
--- a/Source/cmXCodeObject.cxx
+++ b/Source/cmXCodeObject.cxx
@@ -81,7 +81,7 @@ void cmXCodeObject::Indent(int level,
---
Source/cmGlobalXCodeGenerator.cxx | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Source/cmGlobalXCodeGenerator.cxx
b/Source/cmGlobalXCodeGenerator.cxx
index be40c66..2e13692 100644
--- a/Source/cmGlobalXCodeGenerator.cxx
+++ b/Source/cmGlobalXCodeGenerator.cxx
@@
Hello,
I wanted to start documenting our in-company CMake modules. Often I'd
like to refer to some basic CMake commands. As far as I understand the
intersphinx extension [1] should be able to provide that. To reference
remote projects these need to provide a objects.inv mapping file.
But thee
On 17/03/15 20:18, Brad King wrote:
+ target_link_libraries(${target}
+PRIVATE -bundle_loader $TARGET_FILE:${testee})
Please try using this in a CMake source/build tree each with spaces
in the path. Quoting may need updating; perhaps:
target_link_libraries(${target}
Signed-off-by: Gregor Jasny gja...@googlemail.com
---
Tests/CMakeLists.txt | 4 +
Tests/XCTest/CMakeLists.txt| 57 ++
Tests/XCTest/CocoaExample/AppDelegate.h| 6 +
Tests/XCTest/CocoaExample/AppDelegate.m| 18
An XCTest bundle is a CFBundle with a special product-type and bundle
extension. For more information about XCTest visit the Mac Developer
library at:
http://developer.apple.com/library/mac/documentation/DeveloperTools/Conceptual/testing_with_xcode/
Signed-off-by: Gregor Jasny gja
From: Brad King brad.k...@kitware.com
---
Help/release/dev/xcode-xctest.rst | 6 ++
1 file changed, 6 insertions(+)
create mode 100644 Help/release/dev/xcode-xctest.rst
diff --git a/Help/release/dev/xcode-xctest.rst
b/Help/release/dev/xcode-xctest.rst
new file mode 100644
index
From: Brad King brad.k...@kitware.com
Store the version in CMake_TEST_XCODE_VERSION for use by tests that work
with any generator on OS X but may depend on the Xcode version providing
the tools.
---
Tests/CMakeLists.txt | 12
1 file changed, 12 insertions(+)
diff --git
version for any generator on OS X
Help: Add notes for topic 'xcode-xctest'
Gregor Jasny (3):
OS X: Add handling for XCTest bundles
OS X: Add FindXCTest module
Tests: Add XCTest example to test Frameworks and Cocoa App Bundles
Help/manual/cmake-modules.7.rst| 1
For mode 2 the first argument is not the literal NAME
but the package name.
Signed-off-by: Gregor Jasny gja...@googlemail.com
---
Modules/FindPackageHandleStandardArgs.cmake | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Modules/FindPackageHandleStandardArgs.cmake
b/Modules
Signed-off-by: Gregor Jasny gja...@googlemail.com
---
Tests/Environment/main.cxx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Tests/Environment/main.cxx b/Tests/Environment/main.cxx
index 2e1bf4c..b54a664 100644
--- a/Tests/Environment/main.cxx
+++ b/Tests/Environment
Suprisingly new-style tests support generater expressions
also within all test properties. Add a test for that.
Signed-off-by: Gregor Jasny gja...@googlemail.com
---
Tests/Environment/CMakeLists.txt | 12
1 file changed, 12 insertions(+)
diff --git a/Tests/Environment
On 07/03/15 22:20, Gregor Jasny wrote:
Surprisingly new-style tests support generator expressions
also within all test properties. Add a test for that.
This still lacks documentation. The question is what would be the proper
place(s) for this.
I'd add extend the genex note here:
http
Signed-off-by: Gregor Jasny gja...@googlemail.com
---
Help/manual/cmake-modules.7.rst | 1 +
Help/module/XCTestUtilities.rst | 1 +
Modules/XCTestUtilities.cmake | 139
3 files changed, 141 insertions(+)
create mode 100644 Help/module
Signed-off-by: Gregor Jasny gja...@googlemail.com
---
Tests/CMakeLists.txt | 13 +
Tests/XCTest/CMakeLists.txt| 59 ++
Tests/XCTest/CocoaExample/AppDelegate.h| 7 +
Tests/XCTest/CocoaExample/AppDelegate.m| 18
Signed-off-by: Gregor Jasny gja...@googlemail.com
---
Tests/CMakeLists.txt | 17 ++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/Tests/CMakeLists.txt b/Tests/CMakeLists.txt
index 6afedf2..a2e2e24 100644
--- a/Tests/CMakeLists.txt
+++ b/Tests/CMakeLists.txt
Hello Brad,
thank you for the review. In addition to the last series I added a test
case also for the Makefile generator.
On 26/02/15 15:50, Brad King wrote:
The basic functionality is in good shape. My remaining comments
are on the XCTestUtilities module that I hadn't fully reviewed
before:
Ninja build system does not support a in-Makefile verbositiy
switch. So we use cmake --build as a fall back to extract the
CMAKE_VERBOSE_MAKEFILE property and pass it as an optional
-v argument to Ninja.
Signed-off-by: Gregor Jasny gja...@googlemail.com
---
Source/CPack/cmCPackGenerator.cxx
Hello,
For our CI and production build we call cmake --build to execute the
actual build. To be able to examine the build logs we added
-DCMAKE_VERBOSE_MAKEFILE=ON to the configuration step. This worked as
expected for the Makefile generator but is ignored for Ninja.
As far as I understand the
Signed-off-by: Gregor Jasny gja...@googlemail.com
---
Tests/CMakeLists.txt | 13 +
Tests/XCTest/CMakeLists.txt| 62 ++
Tests/XCTest/CocoaExample/AppDelegate.h| 7 +
Tests/XCTest/CocoaExample/AppDelegate.m| 18
1 - 100 of 153 matches
Mail list logo