Hey David,
What is the intended behavior when upgrading CMake on a OSX Machine?
It seems that currently, generated projects will keep a reference to
the resolved symlink, ie
/Applications/CMake\ VERSION/Contents/bin/..., causing confusing errors such as
Hey everyone,
This will be a really, really vague question.
I'm using ctest scripts to run automated dashboards on all my
platforms. My git repository contains quite a few submodules, which I
believe is related.
At some point, ranging from almost instantly to after a few days,
files starts
Hi everyone,
Unfortunately our buildsystem is not yet entirely clean, and produces
a few files in the source directory. I would like to be able to run
git clean before building, anyone have any ideas how to do this?
(Without losing cdash update history)
To be more precise, the commands I would
On Tue, Feb 1, 2011 at 1:37 AM, Dongsheng Song dongsheng.s...@gmail.com wrote:
On 2011-2-1 5:45, David Cole wrote:
The CMake 2.8.4 release candidate stream continues! You can find the
source and binaries here: http://www.cmake.org/files/v2.8/?C=M;O=D
Since we switched to git, and a new
On Tue, Feb 1, 2011 at 1:30 AM, Dongsheng Song dongsheng.s...@gmail.com wrote:
On 2011-2-1 5:45, David Cole wrote:
The CMake 2.8.4 release candidate stream continues! You can find the
source and binaries here: http://www.cmake.org/files/v2.8/?C=M;O=D
Since we switched to git, and a new
On Tue, Feb 1, 2011 at 20:04, David Cole david.c...@kitware.com wrote:
On Tue, Feb 1, 2011 at 1:30 AM, Dongsheng Song dongsheng.s...@gmail.com
wrote:
On 2011-2-1 5:45, David Cole wrote:
The CMake 2.8.4 release candidate stream continues! You can find the
source and binaries here:
On Tue, Feb 1, 2011 at 3:56 AM, Johan Björk p...@spotify.com wrote:
Hey David,
What is the intended behavior when upgrading CMake on a OSX Machine?
It seems that currently, generated projects will keep a reference to
the resolved symlink, ie
/Applications/CMake\ VERSION/Contents/bin/...,
On Tue, Feb 1, 2011 at 7:08 AM, Dongsheng Song dongsheng.s...@gmail.com wrote:
On Tue, Feb 1, 2011 at 20:04, David Cole david.c...@kitware.com wrote:
On Tue, Feb 1, 2011 at 1:30 AM, Dongsheng Song dongsheng.s...@gmail.com
wrote:
On 2011-2-1 5:45, David Cole wrote:
The CMake 2.8.4 release
Hi everyone,
Is it possible to get (or calculate) the CDash url for a certain
submission in a ctest script?
/Johan
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please
Would someone be able to verify this for me?
Thanks,
Brian Panneton
On Thu, Jan 27, 2011 at 11:58 AM, Brian Panneton
brian.panne...@gmail.comwrote:
I have found an issue with UseSWIG.cmake during parallel builds. If you are
swigging Python and Java using the SWIG_ADD_MODULE and
On Tue, 1 Feb 2011 09:56:03 +0100, Johan Björk said:
What is the intended behavior when upgrading CMake on a OSX Machine?
It seems that currently, generated projects will keep a reference to
the resolved symlink, ie
/Applications/CMake\ VERSION/Contents/bin/..., causing confusing errors
such as
I have an application Foo which distributes a plugin for a separate
application Bar. My plugin is dependent on libraries distributed with
application Foo. When application Bar tries to load the plugin, the plugin
will not load, as it cannot find the libraries distributed with Foo.
As far as
On 2/1/2011 1:30 AM, Dongsheng Song wrote:
On 2011-2-1 5:45, David Cole wrote:
The CMake 2.8.4 release candidate stream continues! You can find the
source and binaries here: http://www.cmake.org/files/v2.8/?C=M;O=D
Since we switched to git, and a new workflow, we're expecting to do
more
On 2/1/2011 11:34 AM, Sean McBride wrote:
On Tue, 1 Feb 2011 09:56:03 +0100, Johan Björk said:
What is the intended behavior when upgrading CMake on a OSX Machine?
It seems that currently, generated projects will keep a reference to
the resolved symlink, ie
/Applications/CMake\
On 2/1/2011 11:55 AM, Bill Hoffman wrote:
$ export PATH=~/tmp/cmake-2.8.4-rc2-Linux-i686/bin:$PATH
$ cmake -G Unix Makefiles -DCMAKE_BUILD_TYPE=Release
-DCMAKE_SYSTEM_NAME=Windows -DCMAKE_C_COMPILER=i686-w64-mingw32-gcc
-DCMAKE_RC_COMPILER=i686-w64-mingw32-windres
-- Configuring done
You have
On Tue, 1 Feb 2011 08:39:08 -0800, Scott Fowler said:
I have an application Foo which distributes a plugin for a separate
application Bar. My plugin is dependent on libraries distributed with
application Foo. When application Bar tries to load the plugin, the
plugin will not load, as it cannot
Basically you need to implement the following cmake function:
function(gp_item_default_embedded_path_override item default_embedded_path_var)
You can set to use @executable_path or @loader_path or what ever you really
want in there.
which BundleUtilities will use if it finds it. The trick here
How well does @loader_path work with line 372 in BundleUtilities.cmake? It
doesn't seem to make any allowances for @loader_path or @rpath.
string(REPLACE @executable_path ${exepath} resolved_embedded_item
${embedded_item})
get_filename_component(resolved_embedded_item
We only have exepath defined with which to make a replacement.
BundleUtilities is strongly biased toward having everything be
relative to the main bundle executable (or a similarly-pathed
executable) because of that very line of code. We are using
@executable_path occurrences to actually resolve
fixup_bundle is doing everything we need it to on Mac, except that the
install_names are wrong. It seems that we might be able to just execute a
script at install time to change @executable_path to @loader_path. This gets
us 90% of the way.
otool -L QtGui.framework/Version/4/QtGui
Old:
It sounds to me (since you're not able to use @executable_path) that
stuff from your bundle is depending on being loaded into executables
from more than one path. In which case, you are asking for subtle and
hard-to-diagnose issues down the road (in my opinion)...
I could be wrong ...
What
Hi everybody,
I´m mailing to find out what the community thinks of my feature request
(http://public.kitware.com/Bug/view.php?id=5974), which was unfortunately
rejected, and maybe come up with a better idea that serves the same goal.
However, first I want to say that I appreciate the effort
On Tue, Feb 1, 2011 at 5:36 PM, Maarten Nieber hallomaar...@yahoo.com wrote:
Hi John,
thanks, but that only works one level deep, right? If you have a structure A
- B - C, then C will always inherit all of A, regardless of where in B's
CMakeList you put the ADD_SUBDIRECTORY.
No it depends
2011/2/1 Maarten Nieber hallomaar...@yahoo.com:
Hi everybody,
I´m mailing to find out what the community thinks of my feature request
(http://public.kitware.com/Bug/view.php?id=5974), which was unfortunately
rejected, and maybe come up with a better idea that serves the same goal.
However,
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 4f1e1fe7821da7d5af17d18f031f72daa05c89e1 (commit)
from
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 ae66ec29b69ddbf31ff8dbadca2f3377186a2e69 (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 19aa60d1da62dd95021d975aa406403f3c5b3d9c (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 54e13fcace9c005ef5e96b6c60f3bdac60a5aa3c (commit)
via
28 matches
Mail list logo
