Bummer. Thanks for the info though!
On Wed, Mar 18, 2009 at 4:15 PM, Alexander Neundorf wrote:
> On Thursday 19 March 2009, Hai Nguyen wrote:
> > Hi,
> >
> > I'm doing an out of source build in which my structure looks something
> like
> > this:
> > /include
> > /src
> > /kdevelop
> >
> > So fro
Hi,
I'm currently using Visual Studio 2008 and CMake v2.6.3. I noticed that when
I create unit tests, they are not added as dependencies in the solution
containing all of the unit test projects + the RUN_TESTS project. For
example, when I change one of the source files in a particular unit test
pr
On Wed, Mar 18, 2009 at 10:38 PM, John Drescher wrote:
> I have been using CMake with my Qt projects for a few months now and
> every once and a while moc fails with
> "Cannot open options file specified with @"
>
> I did a google search and ended up finding my own post to this list on
> the same
I have been using CMake with my Qt projects for a few months now and
every once and a while moc fails with
"Cannot open options file specified with @"
I did a google search and ended up finding my own post to this list on
the same subject in April of last year.
http://www.cmake.org/pipermail/cmak
Hi,
I'm working on a simple gtkmm program. I use CMake for the makefile
generator. I use GtkBuilder to create the window form, so I need a
non-executable file, "window.xml", locate at the same directory of
executable file which just build.
The directory structure is simple, every files on the top
On Thursday 19 March 2009, Philip Lowman wrote:
> On Wed, Mar 18, 2009 at 7:05 PM, Alexander Neundorf
>
> > wrote:
> >
> > On Wednesday 18 March 2009, Denis Scherbakov wrote:
> > > You could do the following:
> > >
> > > ADD_LIBRARY(intermediate STATIC a.cpp)
> > >
> > > ADD_LIBRARY(foo b.cpp)
> >
On Wed, Mar 18, 2009 at 7:05 PM, Alexander Neundorf wrote:
> On Wednesday 18 March 2009, Denis Scherbakov wrote:
> > You could do the following:
> >
> > ADD_LIBRARY(intermediate STATIC a.cpp)
> >
> > ADD_LIBRARY(foo b.cpp)
> > TARGET_LINK_LIBRARIES(foo intermediate)
> >
> > ADD_LIBRARY(bar c.cpp)
On Thursday 19 March 2009, Hai Nguyen wrote:
> Hi,
>
> I'm doing an out of source build in which my structure looks something like
> this:
> /include
> /src
> /kdevelop
>
> So from within the kdevelop directory - I do:
> cmake .. -G KDevelop3
>
> When I startup kdeveop with my .kdevelop file, it as
On Wednesday 18 March 2009, Bartlett, Roscoe A wrote:
> Hello,
>
> How can we get CMake to deal with installed shared libraries and set the
> rpath correctly in a portable way? The issue is that we have is that we
> need to enable client applications to link to installed Trilinos shared
> librarie
Hi,
I'm doing an out of source build in which my structure looks something like
this:
/include
/src
/kdevelop
So from within the kdevelop directory - I do:
cmake .. -G KDevelop3
When I startup kdeveop with my .kdevelop file, it asks me what directories I
want to add. I select the kdevelop one. K
On Wednesday 18 March 2009, Denis Scherbakov wrote:
> Dear CMake Community,
>
> Could anyone give me a hint, how to check if a system can handle SIGFPE
> signal and set HAVE_SIGFPE variable.
>
> For example, linux on alpha machines produces a core dump instead of
> SIGFPE.
When do you get a SIGFPE
On Wednesday 18 March 2009, Denis Scherbakov wrote:
> You could do the following:
>
> ADD_LIBRARY(intermediate STATIC a.cpp)
>
> ADD_LIBRARY(foo b.cpp)
> TARGET_LINK_LIBRARIES(foo intermediate)
>
> ADD_LIBRARY(bar c.cpp)
> TARGET_LINK_LIBRARIES(bar intermediate)
That's not portable if bar and foo
Hi all~
I'm having trouble figuring out how to select the appropriate subsystem
for my cmake windows ifort project, with the IDE build environment.
By default, unless otherwise specified, intel's Fortran runtime file are
linked in statically. Everything works fine statically; no errors. I
prefe
Hello,
How can we get CMake to deal with installed shared libraries and set the rpath
correctly in a portable way? The issue is that we have is that we need to
enable client applications to link to installed Trilinos shared libraries and
provide for them, in an automatic way, the right link li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
cygwin of known for its poor performance wrt some disc i/o operations.
I'm already making some changes which will enhance cmake timings on
cygwin, would you guys be interested receiving them, or maybe somebody
from cmake team is already working
On 18.03.09 11:31:13, Eric Lemings wrote:
> When I try to link a static library into a shared library on SUSE Linux
> 11, I get the following link error:
>
> /usr/bin/c++ -fPIC -shared -Wl,-soname,libbar.so -o libbar.so
> CMakeFiles/shared_bar_lib.dir/Bar.cpp.o
> CMakeFiles/shared_bar_lib.dir/_
On Wed, Mar 18, 2009 at 2:50 PM, John Drescher wrote:
> -- Forwarded message --
>
> Please remember to send this to the cmake list as well. There are
> experts who should be better help than me..
My apologies, I thought I was!
Thanks,
George.
_
-- Forwarded message --
Please remember to send this to the cmake list as well. There are
experts who should be better help than me..
On Wed, Mar 18, 2009 at 2:35 PM, George Neill wrote:
> All,
>
> On Wed, Mar 18, 2009 at 1:20 PM, John Drescher wrote:
>>> It seems the following
All,
On Wed, Mar 18, 2009 at 1:20 PM, John Drescher wrote:
>> It seems the following works (at least the cmake_install.cmake
>> commands appear to get generated appropriately).
>>
>> FILE(TO_CMAKE_PATH "${CMAKE_INSTALL_PREFIX}" CMAKE_INSTALL_PREFIX)
>>
>> Is there a CMP policy which deals wit
On Thursday 05 February 2009 18:27:06 David Cole wrote:
> I agree with Clint. This belongs in the new cmCPackDragNDropGenerator.
Please find attached a new patch for the DND generator. Sorry about the delay!
--
Cheers,
Mike Arthur
http://mikearthur.co.uk/
--- Source/CPack/cmCPackDragNDropGenerato
On Wednesday 18 March 2009 17:51:47 Clinton Stimpson wrote:
> I like that better. With the CPACK_DMG_* variables, one can even have
> the PackageMaker generator use those variables.
Have you had a chance to check it works correctly? I've not tested it
extensively as it's basically identical to th
John,
On Wed, Mar 18, 2009 at 12:57 PM, John Drescher wrote:
>> Here is what I do for Program Files
>>
>> string (REPLACE "\\" "/" PGM_FILES $ENV{PROGRAMFILES})
>>
>> then I use PGM_FILES and there is no complaint about bad escape sequences.
>>
> BTW, here is the whole section:
>
> IF(WIN32)
>
>
> Here is what I do for Program Files
>
> string (REPLACE "\\" "/" PGM_FILES $ENV{PROGRAMFILES})
>
> then I use PGM_FILES and there is no complaint about bad escape sequences.
>
BTW, here is the whole section:
IF(WIN32)
#The following command changes \ to / in the Program Files Path so
CMake will
On Wed, Mar 18, 2009 at 1:43 PM, George Neill wrote:
> Hi All,
>
> On windows, I pass CMAKE_INSTALL_PREFIX on the command line e.g.
> "-DCMAKE_INSTALL_PREFIX=c:\some\path". In my cmake code I use
> variable which contain the suffixes /lib, /man/man1 etc...
>
> The install commands end up lookin
Use all "/" instead of "\" -- cmake understands either, but the "/" do not
have to be escaped...
On Wed, Mar 18, 2009 at 1:43 PM, George Neill wrote:
> Hi All,
>
> On windows, I pass CMAKE_INSTALL_PREFIX on the command line e.g.
> "-DCMAKE_INSTALL_PREFIX=c:\some\path". In my cmake code I use
>
Mike Arthur wrote:
On Wednesday 18 February 2009 12:31:25 Mike Arthur wrote:
Please review the attached patch for inclusion.
It adds support to the bundle generator to allow customisation of the
volume name and hdiutil compression type used to create the DMG.
A new version of this patc
Hi All,
On windows, I pass CMAKE_INSTALL_PREFIX on the command line e.g.
"-DCMAKE_INSTALL_PREFIX=c:\some\path". In my cmake code I use
variable which contain the suffixes /lib, /man/man1 etc...
The install commands end up looking like this,
C:\some\path/man/man1/some_man_file
In 2.4 this
On Wednesday 18 February 2009 12:31:25 Mike Arthur wrote:
> Please review the attached patch for inclusion.
>
> It adds support to the bundle generator to allow customisation of the
> volume name and hdiutil compression type used to create the DMG.
A new version of this patch against the DND genera
When I try to link a static library into a shared library on SUSE Linux
11, I get the following link error:
/usr/bin/c++ -fPIC -shared -Wl,-soname,libbar.so -o libbar.so
CMakeFiles/shared_bar_lib.dir/Bar.cpp.o
CMakeFiles/shared_bar_lib.dir/__/__/include/moc_Bar.cxx.o
-L/my/build/path/archive -L
2009/3/18 Stephen Collyer :
> I've been trying to use CPack to generate an RPM package with cmake 2.6.2.
>
> I have the following trivial CMakeLists.txt:
>
>
>
> PROJECT(PRINT)
> CMAKE_MINIMUM_REQUIRED(VERSION 2.6)
>
> ADD_LIBRARY(print print.cpp)
>
> SE
I've been trying to use CPack to generate an RPM package with cmake 2.6.2.
I have the following trivial CMakeLists.txt:
PROJECT(PRINT)
CMAKE_MINIMUM_REQUIRED(VERSION 2.6)
ADD_LIBRARY(print print.cpp)
SET(PRINTER_SRCS main.cpp)
ADD_EXECUTABLE(printer
On Wed, Mar 18, 2009 at 3:28 AM, Oliver Kania
wrote:
> I think using Cmake implies having to manually add the names of new files
> etc. to the Cmake file, doesnt it ? Whenever the project changes, I have to
> "regenerate" the visual studio solution. I do not consider this to be
> convenient.
> It
Dear CMake Community,
Could anyone give me a hint, how to check if a system can handle SIGFPE signal
and set HAVE_SIGFPE variable.
For example, linux on alpha machines produces a core dump instead of SIGFPE.
Many thanks in advance.
Denis
___
You could do the following:
ADD_LIBRARY(intermediate STATIC a.cpp)
ADD_LIBRARY(foo b.cpp)
TARGET_LINK_LIBRARIES(foo intermediate)
ADD_LIBRARY(bar c.cpp)
TARGET_LINK_LIBRARIES(bar intermediate)
Denis
> One of the users I support complained about the following:
>
> add_library(foo a.c b.c)
>
34 matches
Mail list logo
