I have recently tried porting a project to CMake but I am facing a few issues
when cross-compiling
The project can be compiled with a varying set of compilers (already works with
our custom makefiles) and currently the only option seems to be passing this
information along with the cmake comman
Alan W. Irwin wrote:
On 2007-02-28 22:03+0100 Eric Noulard wrote:
2007/2/28, Alexander Neundorf <[EMAIL PROTECTED]>:
>
> History:
> New Since 2.4.0 New INSTALL macro
> New Since 2.4.4 Added the INSTALL(DIRECTORY ...) support
E.g. for FIND_PACKAGE() the COMPONENT feature was added in 2.4.4.
T
On 2007-02-28 22:03+0100 Eric Noulard wrote:
2007/2/28, Alexander Neundorf <[EMAIL PROTECTED]>:
>
> History:
> New Since 2.4.0 New INSTALL macro
> New Since 2.4.4 Added the INSTALL(DIRECTORY ...) support
E.g. for FIND_PACKAGE() the COMPONENT feature was added in 2.4.4. This
might become a lon
2007/2/28, Alexander Neundorf <[EMAIL PROTECTED]>:
>
> History:
> New Since 2.4.0 New INSTALL macro
> New Since 2.4.4 Added the INSTALL(DIRECTORY ...) support
E.g. for FIND_PACKAGE() the COMPONENT feature was added in 2.4.4. This might
become a long list when done completely for all commands.
Kevin Tucker wrote:
Path names with spaces seems to be a hard problem. There's a bug posted
for this same problem with Microsoft's nmake:
http://www.itk.org/Bug/bug.php?op=show&bugid=3&pos=1 and it's marked
"Won't Fix". No notes as to why that decision was made...
I need to figure a way around
Hi All,
We (TSP developers) have done a CMake macro
which helps in building RPM package.
You'll find the CMake macro file attached.
The usage is simple:
1) put the macro file in your CMAKE_MODULE_PATH
2) Then add something like this to your CMakeLists.txt
INCLUDE(CPack)
INCLUDE(UseRPMTools)
IF(
Von: "Eric Noulard" <[EMAIL PROTECTED]>
> 2007/2/28, Alexander Neundorf <[EMAIL PROTECTED]>:
> > Hi,
> >
> > on http://www.cmake.org/HTML/Documentation.html there is the
> > documentation for the current cmake version.
> > It would be nice if the documentation for the older versions would
> > als
Path names with spaces seems to be a hard problem. There's a bug posted
for this same problem with Microsoft's nmake:
http://www.itk.org/Bug/bug.php?op=show&bugid=3&pos=1 and it's marked
"Won't Fix". No notes as to why that decision was made...
I need to figure a way around this as well...
Kevi
On 2007-02-27 22:09-0800 Alan W. Irwin wrote:
On 2007-02-27 23:13-0500 Bill Hoffman wrote:
I wonder if you could just use the output name, and tack on the ada
extension to it. add_executable(foo ...)
gnatmake foo.ada.
Thanks for that idea. I assume you are referring to the pattern. Now
th
2007/2/28, Alexander Neundorf <[EMAIL PROTECTED]>:
Hi,
on http://www.cmake.org/HTML/Documentation.html there is the documentation for
the current cmake version.
It would be nice if the documentation for the older versions would also be
available on www.cmake.org. This would help when checking
Hi,
on http://www.cmake.org/HTML/Documentation.html there is the documentation for
the current cmake version.
It would be nice if the documentation for the older versions would also be
available on www.cmake.org. This would help when checking in which version some
feature has been introduced. A
Original-Nachricht
Datum: Wed, 28 Feb 2007 18:48:41 +
Von: Filipe Sousa <[EMAIL PROTECTED]>
An: cmake@cmake.org
CC:
Betreff: Re: [CMake] cmake does not run ldconfig => not found errors
> Peter Soetens wrote:
> > Is there a reason why cmake 2.4.6 does not run this program af
Peter Soetens wrote:
Is there a reason why cmake 2.4.6 does not run this program after installing
shared libraries on a Unix system (Ubuntu) ? After a 'make install', I got
the following:
$ ldd /usr/local/lib/liborocos-rtt.so
linux-gate.so.1 => (0xe000)
...
liboroc
Is there a reason why cmake 2.4.6 does not run this program after installing
shared libraries on a Unix system (Ubuntu) ? After a 'make install', I got
the following:
$ ldd /usr/local/lib/liborocos-rtt.so
linux-gate.so.1 => (0xe000)
...
liborocos-rtt-corba.so.1.2.0 =
Hello all,
recently, I have added source control bindings to the Visual Studio
generator of my cvs-copy of cmake. Now I am able to bind my cmake-generated
VS project files to our source control system perforce. Which is quite
convenient, since I do not have to switch from VS to my perforce client
15 matches
Mail list logo
