Hello,
I applied some fixes to what becomes CMake 3.3. could you please test
the release candidate?
On 16/06/15 16:27, Michael Jackson wrote:
Running OS X 10.8.5 with Xcode 5.1.1 and Cmake 3.2.x and 3.3.RC and neither
generate a Xcode project file that can be opened by Xcode. We get valid
On 16/06/15 21:27, Gregor Jasny wrote:
Hello,
I applied some fixes to what becomes CMake 3.3. could you please test
the release candidate?
Sorry, somehow overlooked the statement about RC in your mail.
On 16/06/15 16:27, Michael Jackson wrote:
Running OS X 10.8.5 with Xcode 5.1.1 and
On 10/06/15 04:17, Dave Yost wrote:
Hey, I love colors. But one of my users doesn’t.
You could try the Ninja generator instead of Makefile. It much often
faster, as verbose as necessary, and black'n'white.
Thanks,
Gregor
--
Powered by www.kitware.com
Please keep messages on-topic and check
Hi Eric,
On 14/06/15 14:38, Eric Wing wrote:
I have been successful at setting Xcode properties on specific targets
with CMake via:
set_property (TARGET ${TARGET} PROPERTY
XCODE_ATTRIBUTE_${XCODE_PROPERTY} ${XCODE_VALUE})
But I have been unable to set properties on the global/root
On 17/06/15 16:29, Michael Jackson wrote:
Just to follow up with this issue in case anyone else has issues with Xcode
here is what happened. Thanks to Gregor for taking a look at the generated
project file he was able to identify an issue where there were file paths in
the form of // inside
Hi David,
On 04/05/15 20:12, David Hirvonen wrote:
Thanks for the response. I've moved to a more standard *nix layout for
all platforms, and will rely on a post-build step to create my framework
(for now). If I find a fix, I'll be sure to share it here.
On Wed, Apr 29, 2015 at 5:22 AM, Eric
Hello,
On 17/08/15 01:01, digitalriptide wrote:
When I add SYSTEM to target_include_directories, for example using
target_include_directories( my_target SYSTEM PUBLIC ${MY_LIBRARIES} )
in Clang, CMake prepends -isystem to the relavent -I/my/library/path
type flags. With GCC, however, I see no
Hello,
Today I stumbled across funny behavior of string(REGEX REPLACE:
This one would lead to an empty match:
string(REGEX REPLACE "(.*)" "\\1Proxy.cpp" _out "IConnectionCallback")
This one would match whole "IConnectionCallback"
string(REGEX REPLACE "(.+)" "\\1Proxy.cpp" _out
Hello,
On 17/10/15 18:28, Michael Jackson wrote:
Are there any known issues with Xcode 6.4 and CMake 3.3.x? I ask because in our
project when we generate the Xcode project we end up with 2 or 3 executables
listed in the drop down combo box. We also end up with lots of duplicate
targets in
Hello,
On 09/10/15 17:51, Roman Wüger wrote:
> I’m trying to configure and build a project with the “Xcode” generator and
> the bullseye coverage tool.
>
> Without the bullseye coverage tool it works fine but if I want to use it I
> had to do the following workaround:
>
Hello,
in my build process I need to call a compiler like tool with the same
include directories as a certain target.
I tried the following:
cmake_minimum_required(VERSION 3.2)
project(cmake-genex C)
add_library(dummy dummy.c foo.c)
target_include_directories(dummy PUBLIC foo bar)
set(prop
On 05/09/15 08:22, Alex Turbov wrote:
> Hi,
>
> in my project I have `add_executable()`. after that, in a current binary
> dir I need to render a `*.cmake` script (via `configure_file()`) to be
> running from `add_test()` (as `cmake -P`) which should start just the
> compiled executable via
Hello,
On 03/09/15 23:15, Robert Dailey wrote:
> How recent is this documentation?
> http://www.cmake.org/Wiki/CMake:How_To_Find_Libraries#Writing_find_modules
>
> It seems rather old. What is the modern way of doing this?
The cmake-developer help page has a section about modules:
Hello,
On 10/09/15 16:34, Daniel Wirtz wrote:
> i've now quite often encountered the need to access basic git
> information about the source tree from within cmake.
> i've attached the current FindGit.cmake module shipped with CMake
> enhanced by two functions: getGitRevision and getGitBranch.
>
On 08/12/15 20:21, digitalriptide wrote:
> Thank you Gregor! I have tried the Makefile generator, but on OS X -isystem
> still seems to be missing with GCC. The -isystem flag appears with Clang,
> however. I have installed CMake 3.4.1 and GCC 5.3.0, both through MacPorts.
> I can provide a sample
Hello,
please have a look at some other toolchain file like the BlackBerry one:
> https://github.com/blackberry/OGRE/blob/master/src/CMake/toolchain/blackberry.toolchain.cmake
On 30/12/15 21:38, Kuhl, Brian wrote:
> I'm trying to add support for VxWorks to CMake.
> My current dilemma is that
On 15/11/15 21:13, digitalriptide wrote:
Did this fix make it into 3.4? After upgrading to 3.4, GCC still seems
to lack -isystem flags on OS X. Is there anything extra I need to do?
It should be fixed for the Makefile and Ninja generators but not Xcode.
My proposed fix broke older Xcode
Hello,
I'd like to get your feedback on deprecating or dropping support for
older Xcode versions. During changes on the Xcode generator it gets
harder and harder to test against old and very old Xcode versions like 3
and 4.
Are there still users around for these versions of Xcode?
PS: I'm
Hello,
On 01/02/16 04:52, Craig Scott wrote:
> After a bit of experimenting, it seems that getting ccache working with the
> Xcode generator isn't so straightforward. For Ninja and Unix Makefiles, the
> RULE_LAUNCH_COMPILE global property nicely gives us the behaviour we want,
> but this doesn't
Hello,
I discovered that the Visual Studio 2015 Generator does not work with
v120 toolsets (#15986) and consider that major issue.
As far as I see this is related to the debug information setting from
#15894.
Thanks,
Gregor
--
Powered by www.kitware.com
Please keep messages on-topic and
Hello,
On 26/02/16 00:00, Andrew Hundt wrote:
> I believe check_cxx_compiler_flags is failing due to a long/complicated
> compiler path.
>
> Specifically my compiler is set to:
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
>
> CMake version: 3.4.3
Hi,
On 21/01/16 15:14, Vania Joloboff wrote:
Hi
I want to add two definitions to compile one specific files
in addition to the global definitions.
I have the following problem. If I use
set_source_files_properties(source.cpp
PROPERTIES
COMPILE_DEFINITIONS VAR1=${MY_VAR1} VAR2=${MY_VAR2} )
On 06/04/16 20:32, Matthew Keeler wrote:
>
> I think I ran into a bug but I am wondering if anyone has seen it an worked
> around.
>
> I have a source structure like the following (this is a contrived small
> example to illustrate the problem):
>
> - CMakeLists.txt
> - main.c
> - lib
>
On 25/03/16 22:11, Sebastian Schuberth wrote:
> I also just realized CMAKE_C_ABI_COMPILER is set to FALSE in
> CMakeCCompiler.cmake. Looking at CMakeError.log was a good hint. I
> found:
>
> ---8<---
> Building C object CMakeFiles/cmTC_c0166.dir/CMakeCCompilerABI.c.obj
>
>
Hello,
I fear you're one of the first users of the XCtest feature :)
On 21/03/16 13:42, Vladimír Vondruš wrote:
Hello,
I came across this problem when trying to use XCTest macros (
https://cmake.org/cmake/help/latest/module/FindXCTest.html ) on iOS. When
compiling for OSX, ctest properly
Hello,
On 11/05/16 09:25, Attila Krasznahorkay wrote:
> I'm a bit surprised by this. I had to explicitly tell CMake not to treat
> includes coming from imported targets as system includes. Using this variable:
>
> https://cmake.org/cmake/help/v3.0/variable/CMAKE_NO_SYSTEM_FROM_IMPORTED.html
>
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?
>
>
On 10/05/16 01:52, Siyuan Ren wrote:
> Version 7.3.1 (7D1014)
Could you please share your build and source directory with me?
--
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
On 02/05/16 11:16, Siyuan Ren wrote:
> I have CMake 3.5.2.
>
> I write a simple CMakeLists.txt like the below
>
> ```
> project(mytest)
> add_executable(mytest test.cpp)
> ```
>
> Then generate the Xcode project file with `cmake -G Xcode .`. Open the
> project file in Xcode, and I found the
Hello,
On 22/07/16 23:07, Victor Rykov wrote:
> After adding a .metal file to a target via add_executable the metal file
> does not get pushed to the generated project`s Compile Sources queue and
> subsequently does not compile during project build unless I add the file to
> the queue manually
Hello,
an editor with syntax highlighting and indention support would have
helped here.
On 04/07/16 01:26, Sambeet Panigrahi wrote:
IF(NOT NOT_BUILD_SHARED )
ADD_LIBRARY(orocos-rtt-mqueue-${OROCOS_TARGET}_dynamic SHARED ${CPPS})
Hello,
On 02/02/2017 16:15, Сергей Бойцов wrote:
Hello.
I'm looking for some help cause i have faced a really strange problem
with building frameworks on Mac OS
So i have:
Mac OS X : el captain
Xcode 8.0
CMake 3.3.2 [1],
CMake 3.4.5 [2],
CMake 3.5-3.6 [3]
CMake [1] produced correct
Hello,
On 16/01/2017 15:43, Harry Mallon wrote:
Sorry look like it is not in the release build yet.
correct, please use a recent nightly:
https://cmake.org/files/dev/?C=M;O=D
Maybe you could report back if the attribute works for you.
Thanks,
Gregor
--
Powered by www.kitware.com
Please
On 21/09/2016 10:54, James Turner wrote:
>
>> On 20 Sep 2016, at 16:00, Braden McDaniel wrote:
>>
>> When setting CMAKE_OSX_SYSROOT to the unversioned directory name (using
>> Xcode 8, as it happens) and setting CMAKE_OSX_DEPLOYMENT_TARGET, I get this
>> error:
>>
>>
>>
On 23/09/2016 22:35, Gregor Jasny wrote:
> On 21/09/2016 10:54, James Turner wrote:
>>
>>> On 20 Sep 2016, at 16:00, Braden McDaniel wrote:
>>>
>>> When setting CMAKE_OSX_SYSROOT to the unversioned directory name (using
>>> Xcode 8, as it happens) and setting
Hello,
On 02/11/2016 06:01, Robert Ramey wrote:
> Here is what I'm seeing:
>
> a) it looks like CMake is looking for boost_filesystem rather than
> libboost as I expect. (same for system).
>
> b) even if I tweak findBoost to force the system to look for libboost...
> it still fails
>
> b) If I
Hello,
On 25/11/2016 19:25, Nathan Sizemore wrote:
> I receive the following when building:
>
> [ 40%] Building C object
> Utilities/cmlibarchive/libarchive/CMakeFiles/cmlibarchive.dir/archive_cryptor.c.o
> In file included from
>
016 09:29:14 MEZ, schrieb Gregor Jasny via CMake
> <cmake@cmake.org>:
>> Hello,
>>
>> On 25/11/2016 19:25, Nathan Sizemore wrote:
>>> I receive the following when building:
>>>
>>> [ 40%] Building C object
>>>
>> Utilities/cmlibar
Hello Robert,
On 29/10/2016 22:03, Robert Ramey wrote:
> I've just "upgraded" to version 3.6 of CMake. I'm using Xcode with the
> clang compiler. Now when I'm trying to configure a project I'm getting:
>
> The C compiler identification is unknown
> The CXX compiler identification is unknown
>
Hello,
I wonder if there is a reason why no MSVC15 variable is available for
Visual Studio 2017? I'm using those MSVCxx variables and
CMAKE_GENERATOR_TOOLSET to detect the active toolset:
# Visual Studio 2008
if((MSVC90 AND "${CMAKE_GENERATOR_TOOLSET}" STREQUAL "") OR
Hello,
On 01/12/2016 07:02, wy39666...@163.com wrote:
> I have a trouble in using cmake.I try to find a way to resolve that for a
> long time, but finally get no results. I attempt to create an ios application
> imessage extension by cmake but i can't find a suitable command. So i contact
>
On 03/12/2016 15:07, wy39666...@163.com wrote:
>>> I have a trouble in using cmake.I try to find a way to resolve that for a
>>> long time, but finally get no results. I attempt to create an ios
>>> application imessage extension by cmake but i can't find a suitable
>>> command. So i contact
On 03/12/2016 19:46, Gregor Jasny wrote:
> On 03/12/2016 15:07, wy39666...@163.com wrote:
I have a trouble in using cmake.I try to find a way to resolve that for a
long time, but finally get no results. I attempt to create an ios
application imessage extension by cmake but i can't
Hi Steven,
On 3/29/17 5:24 PM, Steven Velez wrote:
> If I understand correctly the purpose of the ZERO_CHECK target is to update
> the generated project files when necessary.
>
> That's fine, but I have noticed on Xcode (8.2) that when ZERO_CHECK runs
> and updates the project, it causes the
On 3/29/17 10:15 PM, Steven Velez wrote:
> I do have a pretty large project with around 142 targets.
>
> Another characteristic of note, and which I noticed while investigating
> this is that our project suffers from
> https://gitlab.kitware.com/cmake/cmake/issues/14297, and I think it is
>
On 3/20/17 12:09 PM, Sergey Zakharchenko wrote:
> Rolf,
>
> 2017-03-20 14:06 GMT+03:00 Rolf Eike Beer :
>> https://gitlab.kitware.com/cmake/cmake/issues/14335
>
> Since the issue is marked "easy" and it's over 3 years old, I assume
> nobody cares? OK then.
Hello,
On 20/03/2017 12:09, Sergey Zakharchenko wrote:
Rolf,
2017-03-20 14:06 GMT+03:00 Rolf Eike Beer :
https://gitlab.kitware.com/cmake/cmake/issues/14335
Since the issue is marked "easy" and it's over 3 years old, I assume
nobody cares? OK then.
I can try to fix it. I
Hello,
On 3/10/17 12:31 AM, Cedric Doucet wrote:
> Actually, I should not modify CMAKE_CXX_COMPILER_FLAGS.
> It seems that the problem comes from the variable
> CMAKE_SHARED_MODULE_CREATE_CXX_FLAGS which only contains ' -bundle
> -Wl,-headerpad_max_install_names' but not ' -undefined
On 3/12/17 6:45 PM, Gregor Jasny wrote:
> On 3/10/17 12:31 AM, Cedric Doucet wrote:
>> Actually, I should not modify CMAKE_CXX_COMPILER_FLAGS.
>> It seems that the problem comes from the variable
>> CMAKE_SHARED_MODULE_CREATE_CXX_FLAGS which only contains ' -bundle
>>
Hello,
On 6/26/17 8:12 PM, Watson, Andre wrote:
> We're currently migrating a huge internal system over to CMake, and we're
> nearing completion, but have run into an issue with the generated Xcode
> projects. We build this system on Windows, Linux, and Mac (both makefile and
> Xcode). On
On 6/22/17 4:01 PM, Robert Dailey wrote:
> In my toolchain file for Android NDK, I specify the following *.so
> paths manually:
>
> set( ANDROID_PREBUILT_LIBRARIES
>
> ${CMAKE_ANDROID_NDK}/sources/cxx-stl/gnu-libstdc++/4.9/libs/x86/libgnustl_shared.so
>
Hello,
On 6/20/18 3:10 AM, A. Sanchez via CMake wrote:
> Hello. I have been trying to get a good version of CMake for my PS3 cluster
> running linux. But everything I try to compile needs CMake 3.0 or higher? Is
> there any way to update from CMAKE 2.4. Right now I am running Fedora 9,
> since
Hello,
On 10/3/18 6:08 PM, Tom Finegan via CMake wrote:
I'm trying to get rid of some local CMake scripting for building assembly
with nasm and yasm, but I'm running into a problem with the Xcode generator.
For the make and ninja generators, everything is fine-- nasm and yasm are
both working
Hello,
On 17.11.16 17:15, Damian wrote:
We are still in the process of switching our large Make-based build to
CMake. One of the issues we're running into is the time it takes to
reparse and regenerate the CMake project (whether ninja, VS, or make)
after touching any CMake file. To give you
On 17.05.19 02:53, Gelryun wrote:
I write MakefileList.txt like this.
include_directories(${COMMINC_DIR} ${DBINC_DIR} ./)
link_directories(${DBLIB_DIR} ${COMMLIB_DIR})
set(DBUSERID withdb/ufdb)
Hello,
On 20.05.19 16:01, hex wrote:
What means command1 [args1...]]? Or, should this read
*add_custom_target(Name [ALL] [COMMAND command1 [args1...]]**
** [COMMAND command2 [args2...] ...]*
I believe this is due to backward compatibility (pre 2.6) reasons so
that you could still write:
Hello,
On 25.04.19 09:29, Orban, Laszlo wrote:
Please help me an issue I'm facing with CMAKE_HOST_SYSTEM_NAME on
FreeBSD 10.3. It gives back empty string, if I read it before the
'project(...)'.
As far as I understood, CMAKE_SYSTEM_NAME can be used only after the
'project(...)' call, but
On 07/07/15 10:10, Gregor Jasny wrote:
one of my colleagues is unable to generate a VS2013 solution. He gets
the following error:
Please disregard. This was a vc12 vs. VS2012 confusion.
Sorry for the noise.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
Hello,
one of my colleagues is unable to generate a VS2013 solution. He gets
the following error:
F:\CitrixLibs\ExternalLibs\CMake\3.1.3\Tools_Windows\bin\cmake.exe -G
Visual Studio 12 -T v120_xp -A Win32 -DWITH_COPY_PREBUILT_CACHE=ON
-DWITH_COPY_PREBUILT=ON
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
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
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
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 c12be0dce8d045b3759296f5ce0607e80820f27d (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 524481c809df3cb7b962af97ba1c9078dc5884c3 (commit)
via
Hi Brad,
On 21/08/15 15:36, Brad King wrote:
Thanks. I merged to 'next' for testing last night. Please take a look
at the failures:
https://open.cdash.org/testSummary.php?project=1name=RunCMake.XcodeProjectdate=2015-08-21
It's all green now:
Hello,
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
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 45a48d7e23bae2590516118643d592f02f69ff4e (commit)
via
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
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 c06c74f32f5318789bd72ddb41cec9759d6a9339 (commit)
via
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
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
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 8fbc8e473b347d69331cd120aea3dd6c33e98599 (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 8ab1833c2ad99fa882b7aa85ac87ded78c580576 (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 addb1dad4f1f99e054f3fc3e0f94d571ef8842c8 (commit)
via
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
Hello,
On 10/11/15 16:22, Bartosz Kosiorek wrote:
> My name is Bartosz Kosiorek and I'm TomTom developer and Open Source
> enthusiast.
I'm Gregor a part time contributor to CMake. During the last months I
mostly worked on Xcode support.
> Last time in our products, we notice that cmake is not
On 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
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 acd292f497cb88d2212be5fe0752dadb05bc9c2a (commit)
via
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
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 03c0c9cc4098108010dc115bbdde4158fe423a40 (commit)
via
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.
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
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.
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 faf5e0ebdae22a8bac15d4b3fd1239e645d70ffe (commit)
via
Hallo,
On 13/08/15 12:56, Ruslan Baratov wrote:
On 13-Aug-15 08:46, Gregor Jasny wrote:
On 13/08/15 01:44, Ruslan Baratov via cmake-developers wrote:
Sending patches with fix. Now it's possible to install simulator
libraries by:
cmake --build _builds --config Release --target install --
On 25/08/15 19:01, Brad King wrote:
On 08/24/2015 04:43 PM, Gregor Jasny via cmake-developers wrote:
I just pushed a topic branch to add support for Xcode 7 TDB files:
http://www.cmake.org/gitweb?p=stage/cmake.git;a=shortlog;h=refs/heads/apple-tbd-stubs
Thanks. Please merge to 'next' when
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 70c864ae8ffec43956e751a2ab600862b4fdac7d (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 b8179759b8cbeebab8f3655eef0f1c90c84b786f (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 8be433e2fbbab9a4b6634246d1b69c2d5fd27380 (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 a9b52abbd4278e4c566965bcd2ba5b853f9f9ba2 (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 6985b37195c2b0336f3702cba64fb83d52a7d2b1 (commit)
via
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:
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 cfbf38704d2ee4caedf3fff51244855b076a152d (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 5259219860a040eb81f50ea05ee47447d8220b4c (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 849ccc59e315e64b2c2c98d79ba2108810c461ca (commit)
via
Hi Eric Brad,
On 15/07/15 12:16, Eric Wing wrote:
On 7/7/15, Brad King brad.k...@kitware.com wrote:
On 07/02/2015 07:54 PM, Eric Wing wrote:
Thank you Brad. When you are ready, let me know how I can help next.
I have basic support with the Xcode generator done.
Please try out this commit:
Hi,
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
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 4653dc36efc23e6a35449521a7d7a7688b0ab288 (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 34141ce58174d8180359bd95389c25255e8cf2b7 (commit)
via
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':
1 - 100 of 186 matches
Mail list logo