[cmake-developers] How to speed up CMake configuration on macOS

2019-03-23 Thread Gregor Jasny via cmake-developers

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 need to install all required packages:

brew install curl expat jsoncpp libarchive rhash libuv xz zstd

Then configure with:
  -DCMAKE_USE_SYSTEM_LIBRARIES=ON
  -DLibArchive_ROOT=$(brew --prefix libarchive)

Speeup:

  embeddedsystem
  Ninja   103s   14s
  Xcode   749s   67s

Cheers,
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:
https://cmake.org/mailman/listinfo/cmake-developers


[cmake-developers] Specification for CTest XML format

2019-03-05 Thread Gregor Jasny via cmake-developers

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



baz
./subdir
./subdir/baz

/Users/gjasny/Git/Experimental/PP-970-test-case/_build/main


But if I change the WORKING_DIRECTORY property of a test


add_test(NAME custom_workdir COMMAND main)
set_property(TEST custom_workdir PROPERTY WORKING_DIRECTORY /tmp)


it suddenly affects the Path:


custom_workdir
/tmp
/tmp/custom_workdir

/Users/gjasny/Git/Experimental/PP-970-test-case/_build/main


What is Path and FullName supposed to contain?

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:
https://cmake.org/mailman/listinfo/cmake-developers


Re: [cmake-developers] [ANNOUNCE] CMake 3.14.0-rc3 is ready for testing

2019-03-04 Thread Gregor Jasny via cmake-developers

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!

-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:
https://cmake.org/mailman/listinfo/cmake-developers


Re: [cmake-developers] Properly Documenting a CMake Module

2019-02-14 Thread Gregor Jasny via cmake-developers

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 produce the documentation but I 
can't seem to figure out how.


The standard modules that ship with cmake all have this ".rst" section 
at the top that seems to magically get extracted and turned into online 
documentation with sphinx, but I just can't figure out how they do it.


The standard modules have a shadow hierarchy at Help/module. For example

https://gitlab.kitware.com/cmake/cmake/blob/master/Help/module/GNUInstallDirs.rst

contains

.. cmake-module:: ../../Modules/GNUInstallDirs.cmake

There's no magic happening.

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:
https://cmake.org/mailman/listinfo/cmake-developers


Re: [cmake-developers] RfD: deprecate link_directories() and link_libraries()

2018-08-21 Thread Gregor Jasny via cmake-developers

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 anymore, given that now even the
pkg-config module can (and does) return absolute paths to the libraries.


What harm does their presence cause?

Please ask on the user list to see if people are using them.

I suspect they may be used by some projects to link to special runtime
libraries when cross-compiling.  We'd need to make sure there is a
better way for all such use cases before deprecating the commands.


We use link_directories() on Windows to give the windows linker the path 
to the boost libraries. Those use '#pragma comment lib' to link required 
libs.


How would one deal with '#pragma comment lib' w/o link_directories()?

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:
https://cmake.org/mailman/listinfo/cmake-developers


Re: [cmake-developers] iOS friendly CMake

2018-04-02 Thread Gregor Jasny via cmake-developers
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:
https://gitlab.kitware.com/gjasny/cmake/commits/17870-iphone-friendly-cmake

It would be nice if you could give the branch a try. But please note the
list of open todos within the issue.

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:
https://cmake.org/mailman/listinfo/cmake-developers


[cmake-developers] iOS friendly CMake

2018-01-16 Thread Gregor Jasny via cmake-developers

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 add your 
development team: -DCMAKE_XCODE_ATTRIBUTE_DEVELOPMENT_TEAM=ABCDEFG


The merge request is here:
https://gitlab.kitware.com/cmake/cmake/merge_requests/1664

Please give it a try and add any comments you have to the merge 
requests. I only tested it with Xcode 9 on High Sierra so far.


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:
https://cmake.org/mailman/listinfo/cmake-developers


Re: [cmake-developers] Extending XCode scheme generation support

2017-10-02 Thread Gregor Jasny via cmake-developers
Hello Steven,

On 9/22/17 3:36 AM, Steven Velez wrote:
> # Property-Centric
> In this proposal, the generation of the scheme files is customized primarily 
> by
> a user setting additional, specialized properties on a given target, which 
> then
> affect the generation of the scheme files associated with that target.
thank you for working an the scheme proposal. I also believe that the
property-centric approach is better suited and easier to implement than
the file-centrix one.

Next steps would be to sequence the necessary changes and define test
cases. I could imagine that adding generator-expression support would be
much harder to implement that other things.

Things that also should be considered are:
* differences between macOS and iOS when generating a scheme
* what should happen if two targets specify the same schema name

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] Xcode source file type

2017-05-14 Thread Gregor Jasny via cmake-developers
Hello,

On 5/14/17 1:17 AM, James Touton wrote:
> The Xcode generator currently attempts to set the lastKnownFileType
> attribute for every source file in a target.  There's a property that
> allows the user to set this value explicitly, but if the property is not
> set, the generator comes up with an appropriate value based on the file
> extension.  For any file extension the generator does not know about, it
> set a value of "sourcecode".
> 
> I'd like to remove all of these defaults.  In all cases I'm aware of, Xcode
> will fill in the same value that CMake does, except that it doesn't default
> to the "sourcecode" value for extensions it doesn't know about.  Xcode has
> a much wider set of known file types than CMake does, and can do a much
> better job filling in these values.
> 
> In particular, I'd most like to get rid of the "sourcecode" default,
> because that tends to completely screw up syntax highlighting for file
> types that Xcode already knows about.
> 
> Would there be any objection to me submitting a pull request for any of the
> above?

