2008/3/28, Bill Hoffman <[EMAIL PROTECTED]>:
> > Yes, that was reported by me as bug
> > http://public.kitware.com/Bug/view.php?id=4993 in May last year.
> >
> > There is actually a simple patch to get absolute paths to work for CPack
> > (see above bug report), but no action has been taken on
Le Thu, 27 Mar 2008 21:40:16 -0400,
Bill Hoffman <[EMAIL PROTECTED]> a écrit :
> Alan W. Irwin wrote:
> > On 2008-03-28 00:51+0100 Alexander Neundorf wrote:
> >
> >> If you use install() with an absolute path DESTDIR is still
> >> honored on "make
> >> install".
> >> But I just tried and while it
Try this after file command:
string(REPLACE ";" " " plugin_STR "${plugin_STR}")
That said, depending on what you need to do, this may be the wrong type of list.
Andy
On Thu, Mar 27, 2008 at 5:08 PM, Leopold Palomo Avellaneda
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> using this line:
> file(GLOB pl
Hi!
On Thu, Mar 27, 2008 at 02:26:02PM -0400, Bill Hoffman wrote:
> I am happy to announce that CMake 2.6.0 has entered the beta stage! You
> can find the source and binaries here: http://www.cmake.org/files/v2.6/.
I must be doing something terribly wrong here, but files in
http://www.cmake.org/
Bill.
On Thursday 27 March 2008 13:11:12 Bill Hoffman wrote:
> If you use the project command in each sub project cmake 2.6 will do the
> right thing and create sub-solutions that include all targets that they
> use in the larger project.
That's great news! I am looking forward to 2.6.
Thanks,
Alan W. Irwin wrote:
On 2008-03-28 00:51+0100 Alexander Neundorf wrote:
If you use install() with an absolute path DESTDIR is still honored on
"make
install".
But I just tried and while it works with "make install", it doesn't when
creating the packages, not only for deb, but lso for the other
On 2008-03-14 13:04-0700 Alan W. Irwin wrote:
Another concern with the current "make test" is it does not depend on the
default "all" target. That is a bad oversight IMO, since the current
situation is you will be running out-of-date tests after some code fixup
unless you remember to run "make"
On 2008-03-28 00:51+0100 Alexander Neundorf wrote:
If you use install() with an absolute path DESTDIR is still honored on "make
install".
But I just tried and while it works with "make install", it doesn't when
creating the packages, not only for deb, but lso for the other formats.
This may be
Hi,
using this line:
file(GLOB plugin_STR RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} *.c *.cpp *.cxx *.h
*.hpp *.ui)
I obtain a list like this:
datosview.cpp;plugincanualesods.cpp;datosview.h;plugincanualesods.h;datosbase.ui
how an I obtain a list in this way?
datosview.cpp plugincanualesods.cpp d
A Divendres 28 Març 2008, Filipe Sousa va escriure:
> Leopold Palomo Avellaneda wrote:
> > Hi again,
> >
> > please, how can I pass an EXACT string to a ARGS command in a custom
> > command?
>
> VERBATIM
>
> add_custom_command(OUTPUT output1 [output2 ...]
> COMMAND comm
On Thursday 27 March 2008, Eric Noulard wrote:
> 2008/3/27, Jerome Arbez-Gindre <[EMAIL PROTECTED]>:
> > Hi,
>
> Hi there :-)
>
> > I am using the CVS version of CMake and I would like to use CMake only
> > for its Packaging capabilities.
>
> If you "only" want to package things you may
> well only
Leopold Palomo Avellaneda wrote:
Hi again,
please, how can I pass an EXACT string to a ARGS command in a custom command?
VERBATIM
add_custom_command(OUTPUT output1 [output2 ...]
COMMAND command1 [ARGS] [args1...]
[COMMAND command2 [ARGS]
On Thursday 27 March 2008, Jonas Karlsson wrote:
> On 25/03/2008, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> > Hello,
>
> First of all I must say I'm sorry that the message got sent twice.
>
> > I'm trying to build GTK-Qt-Engine 1.1, which use CMake as build system,
> > but it fails almost halfw
Andreas Pakulat wrote:
On 26.03.08 19:10:16, Matthew Woehlke wrote:
Andreas Pakulat wrote:
Hmm, actually you're right. I guess either I was confused when I wrote
the module or I just wanted everything to look the same :)
Search-and-replace error indeed. Thought that might be it ;-).
Actually
Hi,
just wanted to let interested parties know that I've added a new version
of FindBoost.cmake to bug #6257. It fixes a few bugs I still had in
v2.
I'd delete the existing versions, but unfortunately CMake's bugtracker
doesn't allow to do that.
Last but not least: Is there any chance of getting
On 26.03.08 19:10:16, Matthew Woehlke wrote:
> Andreas Pakulat wrote:
>> Hmm, actually you're right. I guess either I was confused when I wrote
>> the module or I just wanted everything to look the same :)
>
> Search-and-replace error indeed. Thought that might be it ;-).
Actually (after checking
Hi again,
please, how can I pass an EXACT string to a ARGS command in a custom command?
I need to pass the \ because I got a lot of problems with the line feeds.
Thanks in advance.
Leo
A Dijous 27 Març 2008, Leopold Palomo Avellaneda va escriure:
> Hi,
> I'm trying to create a macro for the
KSpam wrote:
My company is using CMake to build a large number of projects (~300). The
developers have complaints regarding the size (and load-time, etc) of the
top-level solution file. I am attempting to address their concerns.
Take this hypothetical project hierarchy:
module-1/
su
2008/3/27, Eric Noulard <[EMAIL PROTECTED]>:
> 2008/3/27, Jerome Arbez-Gindre <[EMAIL PROTECTED]>:
> >
> > #
> > # Cpack configuration
> > #
> > INSTALL(PROGRAMS myscript
> > DESTINATION ${CMAKE_INSTALL_PREFIX}/sbin)
>
> This install command should be rewritten with relative path:
I did
2008/3/27, Jerome Arbez-Gindre <[EMAIL PROTECTED]>:
> Hi,
Hi there :-)
> I am using the CVS version of CMake and I would like to use CMake only for
> its Packaging capabilities.
If you "only" want to package things you may
well only use CPack without CMake, It should be possible if you craft
you
I am happy to announce that CMake 2.6.0 has entered the beta stage! You
can find the source and binaries here: http://www.cmake.org/files/v2.6/.
I am sure I am leaving something out, but here is the list of changes
that I came up with. (If you notice something missing please let me
know and I
Hello all,
I would like to know how to configure CMakeLists.txt files to do the
following :
1- Let a Fortran90 project placed in the /root/fsrc folder link with a C
shared library placed in /root/contrib/clib folder
2- Specify Fortran as the linker (since Fortran is calling C)
In the /root/CMakeL
Fernando Cacciola wrote:
Hi Bill,
Fernando Cacciola wrote:
Hi People,
Due to some project specific constrains, I need to use cmake within
cygwin but to compile using Visual C++ via nmake.
Since the cygwin cmake doesn't support nmake I must use the windows
cmake binary, but naturally knowing t
Hi Bill,
Fernando Cacciola wrote:
Hi People,
Due to some project specific constrains, I need to use cmake within
cygwin but to compile using Visual C++ via nmake.
Since the cygwin cmake doesn't support nmake I must use the windows
cmake binary, but naturally knowing that I am running under cyg
On 25/03/2008, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> Hello,
>
First of all I must say I'm sorry that the message got sent twice.
> I'm trying to build GTK-Qt-Engine 1.1, which use CMake as build system,
> but it fails almost halfway through with the following message:
> [ 44%] Generating
Fernando Cacciola wrote:
Hi People,
Due to some project specific constrains, I need to use cmake within
cygwin but to compile using Visual C++ via nmake.
Since the cygwin cmake doesn't support nmake I must use the windows
cmake binary, but naturally knowing that I am running under cygwin.
Hi People,
Due to some project specific constrains, I need to use cmake within cygwin
but to compile using Visual C++ via nmake.
Since the cygwin cmake doesn't support nmake I must use the windows cmake
binary, but naturally knowing that I am running under cygwin.
I couldn't find any preset v
Hi,
I am using the CVS version of CMake and I would like to use CMake only for
its Packaging capabilities.
My project consists on only one bash script (which is not compile ;-) called
for example "myscript".
SET(PACKAGE_NAME myscript)
SET(PACKAGE_VERSION 1.0)
#
# Cpack configuration
#
INSTALL(
Joachim Geiger wrote:
-Bill
Hello,
I ran a "make Experimental" on the w04 AIX-5.1 system with the compiler
version 6 with cmake-2.4.8 not modified, which means that the
compilation generated errors.
No, I don't think so. I did see the submission, thanks.
http://public.kitware.com/CDash/view
Bill Hoffman wrote:
Joachim Geiger wrote:
I checked out the cvs-version yesterday (cmake-2.7.20080326). This
compiled on the newer without problems. However, running the test
resulted in 3 failures:
97% tests passed, 3 tests failed out of 90
The following tests FAILED:
56 - SimpleIns
Bill Hoffman wrote:
Joachim Geiger wrote:
Sorry for the delay. You didn't scare me away, but I was trying to see
what might be special about the machines I have access to and about
their setup.
So a first result:
There are two machines, one with AIX-5.1 which has due to compatibility
reasons th
Bill Hoffman wrote:
Joachim Geiger wrote:
//No help, variable specified on the command line.
CMAKE_Fortran_COMPILE_FLAGS=-qrealsize:UNINITIALIZED=8
//Flags for Fortran compiler.
CMAKE_Fortran_FLAGS:STRING=-qrealsize=8
So I did not know what to fix there.
However, in the files flags.make and
Joachim Geiger wrote:
//No help, variable specified on the command line.
CMAKE_Fortran_COMPILE_FLAGS=-qrealsize:UNINITIALIZED=8
//Flags for Fortran compiler.
CMAKE_Fortran_FLAGS:STRING=-qrealsize=8
So I did not know what to fix there.
However, in the files flags.make and link.txt in the proje
Bill Hoffman wrote:
Joachim Geiger wrote:
Hello,
I have the following problem with a fortran compiler flag I want to be
accepted. Compiler is the IBM compiler version 8. The compiler flag I
want to be accepted is -qrealsize=8 .
Using CMAKE_VERBOSE_MAKEFILE=ON I see that the compiler flag appe
Joachim Geiger wrote:
Hello,
I have the following problem with a fortran compiler flag I want to be
accepted. Compiler is the IBM compiler version 8. The compiler flag I
want to be accepted is -qrealsize=8 .
Using CMAKE_VERBOSE_MAKEFILE=ON I see that the compiler flag appears as
-fdefault-real
Joachim Geiger wrote:
Sorry for the delay. You didn't scare me away, but I was trying to see
what might be special about the machines I have access to and about
their setup.
So a first result:
There are two machines, one with AIX-5.1 which has due to compatibility
reasons the AIX-compilers of ve
Hello,
I have the following problem with a fortran compiler flag I want to be
accepted. Compiler is the IBM compiler version 8. The compiler flag I
want to be accepted is -qrealsize=8 .
Using CMAKE_VERBOSE_MAKEFILE=ON I see that the compiler flag appears as
-fdefault-real-8
I tried -DCMAKE_Fort
Bill Hoffman wrote:
Bill Hoffman wrote:
Finally, I ran the test. Three of the 68 tests failed, namely:
38/ 68 Testing complex ***Failed
39/ 68 Testing complexOneConfig ***Failed
63/ 68 Testing kwsys ***Failed
The behaviour was the s
On 27Mar, 2008, at 9:27, Andreas Schneider wrote:
Robert Bielik wrote:
I'm compiling under Ubuntu and want to generate 64 bit code. Is
there a way to get cmake to generate
the correct settings in the Makefile ?
I tried adding -m64 (and -march=x86-64) but the __x86_64__ define
does not seem
Robert Bielik wrote:
I'm compiling under Ubuntu and want to generate 64 bit code. Is there a
way to get cmake to generate
the correct settings in the Makefile ?
I tried adding -m64 (and -march=x86-64) but the __x86_64__ define does
not seem to be set. I.e. when using
This define is set by th
Adiel Mittmann skrev:
Are you trying to cross-compile? Otherwise I don't think you have to do anything
special with CMake to make it generate a working Makefile.
Yes, the server I'm compiling on has 32 bit Ubuntu. But I'm getting access to a
64 bit one
soon so I guess my woes are over then :)
41 matches
Mail list logo