On Wednesday 27 April 2011, you wrote:
Am 27.04.2011 21:28, schrieb Alexander Neundorf:
On Monday 25 April 2011, Oliver Buchtala wrote:
Am 20.04.2011 22:09, schrieb Alexander Neundorf:
...
What would you expect there ?
Some structure that gives me acces to the sources of the
Am 06.05.2011 23:26, schrieb Alexander Neundorf:
On Saturday 30 April 2011, Oliver Buchtala wrote:
Am 30.04.2011 19:56, schrieb Oliver Buchtala:
Am 30.04.2011 19:29, schrieb Alexander Neundorf:
Nowadays, there are ways to deal better with that: linked folders,
virtual folders and linked
On Friday 06 May 2011, Oliver Buchtala wrote:
Am 06.05.2011 23:26, schrieb Alexander Neundorf:
...
When I look around my colleagues I find basically only positive remarks
about the svn support in Eclipse ;-)
This is also my impression from feedback from other users about the
Eclipse
Am 07.05.2011 00:02, schrieb Alexander Neundorf:
On Friday 06 May 2011, Oliver Buchtala wrote:
Am 06.05.2011 23:26, schrieb Alexander Neundorf:
...
When I look around my colleagues I find basically only positive remarks
about the svn support in Eclipse ;-)
This is also my impression from
Am Donnerstag, 5. Mai 2011, 22:21:49 schrieb Dan Furtney:
I have a CMakelists.txt file that works properly for the âUnix Makefilesâ
type build (Linux) and for VS 2008. When generating a CDT4 project (Linux)
from the same file, library paths are not resolved and the project wonât
link.
Are there any plans to support gobject-introspection?
Micha
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
David Cole wrote:
On Thu, May 5, 2011 at 7:08 AM, J.S. van Bethlehem
j.s.van.bethle...@astro.rug.nl
mailto:j.s.van.bethle...@astro.rug.nl wrote:
Hello,
Today I was trying something along the following lines:
in CMakeLists.txt
set(BASENAME some_text)
set(${BASENAME}_DIR
On 6 May 2011 01:12, Michael Hertling mhertl...@online.de wrote:
Yes, absolutely. Although setups with libraries which are needed in some
configurations only are quite rare, AFAIK, your case shows that this may
well happen. ;-) Possible - and more appropriate - solutions could be:
- New
Hello everybody,
Let me say from the get-going: this is the worst question I could ask on
this list because I'm pretty sure I don't provide enough information for
a solution and the problem is likely not with CMake, but I can't think
of anything else currently, so I'll give it a go anyway,
Hello,
Using the nomencl package requires running makeindex a bit like this:
makeindex document.nlo -s nomencl.ist -o document.nls
So I have patched the file UseLATEX.cmake version 1.7.4 as below to
accommodate it.
It just a naive copy and paste of the text for glossaries, so I use
Myles English wrote:
On 6 May 2011 11:00, J.S. van Bethlehem j.s.van.bethle...@astro.rug.nl wrote:
Hello everybody,
Let me say from the get-going: this is the worst question I could ask on
this list because I'm pretty sure I don't provide enough information for a
solution and the problem is
Hi guys,
I've installed a newer version of gcc because the version supplied by
Apple is so far out of date, but I don't know how to configure cmake
such that it uses the normal gcc flags instead of the
Apple specific flags. Is there a way to configure cmake to use the
appropriate flags even though
On Fri, 6 May 2011 10:51:57 -0400, Michael Allen said:
I've installed a newer version of gcc because the version supplied by
Apple is so far out of date, but I don't know how to configure cmake
such that it uses the normal gcc flags instead of the
Apple specific flags. Is there a way to configure
I got it from here:
http://hpc.sourceforge.net/
But that's just a pre-compiled version. If you compile gcc4.x yourself
on your mac you'll see that it behaves the same way.
I'm not trying to use any part of the Apple toolchain, so it makes
perfect sense to me.
On Fri, May 6, 2011 at 11:04 AM,
I'm ending this monologue by this message. I hope this will help someone on
day..
Currently, that is with cmake 2.8.4, this is completely not possible. I go
through most of the sources
and found cmTarget::GetFullNameInternal. Here is the relevant part of the
function :
void
Macports works, but be warned that if you use rtti, (exceptions,
dynamic casting), make sure that you only link against C++ libraries
using the same compiler. Macports errantly uses its own system
libraries in its compiler's.
Juan
On Fri, May 6, 2011 at 10:04 AM, Sean McBride
I'm really sorry I answered this question. I personally hate
macports, but it has its own version of cmake that won't work with the apple
compiler:
/opt/local/bin/cmake -DCMAKE_CXX_COMPILER=/opt/local/bin/g++
-DCMAKE_C_COMPILER=/opt/local/bin/gcc ..
make VERBOSE=1
/opt/local/bin/g++
Ok so you're basically saying that I can just tell cmake that I want
to use a different compiler then, I think that would actually work
with my current compiler and cmake...
On Fri, May 6, 2011 at 12:58 PM, j s j.s4...@gmail.com wrote:
I'm really sorry I answered this question. I personally
Kitware is pleased to offer a free lunch seminar entitled Agile Programming
Practices for High Quality Software Development on Tuesday, May 17th from
12:00pm to 1:00pm. This seminar will be held in the Comfort Suites at 7
Northside Drive Clifton Park, NY 12065.
This hour-long lunch and learn
LinkedIn
Mike Maul requested to add you as a connection on LinkedIn:
--
Robert,
I'd like to add you to my professional network on LinkedIn.
- Mike
Accept invitation from Mike Maul
I'm new to CMake and struggling to understand OSX building.
I have a source code that used to install as an OSX .app just fine with make
and its Makefile.osx. The maintainer has now switched to CMake but does not
know how to write the CMakeLists.txt to achieve the same goal that
Makefile.osx
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 07dd1ba82769c1437b970624a80afca1f6516929 (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 d3e09bba6a6203635ce04b2b7f52506336eedd5d (commit)
from
23 matches
Mail list logo