I'd welcome any attempts to simplify the Xcode generator. But before I'd
ack such a PR I'd like to know why this functionality was added in the
first place. CMake still supports (does not actively break) Xcode 3. If
there is no answer to that question: maybe you could test and limit your
changes to a newer Xcode version (like 5 or above).

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] Help needed: debug a xcodebuild hang

2017-05-02 Thread Gregor Jasny via cmake-developers
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 working in the Xcode team.

Any help is appreciated!

Thanks,
Gregor

[1] https://gitlab.kitware.com/cmake/cmake/issues/16752
-- 

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] Nighly build of CMake release branch available?

2017-04-25 Thread Gregor Jasny via cmake-developers

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 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] Email addresses of Mantis bug reporters

2017-03-29 Thread Gregor Jasny via cmake-developers
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: 
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] One Xcode project per project() call?

2017-02-24 Thread Gregor Jasny via cmake-developers
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
> _build_xcode/Source/kwsys/cmsys.xcodeproj
> _build_xcode/Utilities/cmbzip2/bzip2.xcodeproj
> _build_xcode/Utilities/cmcompress/CMCompress.xcodeproj
> _build_xcode/Utilities/cmcurl/CURL.xcodeproj
> _build_xcode/Utilities/cmjsoncpp/JsonCpp.xcodeproj
> _build_xcode/Utilities/cmlibarchive/libarchive.xcodeproj
> _build_xcode/Utilities/cmliblzma/CMLIBLZMA.xcodeproj
> _build_xcode/Utilities/cmlibrhash/librhash.xcodeproj
> _build_xcode/Utilities/cmlibuv/libuv.xcodeproj
> _build_xcode/Utilities/cmzlib/CMZLIB.xcodeproj
> _build_xcode/Utilities/Doxygen/CMakeDeveloperReference.xcodeproj
> _build_xcode/Utilities/Sphinx/CMakeHelp.xcodeproj

Is that intentional?

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] Mirror CMake release files on GitHub?

2017-02-05 Thread Gregor Jasny via cmake-developers
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)

There seems to be a quite nice command line utility which supports
uploading files to releases, so that process should not involve too much
effort: https://github.com/aktau/github-release

What do you think?

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] require-tr1 topic

2016-12-29 Thread Gregor Jasny via cmake-developers
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 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] Boost 1.63 support

2016-12-27 Thread Gregor Jasny via cmake-developers
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 necessary at all, couldn't they be added in
speculative batches of 10 or so?

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] cm(Generator)Target::IsFrameworkOnApple

2016-11-17 Thread Gregor Jasny via cmake-developers
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 important involves classes like the various generators, target,
makefile, etc? I sometimes wonder where to place a new function and
would like to get some more background.

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] Developer workflow with gitlab

2016-10-31 Thread Gregor Jasny via cmake-developers
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 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] -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" -DCMAKE_OSX_SYSROOT:STRING=/ broken in 3.7.0-rc2

2016-10-31 Thread Gregor Jasny via cmake-developers
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 in cmake 3.7.0 as it no longer properly
>> honors the combination...
>>
>> -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" -DCMAKE_OSX_SYSROOT:STRING=/
> 
> I think I revert my change and also completely remove the deployment
> target mismatch because I cannot see a way to query SDK versions for
> Command Line Tools installs.

I put my changes into fix-macos-sysroot topic and merged to next.

See:
https://cmake.org/gitweb?p=stage/cmake.git;a=shortlog;h=refs/heads/fix-macos-sysroot

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] -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" -DCMAKE_OSX_SYSROOT:STRING=/ broken in 3.7.0-rc2

2016-10-30 Thread Gregor Jasny via cmake-developers
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...
> 
> -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" -DCMAKE_OSX_SYSROOT:STRING=/

I think I revert my change and also completely remove the deployment
target mismatch because I cannot see a way to query SDK versions for
Command Line Tools installs.

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] -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" -DCMAKE_OSX_SYSROOT:STRING=/ broken in 3.7.0-rc2

2016-10-30 Thread Gregor Jasny via cmake-developers
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="" -DCMAKE_OSX_SYSROOT:STRING=/
> while allowing your hack to function when
> -DCMAKE_OSX_DEPLOYMENT_TARGET is not an empty string...


Some questions:
1) Is "xcodebuild -sdk / -version SDKVersion" returning the proper
version? I bet not because you called / an invalid argument.

2) Would it make sense to perform some pre-checks before applying my
"hack" in case sdk is a path? For example if it starts with the output
of "xcode-select --print-path"

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] -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" -DCMAKE_OSX_SYSROOT:STRING=/ broken in 3.7.0-rc2

2016-10-30 Thread Gregor Jasny via cmake-developers
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 #16323 again:

> ~/src/cmake/_build/bin/cmake 
> -DCMAKE_OSX_SYSROOT=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk
>  -DCMAKE_OSX_DEPLOYMENT_TARGET=10.10 -GXcode ..
> -- The C compiler identification is AppleClang 8.0.0.842
> -- The CXX compiler identification is AppleClang 8.0.0.842
> CMake Error at /Users/jasny/src/cmake/Modules/Platform/Darwin.cmake:76 
> (message):
>   CMAKE_OSX_DEPLOYMENT_TARGET is '10.10' but CMAKE_OSX_SYSROOT:
> 
>
> "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk"
> 
>   is not set to a MacOSX SDK with a recognized version.  Either set
>   CMAKE_OSX_SYSROOT to a valid SDK or set CMAKE_OSX_DEPLOYMENT_TARGET to
>   empty.
> Call Stack (most recent call first):
>   /Users/jasny/src/cmake/Modules/CMakeSystemSpecificInformation.cmake:26 
> (include)
>   CMakeLists.txt
> 
> 
> -- Configuring incomplete, errors occurred!
> See also "/Users/jasny/tmp/cm/_build/CMakeFiles/CMakeOutput.log".



