Unfortunately this does not work. It seems that CMake generates all
libraries defined in one CMakeLists.txt with the setting of
CMAKE_SHARED_LINKER_FLAGS at the end of the file.
This causes this setting to be applied to all libraries in the
CMakeLists.txt. As I have 4 libraries in this one CMakeLis
On Wed, Sep 3, 2008 at 2:01 PM, Convey, Christian J CIV NUWC NWPT <
[EMAIL PROTECTED]> wrote:
> From the mail archives and personal experience, it looks to me like
> commands of the form:
> SET(CMAKE_BUILD_TYPE Debug)
>
> aren't effective. I don't think I fully understood the explanations of
>
Thanks; I gave up on trying to get long filenames to work. There are too many
levels involved, and if you get it right on 1-n, then n+1 messes it up, etc.,
etc.
Right, the I took out the FORCE_C_COMPILER stuff. But it still breaks things it
shouldn't.
z/OS is indeed not the only OS on System z
Maybe save and restore the CMAKE_SHARED_LINKER_FLAGS around your reset of it
in the sub-CMakeLists.txt...?
On Wed, Sep 3, 2008 at 10:41 AM, Martin Apel <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have defined the following in a top-level CMakeLists.txt:
> SET (CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHAR
On 2008-09-03 20:16-0400 Andrew Sayman wrote:
On Wed, Sep 3, 2008 at 7:57 PM, Christopher Harvey
<[EMAIL PROTECTED]> wrote:
try getting rid of quotes
Getting rid of the quotes doesn't change anything.
putting them all in a single command.
This isn't helpful without removing all of the ben
${PLINK_EXECUTABLE} contains spaces...
Maybe you need escaped quotes:
SET(CMAKE_CXX_LINK_EXECUTABLE "\"${PLINK_EXECUTABLE}\"
\" around the executable variable reference...?
On Wed, Sep 3, 2008 at 6:04 PM, Alexander Neundorf
<[EMAIL PROTECTED]>wrote:
> On Monday 25 August 2008, Phil Smith wrote
On Wed, Sep 3, 2008 at 7:57 PM, Christopher Harvey
<[EMAIL PROTECTED]> wrote:
> try getting rid of quotes
Getting rid of the quotes doesn't change anything.
> putting them all in a single command.
This isn't helpful without removing all of the benefits of the CMake
standard modules. If I wanted
usually, I just do this type of thing:
TARGET_LINK_LIBRARIES(binary SDL GL GLU GLEW)
try getting rid of quotes, and putting them all in a single command.
Andrew Sayman wrote:
I've been working on linking to some system libraries in a project I'm
building in Linux and I've run into a problem wit
I've been working on linking to some system libraries in a project I'm
building in Linux and I've run into a problem with CMake adding
redundant linker arguments.
The simplest case I came down to is this:
In the Example/Demo/CMakeLists.txt file add the following lines:
target_link_libraries (hello
The FIND_PROGRAM(CMAKE_RC_COMPILER NAMES ${CMAKE_RC_COMPILER_LIST} DOC "RC
compiler") line in CMakeDetermineRCCompiler.cmake is setting
CMAKE_RC_COMPILER_LIST to "rc". I'll debug further this evening.
Craig
-Original Message-
From: Bill Hoffman [mailto:[EMAIL PROTECTED]
Sent: Wednesday
On Monday 25 August 2008, Phil Smith wrote:
> I'm back on this, after a week at a conference and a week of vacation.
>
> I have the GET_FILENAME_COMPONENT call working, and it returns what I'd
> expect (c:/progra~1/dignus), but the FIND_PROGRAM resolves the path with
> blanks (c:/Program Files/Dign
On Wednesday 03 September 2008, Andreas Pakulat wrote:
> On 03.09.08 17:52:02, Alexander Neundorf wrote:
> > On Thursday 28 August 2008, Andreas Pakulat wrote:
> > > On 28.08.08 10:16:48, BRM wrote:
> >
> > ...
> >
> > > IMHO the approach to regenerate project description files for an IDE
> > > fro
Renato N. Elias wrote:
Bill Hoffman wrote:
Renato N. Elias wrote:
A managed to do something work (but not in the way that I'd like). In
CMake, when configuring my project, if a check the "Show Advanced
Values" and insert a "/c" in the CMAKE_Fortran_FLAGS the project works
fine.
Weir
On 03.09.08 17:52:02, Alexander Neundorf wrote:
> On Thursday 28 August 2008, Andreas Pakulat wrote:
> > On 28.08.08 10:16:48, BRM wrote:
> ...
> > IMHO the approach to regenerate project description files for an IDE
> > from a buildsystem tool is simply broken.
>
> Well, it has to. Otherwise the
It shouldn't make a difference to the cmake variables. The debug libraries
get installed into the same frameworks. And cmake references the frameworks,
not the libraries within the frameworks. To run your application with the
debug libraries in the frameworks, you set the environment variabl
Thanks, Clint!
As you say, they provide a separate debug library, ie see:
http://trolltech.com/developer/downloads/qt/mac
qt-mac-opensource-4.4.1.dmg
qt-mac-opensource-4.4.1-debug-libs.dmg (dmg containing ONLY the debug
libraries, only usable with dmg above installed)
I'll check this out and see
On Tuesday 26 August 2008, Rex Dieter wrote:
> John Fine wrote:
> > Ulrich Drepper wrote:
> >> It's most certainly not that simple. I haven't looked at the sources.
> >> But the asm code does not really correspond to the code above. The
> >> function above is most certainly inlined. The problem m
Craig Miller wrote:
Yep, a Visual Studio 2005 target works.
The output of rc /? is:
c:\users\craig\nav\maps\basemaps\install>rc /?
Microsoft (R) Windows (R) Resource Compiler Version 5.2.3690.0
Copyright (C) Microsoft Corporation. All rights reserved.
c:\users\craig\nav\maps\basemaps\i
Forgot to answer the last question... I did a custom compiler installation,
but only so far as selecting whether or not I wanted Visual C++, Visual
Basic, etc. Nothing fancy and nmake, etc all work from the Visual Studio
command prompt (I use them everyday).
Craig
-Original Message-
Fro
Yep, a Visual Studio 2005 target works.
The output of rc /? is:
c:\users\craig\nav\maps\basemaps\install>rc /?
Microsoft (R) Windows (R) Resource Compiler Version 5.2.3690.0
Copyright (C) Microsoft Corporation. All rights reserved.
Usage: rc [options] .RC input file
Switches:
/rEmit .
On Wednesday 03 September 2008 12:28:57 pm Darren Weber wrote:
> In ccmake settings for VTK-5-2 with Qt 4.4 on OSX, I see a lot of
> settings like this:
>
> QT_QTCORE_LIBRARY
> optimized;/Library/Frameworks/QtCore.framework;debug;/Library/Frameworks/Qt
>Core.framework QT_QTCORE_LIBRARY_DEBUG QT_Q
In ccmake settings for VTK-5-2 with Qt 4.4 on OSX, I see a lot of
settings like this:
QT_QTCORE_LIBRARY
optimized;/Library/Frameworks/QtCore.framework;debug;/Library/Frameworks/QtCore.framework
QT_QTCORE_LIBRARY_DEBUG QT_QTCORE_LIBRARY_DEBUG-NOTFOUND
The optimized and debug libraries are both s
I think we may be on the "right" track with addition(s) to the DYLD path, ie:
[ [EMAIL PROTECTED] ~/src/kitware/VTK_build ]$ echo $DYLD_LIBRARY_PATH
[ [EMAIL PROTECTED] ~/src/kitware/VTK_build ]$ export
DYLD_LIBRARY_PATH=/usr/local/lib/vtk-5.2
[ [EMAIL PROTECTED] ~/src/kitware/VTK_build ]$ echo $
>From the mail archives and personal experience, it looks to me like
commands of the form:
SET(CMAKE_BUILD_TYPE Debug)
aren't effective. I don't think I fully understood the explanations of
why, though.
If it's ok to specify this variable on the cmake command line ( cmake
-DCMAKE_BUILD_TYPE=D
Quoting John Giordano <[EMAIL PROTECTED]>:
Hello:
I have been trying desperately to get CMake to configure my system
with no luck.
I am hoping someone can help me.
I have the gcc compiler running as a cross compiler producing code for
a coldfire V2 chip.
The Netburner company has sup
Craig Miller wrote:
I'm running Visual Studio 2005 w/ SP1.
OK, so lets start from the beginning... Create a very simple project:
---CMakeLists.txt--
cmake_minimum_required (VERSION 2.6)
project(bar)
add_library(foo foo.c)
-
foo.c
int foo()
{
return 1;
}
Put th
On Tuesday 26 August 2008, Philip Lowman wrote:
> On Mon, Aug 25, 2008 at 10:31 AM, Fernando Cacciola <
>
> [EMAIL PROTECTED]> wrote:
> > And while you are it.. I currently use: set(var) to read the value
> > back from the cache (very usefull somtimes), but this is undocumented and
> > extremely no
Craig Miller wrote:
Yeah, I made a few posts last week with the details of the specific problem
I'm having. A couple of folks tried to help, but in the end they were
stumped too.
Here's an excerpt with the meat of the problem from one of those posts:
On Aug 28, 2008, at 5:04 PM, Craig Miller
On Sep 3, 2008, at 1:01 PM, Darren Weber wrote:
Thanks heaps for some very useful insight into resolving my OSX
nightmares.
It always helps to RTFM! I was starting to think there is a problem
within the .so file and how it specifies the location of the dylib
required (path and version). As
otool -L [complete path to library] is what you are looking for. That
will reveal all the libraries and any rpaths that were used in the
linking process.
On Sep 3, 2008, at 1:01 PM, Darren Weber wrote:
As yet, I have no idea how to "debug"
that. I was stratching around for ldd or someth
Yeah, I made a few posts last week with the details of the specific problem
I'm having. A couple of folks tried to help, but in the end they were
stumped too.
Here's an excerpt with the meat of the problem from one of those posts:
> On Aug 28, 2008, at 5:04 PM, Craig Miller wrote:
>
>> Mike,
>>
Thanks heaps for some very useful insight into resolving my OSX nightmares.
It always helps to RTFM! I was starting to think there is a problem
within the .so file and how it specifies the location of the dylib
required (path and version). As yet, I have no idea how to "debug"
that. I was strat
I've been using CMake on Vista 64 for a while, even with big projects.
I've not had the problems you've had from your previous posts.
Clint
On Wednesday 03 September 2008 10:45:14 am Craig Miller wrote:
> Thanks for the reply Alex. As a new user, I wasn't aware of the wiki and
> didn't think to
Craig Miller wrote:
Thanks for the reply Alex. As a new user, I wasn't aware of the wiki and
didn't think to look under the developer menu (thought it was for CMake
devs, not devs using CMake). I was following the directions under
http://www.cmake.org/HTML/Documentation.html.
I'll take a cl
On Thursday 28 August 2008, Andreas Pakulat wrote:
> On 28.08.08 10:16:48, BRM wrote:
...
> IMHO the approach to regenerate project description files for an IDE
> from a buildsystem tool is simply broken.
Well, it has to. Otherwise the project file become wrong. That's not a big
problem for the
On Saturday 23 August 2008, Darren Weber wrote:
> What is CMAKE_OBJCOPY and CMAKE_OBJDUMP? They are not found on my system. I
> don't see an entry in the book index for these variables.
If found, they point to objcopy and objdump from the binutils.
They are currently more or less only there for co
On Thursday 28 August 2008, Vandenbroucke Sander wrote:
...
> I'm still on 2.4. Upgrading is planned some time in the future.
>
> > What is your exact original command line for running CMake?
>
> set CC=distcc nios2-elf-gcc
> set CXX=distcc nios2-elf-g++
> cmake -G "MSYS Makefiles" ../ -DCMAKE_SYST
Thanks for the reply Alex. As a new user, I wasn't aware of the wiki and
didn't think to look under the developer menu (thought it was for CMake
devs, not devs using CMake). I was following the directions under
http://www.cmake.org/HTML/Documentation.html.
I'll take a closer look, but a quick
On Thursday 28 August 2008, Craig Miller wrote:
...
> Any links to recent tutorials would be very appreciated.
Did you have a look at the wiki ?
It's in the "Developers" menu.
Beside that, if you find things which are missing/wrong in the html pages for
documentation, please consider filing bug
On Wednesday 03 September 2008 5:41:53 am Nicolas Desprès wrote:
> Hi,
>
> I'm using cmake 2.6.0 and Qt-4.4.1 commercial on windows. While trying
> to compile my Qt application in release mode using
> -DCMAKE_BUILD_TYPE=Release, I met a problem with conditional Qt slots.
> In one of my header, I ha
Hi,
I have defined the following in a top-level CMakeLists.txt:
SET (CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS}
-Wl,--unresolved-symbols=ignore-in-shared-libs")
Now I'd like to reset this for one specific library in a subdirectory
(in a separate CMakeLists.txt added with ADD_SUBDIR
Hello:
I have been trying desperately to get CMake to configure my system
with no luck.
I am hoping someone can help me.
I have the gcc compiler running as a cross compiler producing code for
a coldfire V2 chip.
The Netburner company has supplied me with the gcc toolchain for cross
comp
Anders Moe wrote:
Thank for answering.
I'm using the CmakeSetup.exe utility and interactively pick the Visual
Studio 8 2005 compiler when it asks meI hope that answered the
question ?
The error dialog doesn't allow copy/paste, or I'd include more info.
The information should be i
Hi,
I'm using cmake 2.6.0 and Qt-4.4.1 commercial on windows. While trying
to compile my Qt application in release mode using
-DCMAKE_BUILD_TYPE=Release, I met a problem with conditional Qt slots.
In one of my header, I have something like that:
#ifndef NDEBUG
void mySlot()
#endif
In debug mod
Thank for answering.
I'm using the CmakeSetup.exe utility and interactively pick the Visual Studio 8
2005 compiler when it asks meI hope that answered the question ?
The error dialog doesn't allow copy/paste, or I'd include more info.
Regards,
Anders
__
What CMake generator are you using?
On Wed, Sep 3, 2008 at 4:10 AM, Anders Moe <[EMAIL PROTECTED]> wrote:
>
>
> Hi all
>
> I'm trying to compile a 32 bit version of VTK using the 32 bit MSVC 2005
> command shell. Note that I'm running XP64.
>
> This works fine for Qt, but cmake gives an error du
Hi all
I'm trying to compile a 32 bit version of VTK using the 32 bit MSVC 2005
command shell. Note that I'm running XP64.
This works fine for Qt, but cmake gives an error during the "simpel test
program compile" where it appears that the test solution *.sln is setup for
x64, since the er
Darren Weber wrote:
[]
ImportError:
dlopen(/usr/local/lib/python2.5/site-packages/vtk/libvtkCommonPython.so,
10): Library not loaded: libvtkCommonPythonD.5.2.dylib
Referenced from:
/usr/local/lib/python2.5/site-packages/vtk/libvtkCommonPython.so
Reason: image not found
This is not a prob
48 matches
Mail list logo
