At 12:14 PM 10/16/2006, Luigi Calori wrote:
>I have the following problem:
>a master cmake project that wants to configure and build a series of slave
>cmake projects
>I' ve tried several hacking but not found an elegant solution.
>I' ve read from the list that the
>
>ctest --build-and-test
>
>
>c
At 07:19 PM 10/11/2006, Axel Roebel wrote:
>This is exactly what I do currently.
>I thought there would may be exist an easier way.
>I now see that my main problem is how I replace the compiler:
>
>I patch CMakeFiles/CMakeCCompiler.cmake
>from within CMakeLists.txt,
>while I probably should simply
At 05:11 PM 10/11/2006, Eran Guendelman wrote:
>Hi, we are trying to track down why cmake 2.4 is crashing when generating the
>VisualStudio 7 build files whereas cmake 2.2 worked fine. I built a debug
>version of cmake and narrowed it down to the following issue:
>
>In cmLocalGenerator::ComputeL
At 05:10 PM 10/11/2006, Warren Turkal wrote:
>On Wednesday 11 October 2006 12:52, Brad King wrote:
>> Mike Jackson wrote:
>> > BTW, when is the next release?
>>
>> When it's ready.
>
>Typical open source answer:-)
Unlike commercial software which always releases on fixed
and reliable schedule
At 12:29 PM 10/11/2006, Sean McBride wrote:
>
>Any ideas?
It is a bug in the Xcode generator happens with any version of Xcode.
I am working on a fix.
-Bill
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
At 04:56 PM 10/10/2006, Sean McBride wrote:
>Hi all,
>
>If I make just one change (CMAKE_GENERATOR from "Unix Makefiles" to
>"Xcode") CMake won't build, giving this error:
>
>-- Check for working C compiler: gcc
>-- Check for working C compiler: gcc -- broken
>CMake Error: Error in cmake code at
>/
At 05:57 AM 10/10/2006, John Biddiscombe wrote:
>Matthieu
>
>If you have qt3 and qt4 that is not in your path, it should all work if you do
>the following
>run ccmake, it will detect qt3, now set desired qt to 4, run ccmake again.
>some errors no doubt. Force cmake's qmake setting to point to
>/
At 05:43 AM 10/10/2006, Toni Cebrian wrote:
>Hello,
>
> I have a Sparc machine with Solaris 8 installed. I have locally installed
> GCC (/usr/local/bin) and mounted with NFS a disk with the compiler tools of
> Sun (/opt/studio11/SUNWspro/bin). The problem I have is that when I run
> ccmake I t
At 10:59 AM 10/9/2006, Matthieu Brucher wrote:
>The assumption made is that your environment is set up correctly to build the
>qt version you
>want to use. This means that the correct qmake should be in your PATH. If
>you type
>which qmake, that is the one cmake will pick.
>
>-Bill
>
>
>My env
At 10:25 AM 10/9/2006, Matthieu Brucher wrote:
>Hi,
>
>I have another problem with the selection of Qt4. I try to use
>FIND_PACKAGE(Qt4) on a Linux because everything was fine on Windows. When
>searching in this package, my version of cmake - the one on Fedora Core 5 that
>does not have the Find
At 05:39 AM 10/5/2006, Xavier Delannoy wrote:
>it's working fine. I have moved
>SET(CMAKE_INSTALL_PREFIX "$ENV{DESTDIRPREFIX}")
>to the root CMakeLists.txt
>
>(- CMakelists.txt
> |--static
>|-- CMakeLists.txt
> |--shared
>|-- CMakeLists.txt
>
>if SET(CMAKE_INSTALL_PREFIX "$
At 06:58 AM 10/5/2006, frederic heem wrote:
>Hi,
>After upgrading from cmake 2.4.3 to cmake in cvs, cmake aborts because the
>macro QT4_ADD_DBUS_INTERFACE. Indeed, FindQt4.cmake was downloaded from the
>kde project and the FindQt4.cmake from cvs does not contain this macro.
>Basically, all Find
At 09:19 AM 10/4/2006, Alexander Neundorf wrote:
>> I have just checked in a fix for this. It now looks for qmake,
>> and checks to see if the qmake is the right version, if it is from
>> qt3, then it will look for qmake-qt4.
>
>This sounds really good
>
I found a problem with it this morning
At 02:51 AM 10/4/2006, Michael G. Hansen wrote:
>Hi,
>
>I have two suggestions for FindQt4.cmake:
>
>1. FindQt4 looks for qmake before qmake-qt4. I think the other way
>around would be better, because FindQt4 fails if it finds qmake and then
>finds out that it is from QT3, without looking at the po
At 06:45 AM 10/4/2006, Eric Noulard wrote:
>In my project I have a library
>
>ADD_LIBRARY(tsp_ascii_writer ${ASCII_WRITER_LIB_SRC})
>
>and an executable with the same name
>
>ADD_EXECUTABLE(tsp_ascii_writer ${ASCII_WRITER_SRC})
The target names must be different.
However you can use the target pro
At 04:27 AM 10/4/2006, frederic heem wrote:
>Hi,
>An very simple CMakeLists.txt has been written to show to problem:
>
>include_directories("-I/bar")
That is the problem. include_directories does not take a -I,
the compiler may use some other flag, you just have to give
it the directory with no
At 12:28 PM 10/3/2006, frederic heem wrote:
>foreach(PACKAGE ${PACKAGELIST})
>find_package(${PACKAGE})
>message(${PACKAGE}_FOUND)
>if (${PACKAGE}_FOUND)
>include_directories(${${PACKAGE}_INCLUDE_DIR})
>set(dumpcap_LIBS ${dumpcap_LIBS} ${${PACK
At 03:00 AM 10/1/2006, Andrey Rahmatullin wrote:
>On Sat, Sep 30, 2006 at 08:34:58AM -0700, Alan W. Irwin wrote:
>> However, libltdl does not solve the issue of how to dynamically load
>> plug-ins on windows systems.
>SIM always used libltdl on all platforms without problems (until we
>switched to
At 08:08 AM 9/17/2006, Yuan, Jue wrote:
>Hi all,
>
>I am the maintainer of kdesvn for FreeBSD. As kdesvn has changed its
>make system to CMake, I think it is time to change the port of kdesvn
>according to this. I'm not familiar with CMake before, and I end up
>with some errors when trying to apply
At 08:53 PM 9/14/2006, Sonali Barua wrote:
>Hello,
>
>I am facing a problem in my CMakeLists.txt file. I would like to add several
>ITK files in a folder that consitutes a library that isn't yet part of the
>original ITK library using cmake. What are the commands that I have to use so
>that my s
At 05:34 AM 9/15/2006, Johan Seland wrote:
>Hello.
>
>I have been a happy user of CMake for the last couple of monts (both
>on Linux and using MinGW on WinXP), but have currently run into an
>annoying problem.
>
>I have to do a project using DirectX and need to link with GDI32,
>WINMM and D3D9.
>I
At 02:49 PM 9/14/2006, Wojciech Jarosz wrote:
>Thanks for the tip. I figured it had to do with my ignorance of how dlls work
>on Windows.
>
>Is there a way to automate this process within the CMake framework? Meaning,
>I'd like everything to be exported on Windows so that it matches the behavio
At 12:07 AM 9/14/2006, Wojciech Jarosz wrote:
>Hi,
>I have been using CMake on Linux and Mac OS X for a couple months now and am
>very happy with it. Now I am having a bit of trouble getting my project to
>work on windows using VC++ Express Edition.
>
>Among other things, my project has two (shar
At 06:27 PM 9/11/2006, Brandon J. Van Every wrote:
>I'm making a casual effort to build the G3D library, which has CMake support
>under development. It contains:
>INCLUDE (FindSDL)
>FIND_PACKAGE(SDL REQUIRED)
>
>I have SDL binaries for VS7.1 on my system in E:\devel\vs71\SDL-1.2.11.
>CMakeSetup
At 10:14 AM 9/12/2006, Thangaraj Umapathy wrote:
>Hi All,
>
>I am new to CMake. I want know how to convert my
>existing XCode project into CMake. Is there any way in
>CMake to do this job? If yes, can you please tell me
>the way?
There is no automatic way. You have to write CMakeLists.txt files
At 02:09 PM 9/11/2006, Warren Turkal wrote:
>On Monday 11 September 2006 07:49, William A. Hoffman wrote:
>> At 09:32 AM 9/11/2006, Brad King wrote:
>> We could try something like this:
>> http://directory.fsf.org/MCPP.html
>
>Here's something that may be b
At 09:32 AM 9/11/2006, Brad King wrote:
>William A. Hoffman wrote:
>> At 03:20 PM 9/8/2006, Warren Turkal wrote:
>>> On Friday 08 September 2006 13:11, you wrote:
>>>> #ifdef FOO
>>>> use abc
>>>> #else
>>>> use xyz
>>>>
At 04:33 PM 9/8/2006, Alexander Neundorf wrote:
>How should all that work when cross-compiling ?
>The FindFoo.cmake files as far as I can see cannot and are not written to find
>libraries in strange directories for cross-compiling.
>All the values could be set manually by hand, but this is not re
At 04:06 PM 9/8/2006, [EMAIL PROTECTED] wrote:
>
>
>
>-Original Message-
>From: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Sent: Fri, 8 Sep 2006 4:06 PM
>Subject: Re: [CMake] Adding cross-compiler support to CMake ...
>
>lol, I actually intended to try cross-compiling KDE as a demostratio
At 03:20 PM 9/8/2006, Warren Turkal wrote:
>On Friday 08 September 2006 13:11, you wrote:
>> #ifdef FOO
>> use abc
>> #else
>> use xyz
>> #endif
>
>That's exactly the type of thing causing the problems.
Brad, how hard do you think it would be to run the fortran stuff
through cpp with the same -I a
At 03:02 PM 9/8/2006, Alan W. Irwin wrote:
>On 2006-09-08 13:59-0400 William A. Hoffman wrote:
>
>>As a CMake developer I think it would be much easier to do it with
>>two makefiles. As far as I can tell there are two modes of cross compiling.
>>
>>1. The whole p
Warren, is code like this causing your trouble:
#ifdef FOO
use abc
#else
use xyz
#endif
Or is it something else?
-Bill
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
At 12:28 PM 9/8/2006, Michael Casadevall wrote:
>Hrm, interesting idea, I admit that it didn't occur to me, although I
>don't see how it really is that different. In your case, you simply
>setting the same variables twice for local and cross-compilation,
>which seems a little kludgy. I mean,
At 11:03 AM 9/8/2006, Benjamin Reed wrote:
>On 9/6/06, Brandon J. Van Every <[EMAIL PROTECTED]> wrote:
>
>I don't know if this is what he meant, but at least as far as
>universal binaries are concerned, TRY_COMPILE *can* cause issues.
>
>For example, there are a number of autotool'd things that I h
At 02:39 AM 9/8/2006, Michael Casadevall wrote:
>I've been working on determining on how to do the platform part of this. My
>first guess is we could do something like this in the platform files:
>
>(from gcc.cmake)
>IF(CMAKE_COMPILER_IS_GNUCC)
> SET (CMAKE_C_FLAGS_INIT "")
> SET (CMAKE_C_FLAGS_
At 06:42 PM 9/7/2006, Michael Casadevall wrote:
>1. Never seen that. autotools should only enter cross-compiling mode
>if --host is set, and its different the current platform, or if both
>build and host are set with different values.
If you look in a configure script..
rm -f a.out a.exe conft
At 04:36 PM 9/7/2006, Brad King wrote:
>Michael Casadevall wrote:
>> I wish to add support for cross-compiling to CMake since its a tool I
>> use a lot, and I can finally kill the last few of my projects using
>> autotools. To my knowledge, autotools is the only system that provides
>> cross-compil
At 05:36 PM 9/6/2006, Anton Deguet wrote:
>Hello,
>
>I have found that using EXEC_PROGRAM with ${CMAKE_COMMAND} -E I can
>write/remove a key in the Windows registry but I haven't figured out how
>to read a key. Is there a simple solution for that?
Sure, but it seems not to be documented
Sev
At 06:09 PM 9/6/2006, Richard Fuchs wrote:
>I need to set an environment variable so I'm doing this:
>
>SET(ENV{ACE_ROOT} "/work/secore-dev/secore/external/ACE_TAO/ACE_wrappers/ace")
>
>but after cmake is run and the Makefiles are generated, I do an env and the
>environment variable ACE_ROOT is n
At 03:55 PM 9/6/2006, Brandon J. Van Every wrote:
>Michael Casadevall wrote:
>>>
>>>My intent here is not to start a flamewar between autotools and cmake, In
>>>some cases, autotools is the proper tool vs cmake due to cross-compiling
>>>(which will hopefully fixed) and the fact that you need the
At 07:25 PM 9/5/2006, Alan W. Irwin wrote:
>On 2006-09-05 14:45-0700 Russell L. Carter wrote:
>
>>Greetings,
>>I am new to cmake and am encountering this error when
>>I try to build a trivial Fortran library:
>>
>>[EMAIL PROTECTED] [216] make
>>Scanning dependencies of target hwode
>>make[2]: *** N
At 09:21 AM 8/31/2006, Jon Trauntvein wrote:
>I have been successfully using cmake to build projects on non-windows
>platforms (Linux) but have been using visual studio projects to build
>these under windows basically because these projects already existed. I
>have been so pleased with the results
You can always just set the environment variables:
FC == path to comiler
FFLAGS == options for the compiler
Then run cmake on a clean build tree, and it should use those values.
-Bill
At 06:13 AM 8/31/2006, Arjen Markus wrote:
>Hello,
>
>some further information on Fortran compilers:
>I have
I would like to create some sort of process for getting modules in to
CMake releases. At that point, the modules should conform to the CMake
BSD license. I don't want inconsistent licenses in the CMake release
tree.
However, licensing aside, there needs to be some sort of process for
gettin
At 01:51 PM 8/30/2006, Richard Fuchs wrote:
>William A. Hoffman wrote:
>>At 11:06 AM 8/30/2006, Richard Fuchs wrote:
>>
>>>I want to be able to create my libraries in a different directory instead of
>>>the current_bin_dir
>>>
>>
At 11:06 AM 8/30/2006, Richard Fuchs wrote:
>I want to be able to create my libraries in a different directory instead of
>the current_bin_dir
>
>For example:
>ADD_LIBRARY(serialize SHARED ${SERIALIZE_SRCS})
>creates current_bin_dir/libserialize.so
>
>But if I try:
>ADD_LIBRARY(/all_my_lib_files/s
At 10:47 AM 8/30/2006, Xavier Larrode wrote:
>Actually i don't have the sources of the generator, it's another library wich
>is doing that, so i can't make a new target.
>SO i did an EXEC_PROGRAM to generate it before scanning files, but i don't
>know how to generate it after a make clean wich ha
At 07:35 PM 8/29/2006, Eric Noulard wrote:
>Could you tell me why we could not TRY_RUN even if
>CC and CMAKE_C_FLAGS
>have been "overloaded"?
If you are cross compiling, you can not run sample code because it will
not be compiled for the host machine.
The basic idea for cross compiling with cmake
l of that information is potentially wrong.
>William A. Hoffman writes:
>>At 09:46 PM 8/27/2006, [EMAIL PROTECTED] wrote:
>>>I am (trying to) migrate from jam+msvcgen to cmake for projectfile
>>>autogeneration. Previously, I ran jam msvcgen to autogenerate all
>>>
At 09:46 PM 8/27/2006, [EMAIL PROTECTED] wrote:
>I am (trying to) migrate from jam+msvcgen to cmake for projectfile
>autogeneration. Previously, I ran jam msvcgen to autogenerate all
>projectfiles, and then those *.vcproj,*.sln,*.dsw,*.dsp got distributed. So
>developers could use the distribute
At 05:13 PM 8/27/2006, Alan W. Irwin wrote:
>On 2006-08-27 16:30-0400 William A. Hoffman wrote:
>
>>At 12:00 PM 8/27/2006, Steve Johns wrote:
>>>Michael Bell wrote:
>>>>>ADD_CUSTOM_TARGET(makeExecutable ALL)
>>>>>FOREACH(file ${SCRIPTS})
>&
At 12:00 PM 8/27/2006, Steve Johns wrote:
>Michael Bell wrote:
>>>ADD_CUSTOM_TARGET(makeExecutable ALL)
>>>FOREACH(file ${SCRIPTS})
>>> CONFIGURE_FILE(${CMAKE_CURRENT_SOURCE_DIR}/${file}
>>> ${EXECUTABLE_OUTPUT_PATH}/../${file}
>>> @ONLY)
>>> ADD_CUSTOM_COMMAND(
>>> TARGET mak
At 09:06 PM 8/20/2006, Jamie Jones wrote:
>On Sun, 2006-08-20 at 11:10 -0400, William A. Hoffman wrote:
>
>> >The "magic" build script for Win32 contain this fragment of the build
>> >line for MSVC
>> >
>> >/DEF:"./../../engine
So, the problem was that some Unix shells were having trouble with long
command lines. So, we made it a cmake script to do the linking. I
forgot that folks used back tic commands to run pkconfig. However, that
is a bad thing to do anywayIt does not work with Xcode projects,
it does not
At 09:53 AM 8/20/2006, Jamie Jones wrote:
>G'day List,
>
>I've been happily cmakifing my opensource project and after a good
>success on *NIX (Yay! no more autotools) have run into a snag.
>
>We use a plugin system where our main binary loads a plugin eg an opengl
>renderer. On *NIX this is fine be
Please post the call you used for RENAME.
At 03:45 AM 8/19/2006, Thomas Arcila wrote:
>Hi,
>
>I've just found a bug. Documentation states that RENAME is allowed for
>PROGRAMS
>while it's actually refused by CMake.
>I've made my way making the renaming before the installation
>(using CONFIGURE_F
At 04:47 PM 8/17/2006, James Bigler wrote:
>I'm trying to implement the stuff found in
>
>http://www.cmake.org/Bug/bug.php?op=show&bugid=1731
>http://www.cmake.org/Bug/bug.php?op=show&bugid=2172
>http://www.cmake.org/pipermail/cmake/2005-August/007102.html
>http://www.itk.org/cgi-bin/viewcvs.cgi/Wr
At 01:40 PM 8/17/2006, Ryan Connelly wrote:
>I agree. Unfortunately, I already purchased 2.2 :(. Maybe I can get a reduced
>price on the new one when it comes out?
>
>Ryan
>
>Crni Gorac wrote:
>>Any plans regarding updating "Mastering CMake" book to
>>version 2.4? Am going to purchase, but would
At 10:17 AM 8/17/2006, [EMAIL PROTECTED] wrote:
>---- "William A. Hoffman" <[EMAIL PROTECTED]> wrote:
>> OK, I am going to revert my changes. It causes the lex to go
>> into an infinite loop and I don't have time to track it down now.
>>
>> -B
Looks like a new problem. CPack with compress seems to be not
working on your system for some reason.
-Bill
At 03:15 PM 8/16/2006, Louis Kruger wrote:
>On Wednesday 16 August 2006 18:09, you wrote:
>> The changelog is not updated each night.
>> If you do a new cvs update, this problem is fixed.
At 12:58 PM 8/15/2006, [EMAIL PROTECTED] wrote:
>---- "William A. Hoffman" <[EMAIL PROTECTED]> wrote:
>>
>> Will the change I just checked into CVS work for you?
>>
>> -Bill
>>
>
>Yeah, sorry I wrote my email before seeing that you had co
What version of cmake is this?
Try a cvs update, and see if it fixes the problem.
I recently fixed this test failure.
-Bill
At 11:05 AM 8/16/2006, Louis Kruger wrote:
>On Wednesday 16 August 2006 16:10, you wrote:
>> bin/ctest -V -R SimpleInst
>Produces:
>
> Add coverage exclude regular expressi
At 01:09 PM 8/15/2006, Scott Amort wrote:
>Hello,
>
>I am attempting to emulate the autotools `make check' behaviour in my
>CMake project. I currently have a testing framework setup and working
>using ENABLE_TESTING() and CTest, however, it has two drawbacks (from my
>perspective, anyways ;-) ).
>
At 03:21 PM 8/14/2006, Jorge Rodriguez wrote:
>2) Is there anything like:
>
>IF(WIN64)
> MESSAGE("Win 64!")
>ENDIF(WIN64)
>
>I notice that on a 64 bit build machine with a 64 bit compiler, this does not
>print the message, but IF(WIN32) works fine. (Which is good, because I have
>alot of IF(WIN
At 11:48 AM 8/15/2006, [EMAIL PROTECTED] wrote:
> Brad King <[EMAIL PROTECTED]> wrote:
>>
>> FYI, there is a bug report for this problem:
>>
>> http://www.cmake.org/Bug/bug.php?op=show&bugid=3109
>>
>> I briefly looked at fixing it but got stuck on the free-format versus
>> fixed-format pa
At 02:44 AM 8/15/2006, Arjen Markus wrote:
>> worked out?
>
>Please reduce that to:
>
>^[cC*].*\n { return EOSTMT; }
>
>and you will not miss any dependencies as far as I can tell.
>
>(I was wondering about false positives, like when you have
>"INCLUDE 'filename'" or "USE module" in a literal strin
At 09:53 PM 8/14/2006, Alan W. Irwin wrote:
>An even easier solution (as proposed by Bill Hoffman) is for CMake to parse
>fortran files ignoring all distinctions between fixed and free format (so
>that any line starting with [cC*dD] is automatically skipped even though it
>is not a comment for the
At 04:23 PM 8/14/2006, Brandon J. Van Every wrote:
>Bill Hoffman wrote:
>>So, with cmake you can use "Unix Makefiles" to build with the microsoft
>>compiler cl.
>
>Holy build permutations Batman! Neat trick though this may be, it's small
>wonder I've stuck with a policy of keeping "usual tools
At 10:41 AM 8/14/2006, Christian Lang wrote:
>Hello,
>
>I tried it, but it did not work either ...
>
>>Try putting the ${DATE} inside the quotes...
>>
>>Christian Lang wrote:
>>
>>>Hello,
>>>
>>>I want to add some custom install code via INSTALL(CODE ). How can I
>>>set variables inside such a INS
At 11:05 AM 8/14/2006, Arjen Markus wrote:
Can we just have the rule for both? Basically, anything after a c should
be a comment?
If it is old fixed format fortran it won't have modules anyway, and should
have no depends.
So, if it finds too many comments because of a stray
At 10:43 AM 8/14/2006, Arjen Markus wrote:
>William A. Hoffman wrote:
>
>>Can we just have the rule for both? Basically, anything after a c should be
>>a comment?
>>If it is old fixed format fortran it won't have modules anyway, and should
>>have no depends.
At 02:37 AM 8/14/2006, Arjen Markus wrote:
>[EMAIL PROTECTED] wrote:
>
>>Hi Alan,
>>
>>My knowledgebase of fortran lies with fixed format f77 fortran, so your right
>>the solution below only works for fixed format Fortran. There is currently
>>nothing in the .l file to set the state, so the li
At 03:18 PM 8/11/2006, Abe Stephens wrote:
>Thanks for your directions, I'm experiencing one problem however:
>
>I can't seem to communicate a variable from my project configure (which
>contains the ADD_CUSTOM_COMMAND) to the invocation of myscript.cmake.
>
>The command below is:
>
>COMMAND ${CMAK
See Modules/Platform/Windows.cmake.
There is some stuff you can un-comment out.
# uncomment these out to debug nmake and borland makefiles
#SET(CMAKE_START_TEMP_FILE "")
#SET(CMAKE_END_TEMP_FILE "")
#SET(CMAKE_VERBOSE_MAKEFILE 1)
The problem is it might cause the command line to be too long an
>When I run ccmake and set CMAKE_Fortran_Compiler to ifort or ${Install
>Path}/ifort and then configure CMAKE_Fortran_Compiler resets back to the gnu
>compiler /usr/bin/f95. I don't understand why this is happening. Any ideas?
>
>I'm running on FC4, with CMAKE 2.4.3. Running ifort from the
At 06:54 AM 8/10/2006, Brandon J. Van Every wrote:
>William A. Hoffman wrote:
>>
>>CMake relys on a correctly installed compiler. If you can create a simple
>>project with the VS GUI,
>>and it works, and CMake does not, then it is CMake's fault. If you create
At 09:14 PM 8/9/2006, Brandon J. Van Every wrote:
>William A. Hoffman wrote:
>
>The bad appearance probably doesn't happen so much in practice with VS .NET
>2003, because people typically install a Platform SDK somewhere along the way,
>for whatever reason they need it
At 07:26 PM 8/9/2006, Matt Rogers wrote:
>Hi,
>
>Would the CMake developers be interested in patches that allows people to use
>their already installed libraries such as curl, expat, libtar, etc. on
>certain platforms and fallback to the in-source libraries if they're not
>installed?
>
>Initiall
At 02:31 PM 8/9/2006, Tim Teulings wrote:
>Hello!
>
>I try to use the CHECK_TYPE_SIZE macro in the CheckTypeSize module to
>detect the availability and the size of wchar_t.
>
>Since wchar_t is not a build-in type but is defined in I want
>the macro to include before calculating the size.
>
>I tri
At 06:25 PM 8/8/2006, Anton Deguet wrote:
>Brad,
>
>Thank you for your reply. I finally had a chance to try it and I must
>admit that I only have a partial success to report. The main issue I
>have is that I am using a custom command (post build) to generate the
>list of test cases used by CTest
At 08:23 AM 8/8/2006, William A. Hoffman wrote:
>At 02:53 AM 8/8/2006, Arjen Markus wrote:
>>Hello,
>>
>>as one of the maintainers of the PLplot package I have been
>>experimenting with CMake on Windows. I used the pre-built
>>stable Windows version (downloaded
At 02:53 AM 8/8/2006, Arjen Markus wrote:
>Hello,
>
>as one of the maintainers of the PLplot package I have been
>experimenting with CMake on Windows. I used the pre-built
>stable Windows version (downloaded it last week).
>
>When I start CMake and ask it to build the project files
>for MSVC++ 6.0,
At 05:57 AM 8/8/2006, Christian Ehrlicher wrote:
>Hi,
>
>I've set my LIBRARY_OUTPUT_PATH to
>SET(LIBRARY_OUTPUT_PATH ${CMAKE_BINARY_DIR}/${CMAKE_BUILD_TYPE}/plugins)
>to distinct between debug and release build on win32. This works fine with
>nmake makefiles but fails with vcproj. The output path
bstdc++ should automatically be added at the linking step.
>When libstc++ is not linked, the resulting run-time error message was
>difficult to debug, to say the least.
>
>thanks,
>michael
>
>On 8/7/06, William A. Hoffman <[EMAIL PROTECTED]> wrote:
>>I think that t
At 11:52 AM 8/7/2006, Anders Sundman wrote:
>What is the rationale for this design desision? It seems to me that this
>feature introduces an unnecessary dependency? It's not realy a big issue
>for me, but I'm curious.
Most of the time it is a necessary dependency. Especially in the case
of link
At 10:38 AM 8/7/2006, Fu Limin wrote:
>Thank you for the hint!
> From the log file, I find out the problem is due to an error in determing
> pthread library, it used -lpthreads flag to link the testing code. I don't
> understand why it does not use -lpthread without s. I guess this testing is
>
I think that the problem was sun was shipping with a gcc that did not have
a shared stdc++, so if you created shared libraries with g++ they did not link.
-Bill
At 10:36 AM 8/7/2006, Michael Bell wrote:
>Hi,
>
>When compiling ITK2.8 on Solaris 5.9 with gcc 3.3.1, files are being
>compiled correc
At 07:02 AM 8/7/2006, Fu Limin wrote:
>Hi,
>
>I am trying to use cmake as the building system for my project which may
>use many different libraries. I only have one day experience with it
>:-), so far everything works fine except that a sub-project using Qt4
>can not be built. The problem is when
At 03:13 AM 8/7/2006, Anders Sundman wrote:
>> At 04:08 AM 8/4/2006, Anders Sundman wrote:
>>>Shouldn't the line:
>>>-> C:\MinGW\bin\g++.exe-shared -o liba.dll
>>> -Wl,--out-implib,liba.dll.a "CMakeFiles/a.dir/a.obj" -lb
>>>
>>>also contain a -L switch since I have the line
>>> "LINK_DIRECTORIE
At 12:48 PM 8/6/2006, Daniel J. Hilferty wrote:
>Would including the source increase compile time with CMake? Since these
>libraries should only need to be built once, I would hate to recompile them
>every time I build the library.
The .o files for the libraries would be compiled once, it would
At 05:39 PM 8/6/2006, Craig Bradney wrote:
>Hi,
>
>I'm wondering if theres any known issues with dependencies when running the
>make stage where you use make -jN (I'm using N=3 on a core duo) and moc is
>not occurring before the resulting files are required? Source is current
>Scribus 1.3.4cvs,
At 10:19 AM 8/6/2006, Daniel J. Hilferty wrote:
> Currently, we support Windows, Linux and OS X. We are hoping that CMake
> would allow us to support MinGW as well. For Windows builds - because these
> libraries are not standard, we do actually include the code for zlib, IJG
> (jpeg) and p
At 01:28 AM 8/6/2006, Daniel J. Hilferty wrote:
>William A. Hoffman wrote:
>>At 07:31 PM 8/5/2006, Daniel J. Hilferty wrote:
>>
>>>After reading the FAQ, I found that what I actually wanted to create is a
>>>convenience library -- which is not yet supported
At 07:31 PM 8/5/2006, Daniel J. Hilferty wrote:
>After reading the FAQ, I found that what I actually wanted to create is a
>convenience library -- which is not yet supported by CMake. The FAQ led me to
>believe that there is no future plans to support this feature. Has anyone
>hear differently
At 04:08 AM 8/4/2006, Anders Sundman wrote:
>Shouldn't the line:
>-> C:\MinGW\bin\g++.exe-shared -o liba.dll -Wl,--out-implib,liba.dll.a
>"CMakeFiles/a.dir/a.obj" -lb
>
>also contain a -L switch since I have the line
>"LINK_DIRECTORIES(${TEST_SOURCE_DIR}/b)" in the cmake file for the "a"-lib?
At 05:20 PM 8/3/2006, Anders Sundman wrote:
>Hi all!
>
>I'm new to cmake and I'm currently trying to get the hang of how it works.
>Unfortunately, I'm stuck with a simple (?) problem that I can't seem to
>work out. Any help will be much appreciated.
>
>I have created a minimal (OS X) example to d
At 03:33 AM 8/3/2006, Sylvain Benner wrote:
>Hello,
>
>I've read that there was an initial attempt but it seems that it is not on the
>CVS anymore.
>In the changelog it says :
>
>2005-03-02 10:58 martink
>* Source/: cmGlobalCodeWarriorGenerator.cxx,
>cmGlobalCodeWarriorGenerator.h, cmLocalCodeW
At 03:59 AM 8/3/2006, Christian Ehrlicher wrote:
>Hi,
>
>One more small problem:
>
>if(NOT WIN32)
>MESSAGE(STATUS "if(NOT WIN32)")
>set(tmp "test")
>if(${tmp} STREQUAL "test")
>MESSAGE(STATUS "match")
>else(${tmp} STREQUAL "test")
>MESSAGE(STATUS "no match")
>end
At 02:21 AM 8/3/2006, Jan Woetzel wrote:
>Christian Ehrlicher wrote:
>
>>SET(myproject_SRCS
>> myproject.cpp
>> myproject.jisp
>>)
>>
>>ADD_LIBRARY(myproject SHARED ${_myproject})
>>
>>myproject.jisp.rule is created and executed correct, but myproject.jisp
>>doesn't have 'Custom build
CMake 2.4.3-1 is now available on Cygwin mirrors.
There has been a new release of the official cmake (2.4.3-1).
This is a minor release from 2.4.2-1 to 2.4.3-1
Changes in CMake 2.4.3
* fix for 3557 - Under MSVC8 hardcoded TargetEnvironment for MIDL Compiler
* Fix for Xcode all projects to prev
1 - 100 of 438 matches
Mail list logo
