The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=11767
==
Reported By:Florian Rathgeber
Assigned To:
Hi all
I am trying to build and link against a dependency out of the source tree.
I tried to arrange a custom target/command combo but it did not work.
Could someone help me with this?
What I really need is how to let cmake and make be correclty launched for such
an out of tree dependency before
E.g. cmake --help-fullfilename.docbook
gives you a docbook file, which can then be processed further.
The interesting thing is how to get the links into these files initially.
Do you need any intermediate format(s) for the desired data exchange?
Regards,
Markus
2011/1/26 Michal Turlik michal_...@yahoo.com
Hi all
I am trying to build and link against a dependency out of the source tree.
I tried to arrange a custom target/command combo but it did not work.
Could someone help me with this?
What I really need is how to let cmake and make be correclty
Hi,
executing the command 'cmake -E tar xfz archive.tgz' can be really
noisy. It works fine in Linux and also in Windows if I use the Qt GUI to
CMake. In a Windows Terminal it reports CMake Error: Problem with
archive_write_finish_entry(): Can't update time for %s for every single
file in the
From the libarchive source code, it looks like this message appears as
a warning and returns ARCHIVE_WARN.
CMake spits out an error message whenever a libarchive function
returns anything other than ARCHIVE_OK.
Perhaps we should detect ARCHIVE_WARN and only emit a CMake Warning
message rather
On 01/21/2011 02:59 PM, Vincent Garcia wrote:
Dear CMake users,
I have this BIG project which has tons of subdirectories (many levels).
In each (final) subdirectory, I create targets (executables and libraires).
So I have my top level CMakeLists.txt and one CMakeLists.txt file (which is
Hello everyone,
Currently I'm using cmake for building my c++/Qt project.
The source directory structure looks like this:
Project
|_ src
|_ include
|_ data
Currently I run cmake from the source directory, having an in-source-build.
Now I want to be able to have a complete seperate build folder.
Send some code for us to look at.
If the cwd is where your exe is, and there's a file at ./data/file1
then you should certainly be able to open and read that file with that
file name.
Maybe your cwd is not what you think it is.
Maybe your code changes it somewhere between launching and
ok, sorry, let's make it more real. I cannot disclose much code, but
it's like this:
I have a normal Qt application started out of a main.cpp which is
located in $SOURCE_DIR/src
In another QWidget also located in $SOURCE_DIR/src I call a function
which is also declared in $SOURCE_DIR/src
with
I thank you so much Eric,
However I managed this thing and obteined the expected result by writing
something similar and then including it in my root CMakeLists.txt:
- util lib dependency -
# -*- Makefile -*-
IF(BUILD_STANDALONE)
project( util_lib_pro )
# compatibility issues
Look at these two documents:
http://doc.trolltech.com/4.1/qt-conf.html
http://doc.trolltech.com/4.1/qlibraryinfo.html#location
By creating a qt.conf in your build directory next to your application
you can make your code completely agnostic to the location of your data
files.
HTH
Michael
On
On Wednesday 26 January 2011, SF Markus Elfring wrote:
E.g. cmake --help-fullfilename.docbook
gives you a docbook file, which can then be processed further.
The interesting thing is how to get the links into these files initially.
Do you need any intermediate format(s) for the desired data
The CMakeLists.txt below illustrates the problem:
-
cmake_minimum_required(VERSION 2.8)
project(testo)
function(set_a_var var value)
set(${var} ${value})
message(${var} = ${${var}})
endfunction()
set_a_var(testo HELLO!)
You can install target and data and then run your program.
2011/1/26, Benjamin Kurz benjamin.k...@bioskill.com:
Hello everyone,
Currently I'm using cmake for building my c++/Qt project.
The source directory structure looks like this:
Project
|_ src
|_ include
|_ data
Currently I run
I thank you so much Eric,
However I managed this thing and obteined the expected result by writing
something similar and then including it in my root CMakeLists.txt:
- util lib dependency -
# -*- Makefile -*-
IF(BUILD_STANDALONE)
For those project I need that I usually do this
I _think_ there are issues with generating a file that is later used by CMake.
I think. The other issue is that every time you run CMake (by default) that
file is going to be written, then configured by cmake which will most likely
mean a larger recompile than might be necessary.
I don't see
ehi nice!
thanks
--- On Wed, 1/26/11, Rolf Eike Beer e...@sf-mail.de wrote:
From: Rolf Eike Beer e...@sf-mail.de
Subject: Re: [CMake] how to specify dependencies out of the source tree?
To: cmake@cmake.org
Date: Wednesday, January 26, 2011, 7:05 PM
I thank you so much Eric,
However I managed
Hello!
I have a real newbie question here. It's possible this was already
answered, but I tried searching the archives and could not find
anything.
I have an application that links to a few libraries, some of which are
in the system install locations and some of which aren't.
I would like the
Am 26.01.2011 17:44, schrieb Alexander Neundorf:
On Wednesday 26 January 2011, SF Markus Elfring wrote:
E.g. cmake --help-fullfilename.docbook
gives you a docbook file, which can then be processed further.
The interesting thing is how to get the links into these files initially.
Do you need
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 d8f414e9d6add79c71eab1450a9a8610dfc8a071 (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 c0e087fb766cafa2a7d05e04b41239baee9065fe (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 41147fcf485113756566d04505f12a3905c1b7dd (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 5ec9f6f60901c3ed4b8668e8cd34f71b01023631 (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 eae89aa9aa4d7e3bd203d4684a5569923c397bb9 (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 314ddcbf936c136de9b86e6e8b9bb2466d397ff4 (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 7e6a00465989208905432bd41885db6133fa2742 (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 75348fc0fe555fbe8c8d58a3859f09606e3579e3 (commit)
via
28 matches
Mail list logo