-- 

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] -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" -DCMAKE_OSX_SYSROOT:STRING=/ broken in 3.7.0-rc2

2016-10-30 Thread Gregor Jasny via cmake-developers
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 Howarth wrote:
> Gregor,
> This is also a severe regression because if forces the cmake
> users to build against the 10.12 SDK on 10.11 which is not well tested
> for backward compatibility on 10.11. Your change makes it impossible
> to build against the SDK in / installed by the Xcode Command Line
> Tools package.

What do you mean with SDK installed into "/"? I was under the impression
that the Command Line Tools package is installed automatically by Xcode
after first start. I thought it provides the /usr/bin/clang etc.

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] [PATCH] Fix RunCMake.Framework on case sensitive file systems.

2016-08-09 Thread Gregor Jasny via cmake-developers
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.
>  https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=677e73cb

Clang will get a warning for those kind of errors[1] regarding header
files. Would it make sense to add similar warning-functionality to CMake?

Thanks,
Gregor

[1] http://lists.llvm.org/pipermail/cfe-dev/2016-April/048406.html
-- 

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] Email feed for new CMake bugs

2016-08-09 Thread Gregor Jasny via cmake-developers
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

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] iOS combined, some fixes

2016-06-25 Thread Gregor Jasny via cmake-developers
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 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] iOS combined, some fixes

2016-06-15 Thread Gregor Jasny via cmake-developers
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 100% reproducible for you? And do you know what goes wrong?

Does the

   list(LENGTH _lipo_path len)
   if(NOT len EQUAL 1)

take paths with spaces into account?

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] CMake 3.5.2 conflates OSX SDK version with target deployment

2016-05-23 Thread Gregor Jasny via cmake-developers
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 warning originates from times where Xcode bundled two
SDKs and CMake was not sure which one to pick if there was no direct match
between of the deployment target version.

I would keep the warning but document the mechanics between SYSROOT and
Deployment Target. The warning then could refer to the docs.

In the long term CMake should provide a tool chain file for OSX and iOS.

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] CLang error when building iOS bundle

2016-05-11 Thread Gregor Jasny via cmake-developers
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?
> 
> Does any one have a hint what could be wrong?

I cannot see any suspicious things, either (besides that -arch armv7 is
listed twice). I would suggest you create a new user on the machine and
try there. Or you could remove ~/Library/Developer/Xcode/DerivedData first.

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] Integration of clang-tidy

2016-04-27 Thread Gregor Jasny via cmake-developers
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 contains the command line for `clang-tidy` as a ;-list.

I'm wondering what's the advantage of having this built-in support for
clang tidy over using the generated compile command database instead?

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] Making shared xcscheme files for Xcode from Cmake

2016-03-31 Thread Gregor Jasny via cmake-developers
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 we use in the office.
> * It only supports command line args and whether to run as root or not (but 
> this was all we needed for now).
> 
> If you have any use for it, feel free to use it. If it could be useful as a 
> basis for a more integrated module then that would also be fine.

Thank you for working on this. Schema creation is a longstanding user
request? Could you modify your generator so that one can combine
multiple targets to into one schema? Or will that require knowledge of
the target UUID from the xcodeproj file?

Some time ago I looked into adding a schema generator purely implemented
as a CMake module but came to the conclusion that it is not a viable
approach without CMake modifications. Especially the unstable UUIDs
across project re-generation gave me some headaches. So I decided that a
schema generator would best fit best within the Xcode generator.

Now there's the first task defining requirements and creating an useful
and extensible CMake language API for schema generation.

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] [CMake 0016030]: CMAKE_ASM_NASM_COMPILE_OBJECT lacks

2016-03-25 Thread Gregor Jasny via cmake-developers
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 done for all other languages
> in commit v3.4.0-rc1~342^2 (Factor an  placeholder out
> of  in rule variables, 2015-07-13):
> 
>   Factor an  placeholder out of  in rule variables
>   https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c736de7b
> 
> Since prior to that change the -I flags were included in 
> I think leaving ASM changes out of the commit was an oversight.

I pushed a first commit to asm-includes topic but did not merge to next,
yet. Looking at your quoted patch I wonder if  is missing as well?

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] [CMake 0016030]: CMAKE_ASM_NASM_COMPILE_OBJECT lacks

2016-03-25 Thread Gregor Jasny via cmake-developers
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 (non-complete) list:

