Re: [CMake] problems when upgrading to Xcode v5

[Robert Maynard]

The changes to the XCode generator for support of XCode 5 didn't make it
into RC4.


On Wed, Oct 2, 2013 at 3:06 PM, Sean McBride wrote:

> On Wed, 2 Oct 2013 18:42:16 +, Jeff Schenck said:
>
> >I recently upgraded to Xcode v5 on Mac OSX and started getting build
> >failures.  Below is a simplified project that produces the same problem,
> >followed by the error message generated by Xcode.  The problem occurs
> >with version v5 but not v4.6.x of Xcode.  I'm running CMake 2.8.10.2.
>
> The first thing I would try is updating to 2.8.12rc4.  There have been
> fixes for new Xcode/OS X since 2.8.10.2.
>
> Cheers,
>
> --
> 
> Sean McBride, B. Eng s...@rogue-research.com
> Rogue Researchwww.rogue-research.com
> Mac Software Developer  Montréal, Québec, Canada
>
>
> --
>
> 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://www.cmake.org/mailman/listinfo/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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] try_run() fortran support

[Zaak Beekman]

Please ignore this post; I didn't understand where try_run() was looking
for the source code previously. My most recent post has this resolved, and
a solution to diagnosing the largest available Fortran integer at compile
time so that it can be inserted via an appropriate preprocessing directive
at compile time.

Thanks,
Izaak Beekman
===
(301)244-9367
Princeton University Doctoral Candidate
Mechanical and Aerospace Engineering
ibeek...@princeton.edu

UMD-CP Visiting Graduate Student
Aerospace Engineering
ibeek...@umiacs.umd.edu
ibeek...@umd.edu
--

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

Re: [CMake] problems when upgrading to Xcode v5

[Sean McBride]

On Wed, 2 Oct 2013 18:42:16 +, Jeff Schenck said:

>I recently upgraded to Xcode v5 on Mac OSX and started getting build
>failures.  Below is a simplified project that produces the same problem,
>followed by the error message generated by Xcode.  The problem occurs
>with version v5 but not v4.6.x of Xcode.  I'm running CMake 2.8.10.2.

The first thing I would try is updating to 2.8.12rc4.  There have been fixes 
for new Xcode/OS X since 2.8.10.2.

Cheers,

-- 

Sean McBride, B. Eng s...@rogue-research.com
Rogue Researchwww.rogue-research.com 
Mac Software Developer  Montréal, Québec, Canada


--

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

[CMake] try_compile() to determine the largest available Fortran integer

[Zaak Beekman]

Hi,
I managed to write a macro to determine the largest available Fortran
integer kind so that it can be #defined at compile time where needed--via
compiler supplied preprocessors  or the cpp. The macro I wrote needs some
more refinement/abstraction, but the basic technique is there. I am sharing
it here in the event that someone might find it useful. Others' suggestions
proved very helpful in implementing this, particularly Yngve Inntjore
Levinsen's suggestions. My solution relies on more guarantees  by the
standard, and I feel it is more portable, so long as one has an F95
conforming compiler. (Virtually all compilers released in the past decade
are F95 conforming.) Here is my macro:

