On 07/01/2014 02:48 PM, Florent Castelli wrote:
When cross compiling, toolchains won't have install_name_tool,
which is provided by Xcode and command line tools on OSX.
This is a Mach-O specific utility and not required on all platforms.
Applied, thanks:
OS X: Only search for
Am 02.07.2014 15:19, schrieb Brad King:
On 07/01/2014 02:48 PM, Florent Castelli wrote:
When cross compiling, toolchains won't have install_name_tool,
which is provided by Xcode and command line tools on OSX.
This is a Mach-O specific utility and not required on all platforms.
Applied,
On 07/02/2014 08:13 AM, Ben Boeckel wrote:
Colors should only be output if we're outputting to a TTY. Pipes or
redirections should not be colored (they'll only confuse those who don't
recognize the escape sequences). CMake also has color routines already,
but I don't know off-hand how
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15002
==
Reported By:Olivier Trichet
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15003
==
Reported By:Ryan Curtin
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15004
==
Reported By:Chris Foster
Assigned To:
May be you can avoid localized output by setting LANG env var to C.
Or you can ask svn for xml output which may not be localized e.g.
# Get the SVN revision number of an svn command line client is
# available. This version will run at build time rather than only
# at configuration generation
Hi,
The command
SET(ENV{LC_ALL} C)
somewhere inside your cmake macro will do the trick. If you really care
about the original contents of LC_ALL you should save it first and
restore once your done.
BTW: you might consider using the Subversion_WC_INFO() macro in the
FindSubversion module.
Am 02.07.2014 01:04, schrieb Rick McGuire:
We like to include the SVN revision number in our build artifacts to
help
keep track of what version people are working with. I found the
following
code on the mailing lists which appears to work fine:
# Get the SVN revision number of an svn command
I'm generating a drag and drop installer. I'm trying to add a custom
background image and a custom
DS_Store file unsuccesfuly.
set (CPACK_DMG_FORMAT UDBZ)
set (CPACK_DMG_BACKGROUND_IMAGE
${PROJECT_SOURCE_DIR}/macInstallerFiles/background.png)
set (CPACK_CPACK_DMG_DS_STORE
On 02.07.2014 13:18, Guillermo Sotomayor wrote:
I'm generating a drag and drop installer. I'm trying to add a custom
background image and a custom
DS_Store file unsuccesfuly.
set (CPACK_DMG_FORMAT UDBZ)
set (CPACK_DMG_BACKGROUND_IMAGE
${PROJECT_SOURCE_DIR}/macInstallerFiles/background.png)
Currently we have 16 different platform that we target that are a combination
of native compiles and cross compiles. I am adding a new platform to our build
system using CMake's cross compiling facility. This platform is unique in that
compiling a .c file to get an .o file required two steps.
On 02.07.2014 18:53, Eric LaFranchi wrote:
Currently we have 16 different platform that we target that are a
combination of native compiles and cross compiles. I am adding a new
platform to our build system using CMake's cross compiling facility.
This platform is unique in that compiling a
Yes. The cross compiler is run on Windows and we are setup to use either
Windows Command Prompt or Cygwin shell.
What arguments will be passed into the script that is set using the
CMAKE_FORCE_C_COMPIELR macro? I assume this is going to be compiler flags,
source file, and target file?
The
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via fa6c373f9e172e6592a2f3b7ecc28ea7c1e06042 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via ba12dd176aecaedc288a9eefecb0d1adfce4b55e (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 3811d18a7e1e1a7a70ce5ec35bea55e9f3c5f00d (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 2ea0d6ba278e67f1fd6f2f78f2df9951a46eb4a4 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via e2a12b8a58e0b96ef974463d4412fa804e3af297 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 38c9eddad87511ddcb252e0363bdf14ef9b3b866 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 477b07213a806c825f95fdfacd444028e1783dc2 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 33bdcdea809e5f59f943686f4440b9125d721b00 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 2eed2fd2bb42a9ac5c6f271b1e6d4abe47166b9c (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 164bd68a030dcaa658ad7828b7f7b7762cbace74 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 94fbf33ad1fb8e304fb8ba1847b1a74e09e05f13 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via f3ebed934d8996b719e61555f375f07c96d889db (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via db98e04debb3b13fbacc3359edfb0b8047079513 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 93704c1fe754edf720125be6992e404438ee8014 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 402be9c58e49356d556b41dd01c8e66266d2b6fc (commit)
via
20140702)
+set(CMake_VERSION_PATCH 20140703)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
30 matches
Mail list logo