> Modules/CMakeASM-ATTInformation.cmake:set(CMAKE_ASM${ASM_DIALECT}_COMPILE_OBJECT
>  "  -o  ")
> Modules/CMakeASMInformation.cmake:  
> set(CMAKE_ASM${ASM_DIALECT}_COMPILE_OBJECT 
> "-o  
> -c ")
> Modules/CMakeASM_MASMInformation.cmake:set(CMAKE_ASM${ASM_DIALECT}_COMPILE_OBJECT
>  "/c  /Fo 
>  ")
> Modules/CMakeASM_NASMInformation.cmake:set(CMAKE_ASM_NASM_COMPILE_OBJECT 
> "  -f ${CMAKE_ASM_NASM_OBJECT_FORMAT} -o 
>  ")
> Modules/Compiler/ARMCC-ASM.cmake:set(CMAKE_ASM_COMPILE_OBJECT   
> "  -o  ")
> Modules/Compiler/IAR-ASM.cmake:set(CMAKE_ASM_COMPILE_OBJECT  
> " -o ")
> Modules/Compiler/TI-ASM.cmake:set(CMAKE_ASM_COMPILE_OBJECT  
> " --compile_only --asm_file=   
>  --output_file=")
> Modules/Platform/gas.cmake:set(CMAKE_ASM${ASM_DIALECT}_COMPILE_OBJECT 
> "  -o  ")

Does anyone see a reason to *not* prepend all  with a ?

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] [CMake 0015992]: Xcode generator's ReRunCMake.make fails if dependencies have been deleted

2016-02-28 Thread Gregor Jasny via cmake-developers
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 Makefile will fail with a "no
> rule to make target <…>" error. This happens pretty frequently if you have a
> CMake script that reads the ref file for your current git branch and you 
> delete
> branches regularly, and can also happen if you make other build system 
> changes.
> 
> This can be solved by wrapping each item in the list with `$(wildcard 
> )`,
> which effectively makes the dependencies optional.

Brad: I pushed and merged the xcode-regenerate-on-deleted-files topic
but I'm unsure about the test location itself and if this is a feature
all generators should provide. I tested it with Xcode, Make, and Ninja.

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] Patch: refactor XCode blocks writing function

2016-02-21 Thread Gregor Jasny via cmake-developers
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 this for us was adding support for XCode UI 
> Testing (as opposed to non-UI testing), which required us to add the target 
> ID in a nested way that wasn't supported with the previous code. I will send 
> the XCode UI Testing patch separately.

I will review this patch and push it into -next.

One kind request: Could you please install the developer hooks locally
so that you will get the same warnings and pre-commit errors like the
cmake developers? As far as I remember you can set it up by calling

Utilities/GitSetup/setup-hooks

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] Drop support for older Xcode versions?

2016-02-19 Thread Gregor Jasny via cmake-developers

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 exactly does not work for you with Xcode 6/7?

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] Drop support for older Xcode versions?

2016-02-06 Thread Gregor Jasny via cmake-developers
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 talking here about the Xcode generator which creates Xcode
projects, not the Makefile or Ninja generator.

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] Xcode generator is adding old attributes on .pbxproj

2016-02-06 Thread Gregor Jasny via cmake-developers
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 would be a superb start.

Note: you could use the xcproj tool to ask Xcode to re-generate the
project by running "xcproj touch".

I also intend to work on generating schema directly from CMake but this
will take some time.

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] [PATCH] Proposed fix for bug 15183

2016-01-30 Thread Gregor Jasny via cmake-developers
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 only for
> shared libraries). This seems almost certainly undesirable so I've moved
> the code inside the shared library check.

Thank you for the patch. It improves the situation but does not fix it
completely. Nevertheless I will push it to -next as soon as unit test
are green locally.

The case where it does not work is the following:

> cmake_minimum_required(VERSION 3.4 FATAL_ERROR)
> 
> add_library(mystatic STATIC main.c)
> add_library(myshared SHARED main.c)

The myshared library has "@rpath" in the install dir attribute. I guess
the MACOSX_RPATH target property interferes here. I will have a look at
this but certainly the second part of the fix will miss the CMake 3.5
freeze.

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] Anyone going to FOSDEM?

2015-12-30 Thread Gregor Jasny via cmake-developers
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 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.

2015-12-13 Thread Gregor Jasny via cmake-developers
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.

2015-12-13 Thread Gregor Jasny via cmake-developers
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


Re: [cmake-developers] Please comment on ios-universal topic

2015-12-09 Thread Gregor Jasny via cmake-developers

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?


Right. Any objections to that property name?

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] Static Bootstrap: CCMake & GPM

2015-12-08 Thread Gregor Jasny via cmake-developers

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':


Could you please post the content of 
/usr/lib/x86_64-linux-gnu/pkgconfig/ncurses.pc ?



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] Please comment on ios-universal topic

2015-12-08 Thread Gregor Jasny via cmake-developers
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 think that
providing a different property for libraries, frameworks and app bundles
is not really helpful. To combine all targets one could set the CMAKE_
prefixed variable, to combine only some, one could set the property on
the target itself.

Deploying applications which support both armv7 (32bit) and armv8
(64bit) is already working by setting both architectures in the
OSX_ARCHITECTURES property because both are covered by the device SDK.

So technically we already support UNIVERSAL libraries. What we don't
support is combining device and simulator builds. So how about replacing
UNIVERSAL with COMBINED?

IOS_INSTALL_COMBINED_BINARY

I'm not sure if dropping the IOS bundle currently makes sense. At the
moment just iOS (and watchOS, tvOS) is the odd platfrom which requires
work-arounds.

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] Please comment on ios-universal topic

2015-12-01 Thread Gregor Jasny via cmake-developers
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 adding more tests during the next days.

Thank you,
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] [PATCH] CMake 3.4.0rc3 Apple documentation update

2015-11-11 Thread Gregor Jasny via cmake-developers

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 documentation. Please take a look at attachment.


Thank you for extending the documentation. The problem I see is that 
besides MacOSX and iOS there is now also watchOS and tvOS. Do we want to 
mention them explicitely or is there a nice "umbrella" word for them?

--

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] iOS Framework Bundle support

2015-11-10 Thread Gregor Jasny via cmake-developers
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 creating correct iOS 
> Frameworks Bundle.
> For iOS Frameworks, not versioned Bundle is needed, eg.:
> 
>   iOSFramework.framework/
>   iOSFramework
>   Info.plist
>   Headers
> 
> 
> 
> Unfortunately with current version of CMake (3.4.0), it produces OS X 
> Framework Bundle, with versions inside, eg.:
> 
>   MyFramework.framework/
> MyFramework -> Versions/Current/MyFramework
> Resources -> Versions/Current/Resources
> Versions/
> A/
> MyFramework
> Headers
> Resources/
>  Info.plist
> Current -> A
> 
> 
> 
> You could test it with my example project in attachment 
> (cmake_shared_ios_framework.zip).

Unfortunately I cannot reproduce the problem. Could you please write
down the exact steps you took to compile the example in the zip file?
Please also Xcode and cmake version.

