Hi everyone,
We're trying to enhance the export functionality of TriBits [1] and are
looking for some good pieces of documentation of what export config files
should ideally look like.
Any pointers?
Cheers,
Nico
[1] github.com/TriBITSPub/TriBITS
--
Powered by www.kitware.com
Please keep
On 04/14/2015 12:25 PM, Bartlett, Roscoe A. wrote:
Is there a way to make CMake flush STDOUT
Not from the CMake language. However, it shouldn't matter.
This is a problem since I have tests that grep output generated
[snip]
to point to the inc-- Configuring incomplete, errors occurred!
We are pleased to announce that CMake 3.2.2 is now available for download.
Please use the latest release from our download page:
http://www.cmake.org/download/
Thanks for your support!
-
Changes in 3.2.2 since 3.2.1:
Hello CMake people,
Is there a way to make CMake flush STDOUT (written two with MESSAGE() command)
so that we don't get jumbled output?
This is a problem since I have tests that grep output generated by CMake and it
cases tests to fail like shown at:
- Original Message -
I am trying to create a standalone build of our application on Linux. We are
currently building on a mix of Mint 17 and Ubuntu 14.04. I have been doing a
lot of reading about rpath, runpath and chrpath. The only way it would seem
to get this done is to adjust the
I am trying to create a standalone build of our application on Linux. We
are currently building on a mix of Mint 17 and Ubuntu 14.04. I have been
doing a lot of reading about rpath, runpath and chrpath. The only way it
would seem to get this done is to adjust the rpath via the chrpath tool.
The
On 04/14/2015 02:03 PM, Nico Schlömer wrote:
Hi everyone,
We're trying to enhance the export functionality of TriBits [1] and are
looking for some good pieces of documentation of what export config
files should ideally look like.
Any pointers?
For target exports created by cmake itself there
Xcode keeps the objects ordered by the object id.
Because cmake stores them into an unordered container
at creation time they must be sorted before writing the
pbxproj file.
out of curiosity: what exactly is the id? the uuid identifier or the
target name? when ordering targets in the project,
On 04/13/2015 03:37 PM, Gregor Jasny wrote:
this patch series aims to minimize deltas between the CMake Xcode
generator and Xcode itself. It was started by the observation that
if one makes any change to the project within Xcode (e.g. to see
how a variable is called internally) the user cannot
On 04/14/2015 04:15 AM, Tim Blechmann wrote:
out of curiosity: what exactly is the id? the uuid identifier or the
target name? when ordering targets in the project, it would make sense
to order them by target name, as that's what users are used to (iirc the
cmake-generated msvc projects are
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 annotated tag, v3.2.2 has been created
at 0f45dba42da3b06db86d73e5e5ecf7030ade3f8b (tag)
tagging
On 04/14/2015 12:07 PM, Geoffrey Viola wrote:
It was easy to add some pre and post build commands
Thanks, but something needs to verify that these actually
get executed. They could do other operations like use
${CMAKE_COMMAND} -E copy to put files somewhere that
can be checked.
There
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 8f354a97a5e7745870b8e3b540999d47b994f239 (commit)
via
Currently the Tests/GhsMulti project in the test suite is very minimal.
Please look at expanding it to cover more of the generator implementation.
It needs add_custom_target and add_custom_command, for example. They could
just run a simple ${CMAKE_COMMAND} -P mycode.cmake script to
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 53d490d597a79d61de14db75b10b589c72eaef11 (commit)
via
On 04/14/2015 10:17 AM, Tim Blechmann wrote:
Effectively it is a UUID for our purposes. The ordering Gregor
proposes is to match what Xcode writes when it generates the .pbxproj
file, and we can't choose that.
i see ... is it (easily) possible to lexicographically sort he
user-visible
Effectively it is a UUID for our purposes. The ordering Gregor
proposes is to match what Xcode writes when it generates the .pbxproj
file, and we can't choose that.
i see ... is it (easily) possible to lexicographically sort he
user-visible appearance? this is something that can be changed
On 04/14/2015 10:36 AM, Tim Blechmann wrote:
Where is the order stored?
seems to be the children property:
22AA72931ADD5C9900988B41 = {
isa = PBXGroup;
children = (
-22AA729E1ADD5C9900988B41 /* test */,
20150414)
+set(CMake_VERSION_PATCH 20150415)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
out of curiosity: what exactly is the id? the uuid identifier or the
target name? when ordering targets in the project, it would make sense
to order them by target name, as that's what users are used to (iirc the
cmake-generated msvc projects are order their targets by target name)
We don't
20 matches
Mail list logo
