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 way?
Brandon Van Every wrote:
1) licenses that are unfriendly to unfettered commercial development,
often don't get accepted by commercial developers.
Not really.
cmake is a stand-alone utility. With any of the scripting language
licenses, you can still ship cmake with your own, say,
If you could build cmake with Debug (-g) it would be more helpful...
I do not see anything more with Debug (I set Debug in Build Type in
ccmake options)
Also, if you add -VV to ctest what are the last 100 lines of output?
100 lines won't be helpfull, there are just a list of tests results,
Bill Hoffman wrote:
So, I did look at how to fix this some. I have a c# program that can
force a running visual studio process to close and reload the solution
it has. The idea would be to have cmake run this when cmake is run as
part of the build. However, visual studio has a neat trick
On Nov 8, 2007 12:10 AM, Gonzalo Garramuño [EMAIL PROTECTED] wrote:
Anyway... why are you guys so concerned about cmake's license? To me,
as long as the code is open source and forkable, that's all I care for
cmake. I'm not planning to make money selling a fork of cmake, borrow
its source
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
Gonzalo Garramuño wrote:
3) Your license choices are fine for your own use, but you'd need to
talk to Kitware about what they actually want.
Now, that could be a fair point. If I was interested in having Kitware
distribute cmake with ruby. Which albeit I like the idea, I don't think
I
Baptiste Derongs wrote:
If you could build cmake with Debug (-g) it would be more helpful...
If it was debug mode we would have more information about the line
numbers in the stack. There are several += calls on strings in that
function, without knowing which one it is, I can not fix the
On 11/8/07, Bill Hoffman [EMAIL PROTECTED] wrote:
Gonzalo Garramuño wrote:
[...] Also, I am
not sure having N languages for CMake would be the best approach. So,
you go to build a project, and hey they are using CMake, cool, I know
how to run CMake, oh wait, that one is ruby CMake, I
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 .
In any file you use the Q_EXPORT_PLUGIN2 macro, you can put something like
this:
#if defined(NDEBUG)
# define QT_NO_DEBUG
#endif
at the top of the
Bill Hoffman wrote:
Baptiste Derongs wrote:
If you could build cmake with Debug (-g) it would be more helpful...
If it was debug mode we would have more information about the line
numbers in the stack. There are several += calls on strings in that
function, without knowing which one it
So, I am setting up a dashboard on a machine that was recently upgraded
to Leopard. If you upgrade the OS, but do not install the optional
Xcode tools that come on the Leopard disk, the compiler will not work.
The compiler will be there, but if you run it, you will get errors like
this:
On Thursday 08 November 2007, Mike Jackson wrote:
...
As a user of CMake let me second this notion also. CMake only depends
on a C++ compiler which is every where. Tying CMake to Ruby, Perl, tk
or anything else may actually decrease CMake's market penetration. I
don't really see Ruby running
[EMAIL PROTECTED] schrieb:
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 .
In any file you use the Q_EXPORT_PLUGIN2 macro, you can put something like
this:
#if defined(NDEBUG)
# define
Am Donnerstag 08 November 2007 00:18:43 schrieb Matthew McCormick:
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
On Wednesday 07 November 2007, Vitor Vasconcelos Araujo Silva wrote:
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).
Use CTest.
Alex
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Wyszomierski wrote:
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
)
Hey,
I am using CMake under Linux/MacOS X/Cygwin and lately with
Windows+Windows SDK (cmake -G NMake Makefiles)
On all platforms, I used to set a default myself to CMAKE_BUILD_TYPE if
the user did not.
Unfortunately, on Windows with NMake, CMAKE_BUILD_TYPE is set by cmake
to Debug. (A
On Nov 8, 2007 7:01 AM, Gonzalo Garramuño [EMAIL PROTECTED] wrote:
If cmake was a popular C library on the other hand... the type of OSI
licensing would indeed matter *much* more.
What if I just want to rip a chunk of code out of Ruby and reuse it
somewhere? I'll have the PITA of carrying the
http://lists.apple.com/archives/xcode-users/2007/OCt/msg00376.html
http://lists.apple.com/archives/xcode-users/2007/OCt/msg00400.html
Xcode 2.5 is also available.
developer.apple.com
--
Mike Jackson Senior Research Engineer
Innovative Management Technology Services
On Nov 8, 2007, at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Torsten Martinsen wrote:
I'm sure this is a FAQ, but I cannot find the answer anywhere.
Using VS 2003, given that I have a third-party library with debug and release
variants:
/path/to/lib/release/lib.lib
/path/to/lib/debug/lib.lib
21 matches
Mail list logo