That's what I see (cmake master, Xcode generator and Xcode 7.1):

$ find _build/shared_empty/mul/Debug-iphonesimulator/mul.framework
_build/shared_empty/mul/Debug-iphonesimulator/mul.framework
_build/shared_empty/mul/Debug-iphonesimulator/mul.framework/Headers
_build/shared_empty/mul/Debug-iphonesimulator/mul.framework/Headers/mul.h
_build/shared_empty/mul/Debug-iphonesimulator/mul.framework/Info.plist
_build/shared_empty/mul/Debug-iphonesimulator/mul.framework/Modules
_build/shared_empty/mul/Debug-iphonesimulator/mul.framework/Modules/module.modulemap
_build/shared_empty/mul/Debug-iphonesimulator/mul.framework/mul

> The iOS Application Bundle was already fixed in CMake 3.4.0. Unfortunately 
> still iOS Frameworks are not produced correctly (Xcode refuses to sign such 
> Frameworks if you would like to push it into iOS device).
> 
> In attachment I added solution to produce correct iOS Framework (for OSX 
> Frameworks will be produced normally).
> 
> 
> 
> Could you please give some comment about that?
> 
> Do you think architecture of that solution is correct?

I'd go for an early return from cmOSXBundleGenerator::CreateFramework if
we're building for iOS. The code of CreateIOSFramework is just too similar.

> I would like to do next:
> 
> - Refactor code, to have more explicitly names (OSX, iOS or Apple)
> 
> - Update documentation
> 
> - add some unit tests for creating iOS Frameworks

I would like to see a test for that topic. If you'd like to try please
have a look at:
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=744e6c497c01cb3a3129ca66d1cabfa83e17dbd4
https://cmake.org/gitweb?p=cmake.git;a=tree;f=Tests/RunCMake/XcodeProject;hb=HEAD
https://cmake.org/gitweb?p=cmake.git;a=blob;f=Tests/RunCMake/README.rst;hb=HEAD

You need to build cmake via the Xcode generator and run the tests.
During development you can filter just for the XcodeProject tests:

bin/Debug/ctest -R RunCMake.XcodeProject --verbose

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] Patch: install universal iOS libraries

2015-10-27 Thread Gregor Jasny via cmake-developers
Hello,

I hope to have finished the review by end of this week.

On 25/10/15 15:34, Ruslan Baratov wrote:
> +  set(cmd lipo -info "${filename}")

Minor nitpick: lipo should probably be called via xcrun. Otherwise it
might not know how to handle new architectures.

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] Patch: install universal iOS libraries

2015-10-23 Thread Gregor Jasny via cmake-developers
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 CORRESPONDING_*_SDK_NAME variables in Xcode 7.0 but not in 6.4.

At least in Xcode 6.2 I the following variable defined:
SUPPORTED_PLATFORMS="iphonesimulator iphoneos"

It also seems to be set with Xcode 7.1
SUPPORTED_PLATFORMS="watchsimulator watchos"
SUPPORTED_PLATFORMS="appletvos appletvsimulator"

I'd really like to avoid coding any form of database into CMake.
Same for the architectures: In the end the user (or the Xcode default)
sets a list of VALID_ARCHS for device and simulator. Maybe you could use
this for filtering.

I'll reserve a day next week to exclusively work on this topic.

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] cmake Xcode bug clobbering -ObjC/-ObjC++ flags

2015-10-18 Thread Gregor Jasny via cmake-developers
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 developers:

1) I'd like to add an Unit Test for the ExtractFlagRegex function. Could
you please tell me where to add it?

2) Do you consider ExtractFlagRegex generic enough to be moved somewhere
else?

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] Issue on CMAKE_OSX_SYSROOT

2015-10-11 Thread Gregor Jasny via cmake-developers
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
>> if it does not already.

> if (SDK is newer than host) && (is not set CMAKE_OSX_DEPLOYMENT_TARGET)
>   set CMAKE_OSX_DEPLOYMENT_TARGET=
> endif()

Could you please give the following patch to Darwin-Initialize.cmake a try?

https://cmake.org/gitweb?p=stage/cmake.git;a=commit;h=d61c6689c7380c810e060fed6bf3a0b9fbfd41d0

Brad: If we would set in line 33 the CMAKE_OSX_DEPLOYMENT_TARGET cache
variable only if ENV{MACOSX_DEPLOYMENT_TARGET} actually exists we could
get rid of the FORCE attribute later. Would that make sense?

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] Issue on CMAKE_OSX_SYSROOT

2015-10-10 Thread Gregor Jasny via cmake-developers
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. Ironically I just upgraded my workstation to 10.11 some minutes
before :(

What will be the desired behavior here?

At work we always use the lastest SDK (by omitting the versioned suffix)
and just set the deployment target. Works good since some years.

But I guess we want to be more conservative here and stick to old
behavior. How about adding a rule at the end that:

if (SDK is newer than host) && (is not set CMAKE_OSX_DEPLOYMENT_TARGET)
  set CMAKE_OSX_DEPLOYMENT_TARGET=
endif()

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] Patch: install universal iOS libraries

2015-10-07 Thread Gregor Jasny via cmake-developers
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 finished. This behavior controlled by CMake
> variable CMAKE_IOS_INSTALL_UNIVERSAL_LIBS.

some general remarks:

* iOS is not the only platform where the simulator / device situation is
problematic. Others are now watchOS and the upcoming tvOS (see
xcodebuild -showsdks). So it would make sense to replace the ios naming
in the method signatures with something more general.

* Does the patches handle Bundles and Frameworks properly?

* This functionality should be limited to XCODE Generator

0001-

* Could you make the CMAKE_IOS_INSTALL_UNIVERSAL_LIBS a two staged
property like CMAKE_INSTALL_RPATH / INSTALL_RPATH. That way one would be
able to enable this behavior for only some targets

