Re: [cmake-developers] Objective-C support

On Fri, Feb 14, 2014 at 18:02:18 -0500, Sean McBride wrote: > What I mean is that with C++, and STL especially, it's hard to build a > library with a given compiler/standard library combination and link > that library into an executable built with a different > compiler/standard library combination

Re: [cmake-developers] Objective-C support

I was really looking for a way to add the the STL library as a library on the command line and then I realized that I had forgotten that on the Mac, the Objective-C++ compiler driver is clang++/g++. I was only thinking about clang/gcc. Sorry for the noise. On Feb 14, 2014, at 4:02 PM, Sean

Re: [cmake-developers] Objective-C support

On Fri, 14 Feb 2014 17:47:00 -0500, Ben Boeckel said: >> Same in 10.7 and 10.8, and any OS really, since C++ ABIs are not super >> stable. > >Hmm? The only one I know of recently is 4.7.0 and 4.7.1 breaking >std::string ABI with C++11 support enabled (4.7.2 fixed it to be >compatible with < 4.7.0

Re: [cmake-developers] Objective-C support

On Fri, Feb 14, 2014 at 17:22:13 -0500, Sean McBride wrote: > Same in 10.7 and 10.8, and any OS really, since C++ ABIs are not super > stable. Hmm? The only one I know of recently is 4.7.0 and 4.7.1 breaking std::string ABI with C++11 support enabled (4.7.2 fixed it to be compatible with < 4.7.0 a

Re: [cmake-developers] Objective-C support

On Fri, 14 Feb 2014 15:14:23 -0700, Steve Wilson said: >On Mavericks (OS X 10.9) there are two STL implementations: libstdc++ >and libc++. That was also the case in 10.7 and 10.8. In 10.9 the default changed from libstdc++ to libc++ though. >I’m adding support for Objective-C++ and on Maveric

Re: [cmake-developers] Objective-C support

On Mavericks (OS X 10.9) there are two STL implementations: libstdc++ and libc++. I’m adding support for Objective-C++ and on Mavericks it matters which C++ library is used for linking. Is there a standard mechanism already in place for handling the difference in CMake. I checked for the -

Re: [cmake-developers] visual-studio-preprocessor-undefine fix for /U problems

I pushed a updated version of the topic branch to stage. It refactors the OutputPreprocessorDefinitions method into a a new method OutputDefinitionsByTag and adds an argument that lets you specify the tag.I also fixed the test case. SteveW On Feb 14, 2014, at 11:26 AM, Brad King wrote:

Re: [cmake-developers] visual-studio-preprocessor-undefine fix for /U problems

On 2/14/2014 3:48 PM, Steve Wilson wrote: > In the refactor of these functions, would you like to see that > refactor as a separate commit or merged in with the commit for > the other changes? I have a slight preference for a separate commit that first factors the common part out and calls it from

Re: [cmake-developers] visual-studio-preprocessor-undefine fix for /U problems

On Feb 14, 2014, at 11:26 AM, Brad King wrote: > On 2/13/2014 7:33 PM, Steve Wilson wrote: >> The topic is visual-studio-preprocessor-undefine. > > Thanks. The method > > cmVisualStudioGeneratorOptions > ::OutputUndefinePreprocessorDefinitions > > appears to duplicate a lot of code from > >

Re: [cmake-developers] Objective-C support

On 2/14/2014 3:08 PM, Steve Wilson wrote: > the preference I do have is for the OBJC (OBJCXX) form simply because > it matches the capital cases of C and CXX in the CMAKE_* variables We do have "Fortran" already: CMAKE_Fortran_FLAGS, etc. but this is a valid point: CMAKE_OBJC_FLAGS CMAKE_OBJCXX

Re: [cmake-developers] Objective-C support

On Feb 14, 2014, at 12:06 PM, Brad King wrote: > On 2/13/2014 7:35 PM, Steve Wilson wrote: >> The topic name is ‘objective-c-support.’ > > Currently if CXX is enabled then .m sources get compiled as CXX. > See Modules/CMakeCXXCompiler.cmake.in: > > set(CMAKE_CXX_SOURCE_FILE_EXTENSIONS C;M;c++;

[cmake-developers] [CMake 0014756]: RFE: Report changes to cached values

The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=14756 == Reported By:Ben Boeckel Assigned To:

Re: [cmake-developers] Objective-C support

On 2/13/2014 7:35 PM, Steve Wilson wrote: > The topic name is ‘objective-c-support.’ Currently if CXX is enabled then .m sources get compiled as CXX. See Modules/CMakeCXXCompiler.cmake.in: set(CMAKE_CXX_SOURCE_FILE_EXTENSIONS C;M;c++;cc;cpp;cxx;m;mm;CPP) In order to be compatible we need to mak

Re: [cmake-developers] visual-studio-preprocessor-undefine fix for /U problems

Will do. On Feb 14, 2014, at 11:26 AM, Brad King wrote: > On 2/13/2014 7:33 PM, Steve Wilson wrote: >> The topic is visual-studio-preprocessor-undefine. > > Thanks. The method > > cmVisualStudioGeneratorOptions > ::OutputUndefinePreprocessorDefinitions > > appears to duplicate a lot of code

Re: [cmake-developers] visual-studio-preprocessor-undefine fix for /U problems

On 2/13/2014 7:33 PM, Steve Wilson wrote: > The topic is visual-studio-preprocessor-undefine. Thanks. The method cmVisualStudioGeneratorOptions ::OutputUndefinePreprocessorDefinitions appears to duplicate a lot of code from cmVisualStudioGeneratorOptions ::OutputPreprocessorDefinitions Pl

Re: [cmake-developers] Objective-C support

Yes, it does, less support for Objective-C++. I haven’t add support for Objective-C++.It shouldn’t be too hard to add support for Objective-C++ though. On Feb 14, 2014, at 8:42 AM, Sean McBride wrote: > On Thu, 13 Feb 2014 17:35:42 -0700, Steve Wilson said: > >> I just pushed a small t

Re: [cmake-developers] Objective-C support

On Thu, 13 Feb 2014 17:35:42 -0700, Steve Wilson said: >I just pushed a small topic branch to stage the introduces support for >Objective-C as a ‘supported’ language with a separate identity from C/ >CXX. The topic name is ‘objective-c-support.’ Does that solve this by any chance:

[cmake-developers] [CMake 0014755]: Cannot use VisualStudio 2013 Express with Windows7.1SDK for 64Bit builds

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=14755 == Reported By:jest Assigned To: ==