Thanks for the detailed information.
My hackweek starts on Monday and I'll start working on these issues then.
I'll work on finding a way to unify toolchain files for simulator and
devices first. I don't think I'll try to work on iOS8 features since my
company is shipping for iOS6 and there are so
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15185
==
Reported By:Richard Ulrich
Assigned To:
On Wed, Sep 24, 2014 at 6:51 PM, Aleix Pol aleix...@kde.org wrote:
On Wed, Sep 24, 2014 at 3:55 PM, Brad King brad.k...@kitware.com wrote:
On 09/22/2014 07:15 PM, Aleix Pol wrote:
{
version: 1.0,
targets: [...]
}
Yes. The version number could either be maintained as its own
thing,
You could manually check for a file by the name of `CMakeLists.txt` to
exist, e.g.,
```
IF (IS_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}/subdir/
AND EXISTS ${CMAKE_CURRENT_SOURCE_DIR}/subdir/CMakeLists.txt)
ADD_SUBDIRECTORY(subdir)
ENDIF()
```
Cheers,
Nico
On Mon, Sep 29, 2014 at 7:24 PM,
Hi ,
Is there any way to know programmatically ( in cmake ) what files will be
installed if a COMPONENT is installed ( something like a get_property of
component)?
Currently I am installing a COMPONENT to a temporary location for packaging
( not using CPack for packaging ) and then packaging
On 01.10.2014 00:26, Nico Schlömer wrote:
into which of the directories listed in [1] are the CMake export files
(*Config.cmake, *Target.cmake,...) supposed to go?
On [2] scroll down to CMake constructs a set of possible installation
prefixes for the package..
Any of the listed (W) or (U)
Alright, thanks!
On Wed, Oct 1, 2014 at 11:13 AM, Nils Gladitz nilsglad...@gmail.com wrote:
On 01.10.2014 00:26, Nico Schlömer wrote:
into which of the directories listed in [1] are the CMake export files
(*Config.cmake, *Target.cmake,...) supposed to go?
On [2] scroll down to CMake
Hi all
I am using Cmake3.0.2, and want to generate project for Visual Studio 2010,
and I have ifort 12 installed on my computer. After generated the project, when
I build them, I got error:
Error 1 fatal error LNK1181: cannot open input file
What about checking install_manifest.txt after running the cmake command?
Or, if you have multiple components to package in this way, possibly you could
use a different CMAKE_INSTALL_PREFIX for each component. Then, either have the
installer generator use those directories for packing the
The commands for PRE_LINK/POST_BUILD is not correctly quoted for Ninja in
Windows. 'CMD /C command' is added to the command, just as Ninja itself
does.
(this was maybe different in earlier Ninja versions, but has been around for a
couple of years)
(The quoting in the working command is strange,
20141001)
+set(CMake_VERSION_PATCH 20141002)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
11 matches
Mail list logo