0002-CMake-module-for-universal-iOS-library-install

* Could you avoid to hard-code architecture names like i386 or armv7 in
the module?

* In Xcode 7 (and maybe earlier) I see the following environment
variables when I install for Device:

> export CORRESPONDING_SIMULATOR_PLATFORM_NAME=iphonesimulator
> export CORRESPONDING_SIMULATOR_SDK_NAME=iphonesimulator9.0
> export SUPPORTED_PLATFORMS="iphonesimulator iphoneos"
> export SDK_NAME=iphoneos9.0

for Simulator:

> 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?

> +  install_universal_ios_remove_arch("${dev_libpath}" "i386")
> +  install_universal_ios_remove_arch("${dev_libpath}" "x86_64")

Doing it the other way round (keeping only what's needed) looks saner to me.

> +  install_universal_ios_remove_arch("${dev_libpath}" ...)
> +
> +  install_universal_ios_remove_arch("${sim_libpath}" ...)
> +
> +  set(cmd lipo -create ${src} ${dst} -output ${dst})

Would it be possible to just add selected architectures from src to dst
(via lipo -replace)? That way you would save some disk i/o and would
make the pruning step for src superfluous.

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] xcode7-defaults-to-c11 topic

2015-09-16 Thread Gregor Jasny via cmake-developers
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 compiled and tested with

$ export DEVELOPER_DIR=/Applications/Xcode7.app/Contents/Developer
$ mkdir _build_xcode7 && cd $_
$ cmake -DCMAKE_OSX_SYSROOT=macosx10.11
-DCMAKE_OSX_DEPLOYMENT_TARGET=10.10 -GXcode ..
$ xcodebuild
$ bin/Debug/ctest --verbose -R CompileFeatures

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] CDash broken

2015-09-02 Thread Gregor Jasny via cmake-developers
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: 
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] Fixing bug #12506 (iOS install)

2015-08-26 Thread Gregor Jasny via cmake-developers
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 -- -sdk
 iphonesimulator

 and device libraries by:

   cmake --build _builds --config Release --target install -- -sdk
 iphoneos

 or from Xcode IDE (build target install).

 However this commands will install both libraries to the same location.
 This behaviour can be improved by adding some code that will do lipo of
 all libraries before install (i.e. universal libraries will be
 installed). This can be achieved by using ONLY_ACTIVE_ARCHS=NO while
 running Xcode build. The only question is about making install target
 depends on two type of builds (-sdk iphonesimulator and -sdk iphoneos).

 This was my preliminary work:
 https://github.com/gjasny/CMake/commit/978dca25ac387bdec894a1ba2c934317f5f6169f


 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 just expanded as an
 environment variable). I've tested your fix and it works fine for me.
 Since we don't need to replace string with path manually I think your
 solution is neater. I've added description to commit and rebased it, see
 attachment.

I just pushed the fix-ios-install topic including a test. Basically the
patch changes the invocation line of the script from

cmake -DBUILD_TYPE=Release-iphoneos -P cmake_install.cmake

to

cmake -DBUILD_TYPE=Release -DEFFECTIVE_PLATFORM_NAME=-iphoneos -P
cmake_install.cmake

and within the install script

file(INSTALL DESTINATION ${CMAKE_INSTALL_PREFIX}/lib TYPE
STATIC_LIBRARY FILES .../Release/libfoo.a)


to

file(INSTALL DESTINATION ${CMAKE_INSTALL_PREFIX}/lib TYPE
STATIC_LIBRARY FILES .../Release${EFFECTIVE_PLATFORM_NAME}/libfoo.a)


By keeping the ${EFFECTIVE_PLATFORM_NAME} a variable one is able to use
the same install script for iphoneos and iphonesimulator SDKs.

Please review and merge.

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] Xcode 7 tbd library stub support

2015-08-26 Thread Gregor Jasny via cmake-developers

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 ready.


Test looks good:

-- XcodeFileType - PASSED
-- XcodeAttributeGenex - PASSED
-- XcodeAttributeGenexError - PASSED
-- XcodeObjectNeedsQuote - PASSED
-- XcodePlatformFrameworks - PASSED
-- XcodeBundles - PASSED
-- XcodeBundles-build - PASSED
-- XcodeBundles - PASSED
-- XcodeBundles-build - PASSED
-- XcodeTbdStub - PASSED

https://open.cdash.org/testDetails.php?test=366644123build=3974796

--

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] Adding Swift support to CMake

2015-08-25 Thread Gregor Jasny via cmake-developers
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:

  Add rudimentary support for the Apple Swift language with Xcode
  http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bf112531

I was just digging through OSX 10.11 / Xcode 7 errors and noticed that
the Swift tests fail with Xcode7:

https://open.cdash.org/buildSummary.php?buildid=3972344

 CompileSwift normal x86_64 
 /Users/builder/external/CMake/Tests/SwiftOnly/main.swift
 cd /Users/builder/external/CMake/Tests/SwiftOnly
 
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift
  -frontend -c -primary-file 
 /Users/builder/external/CMake/Tests/SwiftOnly/main.swift -target 
 x86_64-apple-macosx10.11 -enable-objc-interop -sdk 
 /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk
  -I /Users/builder/external/CMake-xcode-dbg-x86_64/Tests/SwiftOnly/Debug -F 
 /Users/builder/external/CMake-xcode-dbg-x86_64/Tests/SwiftOnly/Debug 
 -serialize-debugging-options -Xcc 
 -I/Users/builder/external/CMake-xcode-dbg-x86_64/Tests/SwiftOnly/SwiftOnly.build/Debug/SwiftOnly.build/swift-overrides.hmap
  -Xcc 
 -I/Users/builder/external/CMake-xcode-dbg-x86_64/Tests/SwiftOnly/Debug/include
  -Xcc 
 -I/Users/builder/external/CMake-xcode-dbg-x86_64/Tests/SwiftOnly/SwiftOnly.build/Debug/SwiftOnly.build/DerivedSources/x86_64
  -Xcc 
 -I/Users/builder/external/CMake-xcode-dbg-x86_64/Tests/SwiftOnly/SwiftOnly.build/Debug/SwiftOnly.build/DerivedSources
  -Xcc -DCMAKE_INT
 D