macro(Fortran_biggest_int)
  message(STATUS "Checking for the largest available Fortran integer..")
  set(filename ${CMAKE_BINARY_DIR}/getbigint.f90)
  file(WRITE  ${filename} "program getbigint\n")
  file(APPEND ${filename} "  implicit none\n")
  file(APPEND ${filename} "  integer ,parameter :: DEFAULT = kind(1) ,
DEF_RANGE = range(kind(1))\n")
  file(APPEND ${filename} "  integer :: r, ktmp, k\n")
  file(APPEND ${filename} "  r = DEF_RANGE\n")
  file(APPEND ${filename} "  k = DEFAULT\n")
  file(APPEND ${filename} "  do\n")
  file(APPEND ${filename} " r= r + 1\n")
  file(APPEND ${filename} " ktmp = selected_int_kind(r)\n")
  file(APPEND ${filename} " if ( ktmp == -1 ) exit\n")
  file(APPEND ${filename} " k = ktmp\n")
  file(APPEND ${filename} "  end do\n")
  file(APPEND ${filename} "  write(*,'(i0)') k\n")
  file(APPEND ${filename} "end program\n")
  try_run(BIG_INT_COMPILES BIG_INT_RUNS
${CMAKE_BINARY_DIR} ${filename}
RUN_OUTPUT_VARIABLE FBIGINT)
  message(STATUS "Fortran big integer kind: ${FBIGINT}")
endmacro()


Izaak Beekman
===
(301)244-9367
Princeton University Doctoral Candidate
Mechanical and Aerospace Engineering
ibeek...@princeton.edu

UMD-CP Visiting Graduate Student
Aerospace Engineering
ibeek...@umiacs.umd.edu
ibeek...@umd.edu
--

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

[CMake] problems when upgrading to Xcode v5

[Jeff Schenck]

Hello,

I recently upgraded to Xcode v5 on Mac OSX and started getting build failures.  
Below is a simplified project that produces the same problem, followed by the 
error message generated by Xcode.  The problem occurs with version v5 but not 
v4.6.x of Xcode.  I'm running CMake 2.8.10.2.


CMakeLists.txt

cmake_minimum_required ( VERSION 2.8.8 )

project( test )

add_library( a_obj OBJECT t1.c t2.c )
add_library( b_obj OBJECT t3.c t4.c )

add_library( a dummy.c $ )
add_library( b dummy.c $ )

add_executable( t t.c )
target_link_libraries( t a b )


::
t.c
::
#include 

int func1( int a );
int func2( int a );
int func3( int a );
int func4( int a );

int main()
{
int a = 100;
printf( "%d %d %d %d %d\n", a, func1(a), func2(a), func3(a), func4(a) );
return 0;
}


::
t1.c
::
int func1( int a )
{
return a*1;
}


::
t2.c
::
int func2( int a )
{
return a*2;
}


::
t3.c
::
int func3( int a )
{
return a*3;
}


::
t4.c
::
int func4( int a )
{
return a*4;
}


dummy.c is empty


When I run CMake, no errors; running xcodebuild gives:

/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool:
 can't open file: 
/Users/jschenck/TestBuild/test.build/Release/a_obj.build/Objects-normal/undefined_arch/t1.o
 (No such file or directory)
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool:
 can't open file: 
/Users/jschenck/TestBuild/test.build/Release/a_obj.build/Objects-normal/undefined_arch/t2.o
 (No such file or directory)
Command 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool
 failed with exit code 1


The .o files can instead be found here:

$ find . -name t1.o
./test.build/Release/a_obj.build/Objects-normal/x86_64/t1.o


Thanks for your help.  (Sorry for not running this on the latest version of 
CMake, but I rolled back Xcode to an earlier version and now will have a hard 
time reproducing it.  If necessary, I can "upgrade" again.)

Regards,
Jeff Schenck




Notice:
This message and any included attachments are intended only for the use of the 
addressee, and may contain information that is privileged or confidential. If 
you are not the intended recipient, you are hereby notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited. If you have received this communication in error, please destroy 
the original message and any copies or printouts hereof.

--

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

Re: [CMake] [cmake-developers] CMake 2.8.12-rc4 ready for testing!

[Rolf Eike Beer]

Am Mittwoch, 2. Oktober 2013, 15:31:49 schrieb Nicolas Desprès:
> Hi,
> 
> I have just download, compile and run the test suite on my Linux machine
> and I have two failing tests:
> 
> The following tests FAILED:
>  25 - FindPackageTest (Failed)
>  291 - CTestTestMemcheckDummyValgrindInvalidSupFile (Failed)
> 
> This is probably due to my setup. I have attached the log to this post.

It looks like you have done "ln -s /home/despres/local /local" and that 
confuses at least the memcheck test as it expects the "correct" absolute path 
to show up in the error message.

Eike

signature.asc
Description: This is a digitally signed message part.
--

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

[CMake] try_run() fortran support

[Izaak Beekman]

rement
> > - CMake: File command now supports the GENERATE command to produce files
> at
> >  generate time
> > - CMake: target_include_directories now supports the SYSTEM parameter
> > - CMake: Add support for Java in cross compilation toolchains
> > - CMake: Improved support for the IAR toolchain
> > - CMake: Improved support for the ARM toolchain under Visual Studio
> > - CMake: Improvements to the Visual Studio Generators Including
> >   - Separate compiler and linker PDB files
> >   - Support for subdirectory MSBuild projects
> >   - Support for assembly code to VS10
> >   - Support for Windows CE to VS11
> > - CMake: Added COMPILE_OPTIONS target property.
> > - CMake: Added INTERFACE_LINK_LIBRARIES added as a property to targets
> > - CMake: Now supports .zip files with the tar command
> > - CMake: try_compile now supports multiple source files
> > - CMake: Optimized custom command dependency lookup
> > - CMake: Removal of configured files will retrigger CMake when issuing a
> >  build command
> > - CMake: Ninja now tracks custom command generated files that aren't
> listed
> >  as output
> > - CMake: Added generator expression support for compiler versions
> > - CMake-Gui: Add search functions for Output window
> > - CTest: Improved memory checker support
> > - FindGTK2: General Improvements
> > - FindCUDA: Multiple improvements to the custom commands
> >
> >
> > The bug tracker change log page for this version is at:
> > http://public.kitware.com/Bug/changelog_page.php?version_id=112
> >
> > The complete list of changes in RC4 since RC3 can be found at:
> > http://www.cmake.org/Wiki/CMake/ChangeLog
> >
> > As this is expected to be the last RC release please test it and report
> any
> > regressions to the list or the bug tracker.
> >
> > Thanks
> > --
> >
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the CMake FAQ at:
> > http://www.cmake.org/Wiki/CMake_FAQ
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
> >
>
>
>
> --
> Nicolas Despr?s
> -- next part --
> An HTML attachment was scrubbed...
> URL: <
> http://www.cmake.org/pipermail/cmake/attachments/20131002/4f235e80/attachment-0001.htm
> >
> -- next part --
> A non-text attachment was scrubbed...
> Name: test.log
> Type: application/octet-stream
> Size: 4705 bytes
> Desc: not available
> URL: <
> http://www.cmake.org/pipermail/cmake/attachments/20131002/4f235e80/attachment-0001.obj
> >
>
> --
>
> ___
> CMake mailing list
> CMake@cmake.org
> http://www.cmake.org/mailman/listinfo/cmake
>
> End of CMake Digest, Vol 114, Issue 4
> *
>
--

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

Re: [CMake] [cmake-developers] CMake 2.8.12-rc4 ready for testing!

[Nicolas Desprès]

Hi,

I have just download, compile and run the test suite on my Linux machine
and I have two failing tests:

The following tests FAILED:
 25 - FindPackageTest (Failed)
 291 - CTestTestMemcheckDummyValgrindInvalidSupFile (Failed)

This is probably due to my setup. I have attached the log to this post.

Cheers,
-Nico





On Tue, Oct 1, 2013 at 10:49 PM, Robert Maynard
wrote:

> The CMake 2.8.12 release candidate stream continues!
> Thanks to numerous CMake users we uncovered a couple of critical
> regressions
> in RC3. We expect that RC4 will be the final RC unless a new critical,
> regression is discovered. You can find the source and binaries here:
>   http://www.cmake.org/files/v2.8/?C=M;O=D
>
> Some of the notable changes in this release are:
>
> - Introduced target_compile_options command
>   - Specify compile options to use when compiling a given target. Supports
> PUBLIC, PRIVATE, and INTERFACE options. PRIVATE and PUBLIC items will
> populate the COMPILE_OPTIONS property of the target. PUBLIC and
> INTERFACE items will populate the INTERFACE_COMPILE_OPTIONS property
> of the target. Supports generator expressions.
> - Introduced add_compile_options command
>   - Adds options to the compiler command line for sources in the
> current directory and below. Supports generator expressions.
> - Introduced CMake Policy CMP0021:
> - It is now an error to add relative paths to the INCLUDE_DIRECTORIES
>   target property.
> - Introduced CMake Policy CMP0022:
>   - Target properties matching
> (IMPORTED_)LINK_INTERFACE_LIBRARIES(_)
> are ignored, and will no longer be populated by the
> target_link_libraries
> command. It is now an error to populate the properties directly in user
> code. Instead use the INTERFACE keyword with target_link_libraries, or
> the target property INTERFACE_LINK_LIBRARIES.
> - Introduced CMake Policy CMP0023:
>   - Plain and keyword target_link_libraries signatures cannot be mixed for
> a
> given target when this policy is enabled. Once PUBLIC,PRIVATE, or
> INTERFACE keywords are used, all subsequent target_link_libraries calls
> to the target must use one of these keywords.
> - Introduced: Support for RPATH under OSX
>   - Please see the blog post by Clinton Stimpson about using RPATH on OSX
> (http://www.kitware.com/blog/home/post/510)
>
> - CMake: New PUBLIC PRIVATE and INTERFACE options for target_link_libraries
> - CMake: New ALIAS targets feature
> - CMake: Automatically process Headers directory of Apple Frameworks as
>  a usage requirement
> - CMake: File command now supports the GENERATE command to produce files at
>  generate time
> - CMake: target_include_directories now supports the SYSTEM parameter
> - CMake: Add support for Java in cross compilation toolchains
> - CMake: Improved support for the IAR toolchain
> - CMake: Improved support for the ARM toolchain under Visual Studio
> - CMake: Improvements to the Visual Studio Generators Including
>   - Separate compiler and linker PDB files
>   - Support for subdirectory MSBuild projects
>   - Support for assembly code to VS10
>   - Support for Windows CE to VS11
> - CMake: Added COMPILE_OPTIONS target property.
> - CMake: Added INTERFACE_LINK_LIBRARIES added as a property to targets
> - CMake: Now supports .zip files with the tar command
> - CMake: try_compile now supports multiple source files
> - CMake: Optimized custom command dependency lookup
> - CMake: Removal of configured files will retrigger CMake when issuing a
>  build command
> - CMake: Ninja now tracks custom command generated files that aren't listed
>  as output
> - CMake: Added generator expression support for compiler versions
> - CMake-Gui: Add search functions for Output window
> - CTest: Improved memory checker support
> - FindGTK2: General Improvements
> - FindCUDA: Multiple improvements to the custom commands
>
>
> The bug tracker change log page for this version is at:
> http://public.kitware.com/Bug/changelog_page.php?version_id=112
>
> The complete list of changes in RC4 since RC3 can be found at:
> http://www.cmake.org/Wiki/CMake/ChangeLog
>
> As this is expected to be the last RC release please test it and report any
> regressions to the list or the bug tracker.
>
> Thanks
> --
>
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
>



-- 
Nicolas Desprès


test.log
Description: Binary data
--

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/cmak

[CMake] Is there a way to specify NEWLINE_STYLE in an install command?

[Peter Kjær Willendrup]

Hi all,


I develop a simulation code (http://www.mcstas.org) that runs on multiple 
platforms, including both various Unixes and Windows.

We have recently moved our build environment from being based on autoconf, make 
and home-grown scripts to cmake + cpack.

A portion of our shipped datafiles should be installed with platform-dependent 
linefeeds, but as builds for Windows happen via mingw on a Linux box, I would 
like to have cmake do this at either configure or install time.

I have found that this is possible for individual files via

configure_file( 
 [COPYONLY] [ESCAPE_QUOTES] [@ONLY]
 [NEWLINE_STYLE [UNIX|DOS|WIN32|LF|CRLF] ])

but have failed to find something similar for the install () command which we 
use for installing directories with datafiles.

Is the only way really to loop all the datafiles individually and 
configure_file them?


Best,

Peter


Peter Kjær Willendrup
Senior Research Engineer, Special Advisor

DTU Physics



Technical University of Denmark



[cid:image002.gif@01CCCAF1.5E6331F0][cid:EC2A3CAB-AF57-4CEB-96B0-23F6DC35FE76@fysik.dtu.dk]

Department of Physics
Neutrons and X-rays for Materials Physics
Fysikvej

Building 307

DK-2800 Kongens Lyngby

Direct +45 2125 4612

Mobil +45 2125 4612
Fax +45 4593 2399


p...@fysik.dtu.dk

<><><>--

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