On Nov 7, 2007 2:12 AM, Salvatore Iovene
[EMAIL PROTECTED] wrote:
Hi,
I'm not 100% sure this is really a CMake related question, but I'll
fire it up anyway:
I'm building a series of static libraries, name them liba.a, libb.a
and libc.a, and linking them into a shared library libfoo.so.
Would it be possible for you to run ctest in gdb or some debugger and
send a call stack of the crash?
Here is the stack juste after Ctest crashed
(gdb) bt
#0 0x00d5175d in std::string::append () from /usr/lib/libstdc++.so.6
#1 0x00d51972 in std::string::operator+= () from
On 11/7/07, Brandon Van Every [EMAIL PROTECTED] wrote:
On Nov 7, 2007 2:12 AM, Salvatore Iovene
[EMAIL PROTECTED] wrote:
Hi,
I'm not 100% sure this is really a CMake related question, but I'll
fire it up anyway:
I'm building a series of static libraries, name them liba.a, libb.a
and
OK, CMake does not know what you are doing here. It is treating
LDFLAGS like some linker flag. The idea was something like -64 or
some other linker specific flag for a platform.
Ok.
If you inject directories into the link line, you are sort of out
of luck. Why are you doing it this
On 07 Nov 2007, at 09:59, Salvatore Iovene wrote:
On 11/7/07, Brandon Van Every [EMAIL PROTECTED] wrote:
On Nov 7, 2007 2:12 AM, Salvatore Iovene
[EMAIL PROTECTED] wrote:
Hi,
I'm not 100% sure this is really a CMake related question, but I'll
fire it up anyway:
I'm building a series of
On 11/7/07, Renaud Detry [EMAIL PROTECTED] wrote:
On 07 Nov 2007, at 09:59, Salvatore Iovene wrote:
On 11/7/07, Brandon Van Every [EMAIL PROTECTED] wrote:
On Nov 7, 2007 2:12 AM, Salvatore Iovene
[EMAIL PROTECTED] wrote:
Hi,
I'm not 100% sure this is really a CMake related question,
On 11/7/07, Renaud Detry [EMAIL PROTECTED] wrote:
On 07 Nov 2007, at 11:04, Salvatore Iovene wrote:
On 11/7/07, Renaud Detry [EMAIL PROTECTED] wrote:
On 07 Nov 2007, at 09:59, Salvatore Iovene wrote:
On 11/7/07, Brandon Van Every [EMAIL PROTECTED] wrote:
On Nov 7, 2007 2:12 AM,
On 07 Nov 2007, at 11:35, Salvatore Iovene wrote:
On 11/7/07, Renaud Detry [EMAIL PROTECTED] wrote:
On 07 Nov 2007, at 11:04, Salvatore Iovene wrote:
On 11/7/07, Renaud Detry [EMAIL PROTECTED] wrote:
On 07 Nov 2007, at 09:59, Salvatore Iovene wrote:
On 11/7/07, Brandon Van Every [EMAIL
On 07 Nov 2007, at 11:04, Salvatore Iovene wrote:
On 11/7/07, Renaud Detry [EMAIL PROTECTED] wrote:
On 07 Nov 2007, at 09:59, Salvatore Iovene wrote:
On 11/7/07, Brandon Van Every [EMAIL PROTECTED] wrote:
On Nov 7, 2007 2:12 AM, Salvatore Iovene
[EMAIL PROTECTED] wrote:
Hi,
I'm not 100%
On 11/7/07, Renaud Detry [EMAIL PROTECTED] wrote:
On 07 Nov 2007, at 11:35, Salvatore Iovene wrote:
On 11/7/07, Renaud Detry [EMAIL PROTECTED] wrote:
On 07 Nov 2007, at 11:04, Salvatore Iovene wrote:
On 11/7/07, Renaud Detry [EMAIL PROTECTED] wrote:
On 07 Nov 2007, at 09:59,
On 11/7/07, Hendrik Sattler [EMAIL PROTECTED] wrote:
Quoting Salvatore Iovene [EMAIL PROTECTED]:
On 11/7/07, Salvatore Iovene [EMAIL PROTECTED] wrote:
What do you mean by PIC?
Thanks!
Oh, -fPIC. I figured it out. Seems to work fine on Linux. I still have
to try it on Windows tho. I
On 11/7/07, Salvatore Iovene [EMAIL PROTECTED] wrote:
What do you mean by PIC?
Thanks!
Oh, -fPIC. I figured it out. Seems to work fine on Linux. I still have
to try it on Windows tho. I hope it's good as a solution and not just
a hack! :)
--
Salvatore Iovene
http://www.iovene.com/
Key
Hi list,
I'm doing the following:
CHECK_CXX_COMPILER_FLAG(-fPIC HAVE_FPIC_FLAG)
IF(HAVE_FPIC_FLAG)
SET(${CMAKE_CXX_FLAGS} ${CMAKE_CXX_FLAGS} -fPIC)
ENDIF(HAVE_FPIC_FLAG)
And the same with -pipe and -g.
This works fine in Linux, but when trying on WIN32 with Visual Studio
command line prompt,
Quoting Salvatore Iovene [EMAIL PROTECTED]:
On 11/7/07, Salvatore Iovene [EMAIL PROTECTED] wrote:
What do you mean by PIC?
Thanks!
Oh, -fPIC. I figured it out. Seems to work fine on Linux. I still have
to try it on Windows tho. I hope it's good as a solution and not just
a hack! :)
Windows
Hey Brandon...
You will find the stuff in attachment.
Cheers,
Ronan.
Brandon Van Every wrote:
Please provide a reproducer script so others of us can test your claim.
Cheers,
Brandon Van Every
On Nov 6, 2007 6:04 PM, Ronan Collobert [EMAIL PROTECTED] wrote:
Hi,
I have been using
Hi Philip,
Thanks for your help. I down-graded to 2.4.6 but no luck. Here's my exact text:
SET(VS_MULTITHREADED_DEBUG_IGNORE_LIBRARY_FLAGS
/NODEFAULTLIB:nafxcwd.lib
/NODEFAULTLIB:libcmtd.lib
)
SET_TARGET_PROPERTIES(my_test_app PROPERTIES
LINK_FLAGS_DEBUG
On Nov 6, 2007 6:04 PM, Ronan Collobert [EMAIL PROTECTED] wrote:
I also changed the prefixes of the dll using:
SET(CMAKE_SHARED_LIBRARY_PREFIX lib)
SET(CMAKE_IMPORT_LIBRARY_PREFIX lib)
I've never used this mechanism to set library prefixes. I have always
used SET_TARGET_PROPERTIES, using
Yes, indeed, it does work with SET_TARGET_PROPERTIES.
CMAKE_SHARED_LIBRARY_PREFIX advantage is that it set up the prefix for
all libraries. So no need each time you have a library target to have
this SET_TARGET_PROPERTIES additional line.
Like that, I do not remember where I saw doc about
On Nov 7, 2007 11:08 AM, KSpam [EMAIL PROTECTED] wrote:
Static linking is a strange beast. When you link in a static library, it will
only resolve symbols that are currently being used. All other symbols from
the static library are pruned out. The nice thing is that this reduces the
binary
Hello,
There a much nicer platform independent writeup on this at:
http://www.cmake.org/Wiki/CMake_FAQ#Does_that_mean_I_have_to_build_all_my_library_objects_twice.2C_once_for_shared_and_once_for_static.3F.21__I_don.27t_like_that.21
There may be a couple of syntactical issues with the writeup.
Two things with convenience libraries. Part of this may be in the FAQ:
On linux, compile the code fPIC or fpic (slightly different meanings).
So for library hello:
SET_TARGET_PROPERTIES(
hello PROPERTIES
OUTPUT_NAME hello
CLEAN_DIRECT_OUTPUT 1
COMPILE_FLAGS -fPIC
)
where hello is the name of
Renaud Detry wrote:
OK, CMake does not know what you are doing here. It is treating
LDFLAGS like some linker flag. The idea was something like -64 or
some other linker specific flag for a platform.
Ok.
If you inject directories into the link line, you are sort of out of
luck. Why are you
Salvatore,
It sounds like your static libraries were meant strictly as convenience
libraries (i.e. libraries that are only used internal to the build system to
make building other libraries easier). In CMake, it is much easier to not
use convenience libraries. Instead, just add all of the
Hello all,
I intend to start to send my tests to a Dart server. My very first
problem is to figure what's the difference between INCLUDE(Dart) and
INCLUDE(CTest).
I have my tests working, but I just used ENABLE_TESTS() until now.
Thanks in advance,
--
Vitor
Baptiste Derongs wrote:
Would it be possible for you to run ctest in gdb or some debugger and
send a call stack of the crash?
Here is the stack juste after Ctest crashed
(gdb) bt
#0 0x00d5175d in std::string::append () from /usr/lib/libstdc++.so.6
#1 0x00d51972 in std::string::operator+= ()
Another stupid newbie question --
How does one set/change the compiler and linker flags variables?
Putting things like
STRING(REPLACE /MD /MT CMAKE_CXX_FLAGS_RELEASE ${CMAKE_CXX_FLAGS_RELEASE})
or even
SET( CMAKE_EXE_LINKER_FLAGS
${CMAKE_EXE_LINKER_FLAGS} /noDefaultLib:MSVCRT
Hi,
when I compile a qt plugin in release mode (and therefore link against
release qt lib) I've the problem that cmake does not set -DQT_NO_DEBUG .
Because of this Qt assumes we're compiling this plugin in debug mode:
qconfig.h:
==
#if !defined(QT_NO_DEBUG) !defined(QT_DEBUG)
# define
On Wednesday 07 November 2007, Matthew McCormick wrote:
Hi,
Having difficulty changing the object file extension. In my
CMakeLists.txtI have
SET(CMAKE_C_OUTPUT_EXTENSION .obj)
SET(CMAKE_CXX_OUTPUT_EXTENSION .obj)
but I still get *.o object files.
Yes, that's too late in the cmake
On Nov 7, 2007 6:35 AM, Salvatore Iovene
[EMAIL PROTECTED] wrote:
Hi list,
I'm doing the following:
CHECK_CXX_COMPILER_FLAG(-fPIC HAVE_FPIC_FLAG)
IF(HAVE_FPIC_FLAG)
SET(${CMAKE_CXX_FLAGS} ${CMAKE_CXX_FLAGS} -fPIC)
ENDIF(HAVE_FPIC_FLAG)
And the same with -pipe and -g.
This works fine
Hi,
Having difficulty changing the object file extension. In my
CMakeLists.txtI have
SET(CMAKE_C_OUTPUT_EXTENSION .obj)
SET(CMAKE_CXX_OUTPUT_EXTENSION .obj)
but I still get *.o object files.
I am working with cmake version 2.4-patch 7 on Cygwin.
Thanks.
On Nov 7, 2007 2:09 PM, Ronan Collobert [EMAIL PROTECTED] wrote:
Yes, indeed, it does work with SET_TARGET_PROPERTIES.
CMAKE_SHARED_LIBRARY_PREFIX advantage is that it set up the prefix for
all libraries. So no need each time you have a library target to have
this SET_TARGET_PROPERTIES
ok thanks -- well, the variable works fine on all system i tried except
windows. i have a workaround, just wanted to mention the problem.
even under windows, it recognizes it, as it creates libfoo.dll and
libfoo.lib. it is only when linking, that somebody forgot about these
prefixes: it tries
I believe this to be the more accurate than the FAQ and my previous
example. In addition, the static and shared libraries can have the same
name.
Note that cat.cc is an empty file, since the linker will not work
without at least one object file on the dynamic target.
IF(CMAKE_SYSTEM_NAME
Hi,
Having difficulty changing the object file extension. In my
CMakeLists.txtI have
SET(CMAKE_C_OUTPUT_EXTENSION .obj)
SET(CMAKE_CXX_OUTPUT_EXTENSION .obj)
but I still get *.o object files.
Yes, that's too late in the cmake language setup process. What do you need
that for
On Wednesday 07 November 2007, Matthew McCormick wrote:
Hi,
Having difficulty changing the object file extension. In my
CMakeLists.txtI have
SET(CMAKE_C_OUTPUT_EXTENSION .obj)
SET(CMAKE_CXX_OUTPUT_EXTENSION .obj)
but I still get *.o object files.
Yes, that's too
Jesper Eskilson wrote:
KSpam wrote:
If you run the ZERO_CHECK target, CMake will generate the new project
files without building everything. Following ZERO_CHECK, Visual
Studio would have to reload the projects, and then you could build
like normal. This makes building in Visual Studio
It begins with:
MACRO(CHECK_C_SOURCE_COMPILES SOURCE VAR)
IF(${VAR} MATCHES ^${VAR}$)
What is the intent here? If ${VAR} contains regex special characters
you're going to get all kinds of weird and nasty behavior.
Cheers,
Brandon Van Every
___
Am Mittwoch 07 November 2007 22:13:32 schrieb Matthew McCormick:
I'm trying to work with a compiler where you cannot specify the object
extension, the Matlab mex (pseudo) compiler.
I tried this,
$ CMAKE_C_OUTPUT_EXTENSION=.obj CMAKE_CXX_OUTPUT_EXTENSION=.obj ccmake
On 2007-11-07 11:55-0500 Brandon Van Every wrote:
On Nov 7, 2007 11:08 AM, KSpam [EMAIL PROTECTED] wrote:
Static linking is a strange beast. When you link in a static library, it will
only resolve symbols that are currently being used. All other symbols from
the static library are pruned
On Nov 7, 2007 3:49 PM, Ronan Collobert [EMAIL PROTECTED] wrote:
ok thanks -- well, the variable works fine on all system i tried except
windows. i have a workaround, just wanted to mention the problem.
even under windows, it recognizes it, as it creates libfoo.dll and
libfoo.lib. it is only
-- Forwarded message --
From: Matthew McCormick [EMAIL PROTECTED]
Date: Nov 7, 2007 5:10 PM
Subject: Re: RE: Re: changing object file extension from .o
To: [EMAIL PROTECTED]
The mex compiler is really a bunch of scripts, shell scripts in unix and
mostly a perl script in Windows,
Neat! The mex file I'm also working on also happens to use the Boost Spirit
libraries for parsing. Such a cool library. Powerful. The operator
overloading is very effective.
I'm also using MinGW that was set up with gnumex
http://gnumex.sourceforge.net/.
I have set up CMake with MEX-file
On Thursday 08 November 2007, Matthew McCormick wrote:
-- Forwarded message --
From: Matthew McCormick [EMAIL PROTECTED]
Date: Nov 7, 2007 5:10 PM
Subject: Re: RE: Re: changing object file extension from .o
To: [EMAIL PROTECTED]
The mex compiler is really a bunch of scripts,
Hi Salvatore,
On Monday 05 November 2007, Salvatore Iovene wrote:
On 11/3/07, Alexander Neundorf [EMAIL PROTECTED] wrote:
...
Which compiler do you use ?
mwccsym2.exe (Nokia codewarrior C/C++ compiler for winscw platform) and
gcce (for GCCE platform)
Please put the attached
Juan Sanchez wrote:
I was reading exactly the link you sent, and the same one you accused
Brandon of not reading. If there were supplemental materials, you
should have sent them. I am not a lawyer.
To Juan:
Yes. The best place for any license question about source code is, as
usual, the
You're right. Library's destructor was calling
a function that was returning an exception. That in
turn called terminate() killing the process.
Thank You for your help. Now I have CTest failing the
test as it is supposed to.
--
Artur Kedzierski
-Original Message-
From:
I was reading exactly the link you sent, and the same one you accused
Brandon of not reading. If there were supplemental materials, you
should have sent them. I am not a lawyer.
To be honest, the only compelling languages I've seen so far in this
discussion is lua and tcl. This is because they
Hi,
I am writing CTest unit tests for a library I've created.
I've utilized CREATE_TEST_SOURCELIST as described in Mastering CMake
book.
In one of the test, I pass an invalid value to make sure that an
exception is thrown.
In my test program I have a try-catch around the function
Sanchez, Juan wrote:
This part of the license would concern me. Are all files of interest,
by other authors, guaranteed to be BSD friendly?
Again, read LEGAL. You will then find that:
regex when used with Ruby it is Ruby licensed, based on Onigurama.
utils is BSD, credit going to Lucent
For interest, this topic has been brought up before.
http://public.kitware.com/pipermail/cmake-promote/2005-December/39.html
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Josef Karthauser wrote:
I guess what I want is an all/fast - to build all the targets in the
current directory, but nothing else.
Yes, please. So much easier than trying to figure out which targets need
to be built. (Especially since there is install/fast...)
--
Matthew
The time you have
On Nov 7, 2007 8:55 PM, Gonzalo Garramuño [EMAIL PROTECTED] wrote:
Sanchez, Juan wrote:
This part of the license would concern me. Are all files of interest,
by other authors, guaranteed to be BSD friendly?
Other files may use Perl's Artistic License.
That's the license I had read, that
Kedzierski, Artur CIV NSWC Corona, PA53 wrote:
Hi,
I am writing CTest unit tests for a library I've created.
I've utilized CREATE_TEST_SOURCELIST as described in Mastering CMake book.
In one of the test, I pass an invalid value to make sure that an
exception is thrown.
In my
53 matches
Mail list logo