IR=\Debug\ -Xcc 
-working-directory/Users/builder/external/CMake/Tests/SwiftOnly 
-emit-module-doc-path 
/Users/builder/external/CMake-xcode-dbg-x86_64/Tests/SwiftOnly/SwiftOnly.build/Debug/SwiftOnly.build/Objects-normal/x86_64/main~partial.swiftdoc
 -O -module-name SwiftOnly -emit-module-path 
/Users/builder/external/CMake-xcode-dbg-x86_64/Tests/SwiftOnly/SwiftOnly.build/Debug/SwiftOnly.build/Objects-normal/x86_64/main~partial.swiftmodule
 -serialize-diagnostics-path 
/Users/builder/external/CMake-xcode-dbg-x86_64/Tests/SwiftOnly/SwiftOnly.build/Debug/SwiftOnly.build/Objects-normal/x86_64/main.dia
 -emit-dependencies-path 
/Users/builder/external/CMake-xcode-dbg-x86_64/Tests/SwiftOnly/SwiftOnly.build/Debug/SwiftOnly.build/Objects-normal/x86_64/main.d
 -emit-reference-dependencies-path 
/Users/builder/external/CMake-xcode-dbg-x86_64/Tests/SwiftOnly/SwiftOnly.build/Debug/SwiftOnly.build/Objects-normal/x86_64/main.swiftdeps
 -o /Users/builder/external/CMake-xcode-dbg-x86_64/Tests/SwiftOnly/Swif
 t
Only.build/Debug/SwiftOnly.build/Objects-normal/x86_64/main.o
 /Users/builder/external/CMake/Tests/SwiftOnly/main.swift:1:1: error: 
 'println' has been renamed to 'print'
 println(SwiftOnly)
 ^~~
 print
 Swift.println:1:82: note: 'println' has been explicitly marked unavailable 
 here
 @available(*, unavailable) @inline(never) @_semantics(stdlib_binary_only) 
 func printlnT(value: T)

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] [CMake 0015669]: XCTest for iOS target has incorrect TEST_HOST

2015-08-24 Thread Gregor Jasny via cmake-developers

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

2015-08-24 Thread Gregor Jasny via cmake-developers
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


Re: [cmake-developers] [CMake 0015669]: XCTest for iOS target has incorrect TEST_HOST

2015-08-19 Thread Gregor Jasny via cmake-developers
Hello,

On 30/07/15 16:03, Brad King wrote:
 On 07/30/2015 07:38 AM, Gregor Jasny via cmake-developers wrote:
 Do you have a better idea to detect the usage of iphone/simulator SDK?
 Maybe we should handle this in the platform Darwin modules?
 
 This occurs when cross-compiling to iOS, so should we check for
 CMAKE_SYSTEM_NAME set to iOS?  There is already code to do this
 for Android.

The problem I see with this approach is that CMake provides no official
iOS toolchain file (maybe we should?). And the popular cmake-ios project
[1] for example sets SYSTEM_NAME to Darwin.

Maybe we can detect iOS via SDK string for now. If there is a better way
to detect iOS the PlatformIsAppleIos() could easily be changed.

I pushed the ios-app-bundle-layout topic branch together with a test
case. Some words about the patch:

I decided to put the iOS platform detection into cmMakefile and not
cmTarget because I'll need it for another bug (iOS install #12506) later
within cmGlobalGenerator::CreateDefaultGlobalTargets where no target is
available. I also thought about just providing a static function which
only performs the string comparisons but could not find a proper place
for it. From my gut feeling I would have placed it somewhere in a
*Xcode* file. But as far as I understand these files are not built on
non-Apple platforms which would uglify the generic callers.

Please review the topic branch. If you think it would make sense to see
also the ios-install patch and review both in parallel,  I could polish
and push it within the next days.

Thanks,
Gregor

[1] https://code.google.com/p/ios-cmake/source/browse/toolchain/iOS.cmake
-- 

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 0015597]: Issues with the 'Eclipse CDT4 - NMake Makefiles' Generator

2015-08-18 Thread Gregor Jasny via cmake-developers
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

I also stumbled upon this problem and pushed a topic containing a fix:
http://www.cmake.org/gitweb?p=stage/cmake.git;a=shortlog;h=refs/heads/sublime-msvc-includes

Could you please review and if appropriate merge to next?

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] Fixing bug #12506 (iOS install)

2015-08-15 Thread Gregor Jasny via cmake-developers
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
 `${VAR}` syntax (probably it didn't, it's just expanded as an
 environment variable). I've tested your fix and it works fine for me.
 Since we don't need to replace string with path manually I think your
 solution is neater. I've added description to commit and rebased it, see
 attachment.
 
 I start working on a unit test for this now.

I have a first test here:
https://github.com/gjasny/CMake/commit/dcfc8f6f637ffdebe0e7f71ba2768c2acd0811eb

Will add some more during the next days.

-- 

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] Fixing bug #12506 (iOS install)

2015-08-15 Thread Gregor Jasny via cmake-developers
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 just expanded as an
 environment variable). I've tested your fix and it works fine for me.
 Since we don't need to replace string with path manually I think your
 solution is neater. I've added description to commit and rebased it, see
 attachment.

I start working on a unit test for this now.
-- 

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] Fixing bug #12506 (iOS install)

2015-08-12 Thread Gregor Jasny via cmake-developers

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 --target install -- -sdk iphoneos

or from Xcode IDE (build target install).

However this commands will install both libraries to the same location.
This behaviour can be improved by adding some code that will do lipo of
all libraries before install (i.e. universal libraries will be
installed). This can be achieved by using ONLY_ACTIVE_ARCHS=NO while
running Xcode build. The only question is about making install target
depends on two type of builds (-sdk iphonesimulator and -sdk iphoneos).


This was my preliminary work:

https://github.com/gjasny/CMake/commit/978dca25ac387bdec894a1ba2c934317f5f6169f


I will give your patches a try this weekend.

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] Fixing bug #12506 (iOS install)

2015-08-07 Thread Gregor Jasny via cmake-developers

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 done?


I started to look into this and as far as I remember built a PoC for the 
case where you do not build Simulator and non-Simulator within the same 
Xcode project. But I never found the time to write down a summary of 
that complicated topic.


Currently I work around by calling from my build script:
${CMAKE} -DBUILD_TYPE=${CONFIG} -P ${BUILD_DIR}/cmake_install.cmake

I will try to attach something to the bug report within the next days.

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] [CMake 0015669]: XCTest for iOS target has incorrect TEST_HOST

2015-07-30 Thread Gregor Jasny via cmake-developers

Hello,

On 29/07/15 14:07, Mantis Bug Tracker wrote:

==
http://www.cmake.org/Bug/view.php?id=15669
==


this bug caused by different App Bundle layout in MacOSX 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...@googlemail.com
Date: Thu, 30 Jul 2015 13:26:10 +0200
Subject: [PATCH] Fix iOS App Bundle layout

In contrast to Mac OS X App bundle layout the iOS one lacks the
Contents/MacOSX structure. See also the Bundle Structures
documentation in Mac Developer Library:

https://developer.apple.com/library/mac/documentation/CoreFoundation/Conceptual/CFBundles/BundleTypes/BundleTypes.html
---
 Source/cmTarget.cxx | 26 +++---
 Source/cmTarget.h   |  3 +++
 2 files changed, 26 insertions(+), 3 deletions(-)

diff --git a/Source/cmTarget.cxx b/Source/cmTarget.cxx
index cf33791..c39f9c0 100644
--- a/Source/cmTarget.cxx
+++ b/Source/cmTarget.cxx
@@ -632,6 +632,22 @@ bool cmTarget::IsBundleOnApple() const
 }
 
 //
+bool cmTarget::IsIosSdkOnApple() const
+{
+  if (!this-IsApple)
+{
+return false;
+}
+
+  std::string sdkRoot;
+  sdkRoot = this-GetMakefile()-GetSafeDefinition(CMAKE_OSX_SYSROOT);
+  sdkRoot = cmSystemTools::LowerCase(sdkRoot);
+
+  return sdkRoot.find(iphoneos) == 0 ||
+ sdkRoot.find(/iphoneos) != std::string::npos;
+}
+
+//
 static bool processSources(cmTarget const* tgt,
   const std::vectorcmTargetInternals::TargetPropertyEntry* entries,
   std::vectorstd::string srcs,
@@ -6707,9 +6723,13 @@ std::string cmTarget::GetAppBundleDirectory(const 
std::string config,
 bool contentOnly) const
 {
   std::string fpath = this-GetFullName(config, false);
-  fpath += .app/Contents;
-  if(!contentOnly)
-fpath += /MacOS;
+  fpath += .app;
+  if(!this-IsIosSdkOnApple())
+{
+fpath += /Contents;
+if(!contentOnly)
+  fpath += /MacOS;
+}
   return fpath;
 }
 
diff --git a/Source/cmTarget.h b/Source/cmTarget.h
index f567d50..d383219 100644
--- a/Source/cmTarget.h
+++ b/Source/cmTarget.h
@@ -524,6 +524,9 @@ public:
   or CFBundle on Apple.  */
   bool IsBundleOnApple() const;
 
+  /** Return whether this target uses iOS SDK on Apple */
+  bool IsIosSdkOnApple() const;
+
   /** Return the framework version string.  Undefined if
   IsFrameworkOnApple returns false.  */
   std::string GetFrameworkVersion() const;
-- 
2.4.3

-- 

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] How is the Visual Studio compiler looked up

2015-07-07 Thread Gregor Jasny via cmake-developers
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 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] How is the Visual Studio compiler looked up

2015-07-07 Thread Gregor Jasny via cmake-developers
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 -DCMAKE_INSTALL_PREFIX:PATH=C:\Git\med
ia-processing-library\_deploy C:\Git\media-processing-library
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
CMake Error at CMakeLists.txt:7 (project):
  No CMAKE_C_COMPILER could be found.



CMake Error at CMakeLists.txt:7 (project):
  No CMAKE_CXX_COMPILER could be found.



-- Configuring incomplete, errors occurred!
See also
C:/Git/media-processing-library/_build_v120_x86/CMakeFiles/CMakeOutput.log.
See also
C:/Git/media-processing-library/_build_v120_x86/CMakeFiles/CMakeError.log.


Could you please point me to the code which looks up Visual Studio or
the CL.exe compiler? How would you debug this problem?

Thanks,
Gregor
The system is: Windows - 6.1 - AMD64
Compiling the C compiler identification source file CMakeCCompilerId.c failed.
Compiler:  
Build flags: 
Id flags: 

The output was:
The system cannot find the file specified


Compiling the CXX compiler identification source file CMakeCXXCompilerId.cpp 
failed.
Compiler:  
Build flags: 
Id flags: 

The output was:
The system cannot find the file specified


-- 

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