[CMake] cmake ./configure hangs after "Check for working C compiler: /usr/bin/cc "

I'm trying to build cmake on Mac OS 10.5.5, using XCode 3.1.1, gcc 4.0.1 I've tried building cmake 2.6.2, and cmake from cvs, as of 2:30 GMT, 11/26/2008. While running './configure' for either version, it hangs after the message: Check for working C compiler: /usr/bin/cc 'ps' shows /User

Re: [CMake] INCLUDE_DIRECTORIES in sub-directories doesn't work?

Okay, I tried it out just to make sure. It includes the foo directory for both main.c and foo/bar.c. I only want it for foo/bar.c (and any other file in foo/). On Tue, Nov 25, 2008 at 3:10 PM, Sean Soria <[EMAIL PROTECTED]> wrote: > That would add the included directories to every source in the

Re: [CMake] INCLUDE_DIRECTORIES in sub-directories doesn't work?

I think you hit send too early. On Tue, Nov 25, 2008 at 3:41 PM, THE HIGHHAT <[EMAIL PROTECTED]> wrote: > On Tue, Nov 25, 2008 at 4:10 PM, Sean Soria <[EMAIL PROTECTED]> wrote: >> That would add the included directories to every source in the >> project. I want it included _only_ for the foo dire

Re: [CMake] INCLUDE_DIRECTORIES in sub-directories doesn't work?

On Tue, Nov 25, 2008 at 4:10 PM, Sean Soria <[EMAIL PROTECTED]> wrote: > That would add the included directories to every source in the > project. I want it included _only_ for the foo directory. Not necessarily. This would those headers files associated with main.c. The ___

Re: [CMake] INCLUDE_DIRECTORIES in sub-directories doesn't work?

That would add the included directories to every source in the project. I want it included _only_ for the foo directory. On Tue, Nov 25, 2008 at 2:59 PM, THE HIGHHAT <[EMAIL PROTECTED]> wrote: > On Tue, Nov 25, 2008 at 3:43 PM, Sean Soria <[EMAIL PROTECTED]> wrote: >> No, this doesn't work either

Re: [CMake] INCLUDE_DIRECTORIES in sub-directories doesn't work?

On Tue, Nov 25, 2008 at 3:43 PM, Sean Soria <[EMAIL PROTECTED]> wrote: > No, this doesn't work either: > CMakeLists.txt: > ADD_SUBDIRECTORY(foo) > ADD_EXECUTABLE(hello main.c foo/main.c) > > foo/CMakeLists.txt: > SET_PROPERTY(SOURCE main.c PROPERTY INCLUDE_DIRECTORIES > ${CMAKE_CURRENT_SOURCE_DIR})

[CMake] Unicode in Visual Studio projects

Hi, I noticed when I run CMake for Visual Studio 9 2008 it sets my project to "Multibyte Character Set" instead of Unicode. Is there a way to force CMake to set the "Character Set" option to "Use Unicode Character Set"? ___ CMake mailing list CMake@cmake

Re: [CMake] INCLUDE_DIRECTORIES in sub-directories doesn't work?

No, this doesn't work either: CMakeLists.txt: ADD_SUBDIRECTORY(foo) ADD_EXECUTABLE(hello main.c foo/main.c) foo/CMakeLists.txt: SET_PROPERTY(SOURCE main.c PROPERTY INCLUDE_DIRECTORIES ${CMAKE_CURRENT_SOURCE_DIR}) On Tue, Nov 25, 2008 at 2:26 PM, Sean Soria <[EMAIL PROTECTED]> wrote: > Include doe

Re: [CMake] INCLUDE_DIRECTORIES in sub-directories doesn't work?

Include doesn't seem to do what I would expect either. I want to add include directories for any files found in foo. it seems include_directories doesn't do it because there must be a target in that directory. would setting the source property do it? On Tue, Nov 25, 2008 at 2:10 PM, Bill Hoffma

Re: [CMake] How to specify library dependencies?

On Nov 25, 2008, at 5:18 PM, Robert Dailey wrote: On Tue, Nov 25, 2008 at 4:09 PM, Robert Dailey <[EMAIL PROTECTED]> wrote: On Mon, Nov 24, 2008 at 4:39 PM, Michael Jackson <[EMAIL PROTECTED] > wrote: One of the better sources to look at is FindBoost.cmake: Here are some CMake Predefined va

Re: [CMake] How to specify library dependencies?

On Nov 25, 2008, at 5:09 PM, Robert Dailey wrote: On Mon, Nov 24, 2008 at 4:39 PM, Michael Jackson <[EMAIL PROTECTED] > wrote: One of the better sources to look at is FindBoost.cmake: Here are some CMake Predefined variables that you will find useful: APPLE CYGWIN MSVC UNIX WIN32 You can use

Re: [CMake] How to specify library dependencies?

On Tue, Nov 25, 2008 at 4:09 PM, Robert Dailey <[EMAIL PROTECTED]> wrote: > On Mon, Nov 24, 2008 at 4:39 PM, Michael Jackson < > [EMAIL PROTECTED]> wrote: > >> One of the better sources to look at is FindBoost.cmake: >> >> Here are some CMake Predefined variables that you will find useful: >> APPL

Re: [CMake] INCLUDE_DIRECTORIES in sub-directories doesn't work?

Sean Soria wrote: I had them switched originally and just double checked. This also doesn't work: CMakeLists.txt: ADD_SUBDIRECTORY(foo) ADD_EXECUTABLE(hello main.c foo/main.c) foo/CMakeLists.txt: INCLUDE_DIRECTORIES(${CMAKE_CURRENT_SOURCE_DIR}) The problem is the add_subdirectory. Although

Re: [CMake] How to specify library dependencies?

On Mon, Nov 24, 2008 at 4:39 PM, Michael Jackson < [EMAIL PROTECTED]> wrote: > One of the better sources to look at is FindBoost.cmake: > > Here are some CMake Predefined variables that you will find useful: > APPLE > CYGWIN > MSVC > UNIX > WIN32 > > You can use the cmake --help-variable [variable

Re: [CMake] INCLUDE_DIRECTORIES in sub-directories doesn't work?

I had them switched originally and just double checked. This also doesn't work: CMakeLists.txt: ADD_SUBDIRECTORY(foo) ADD_EXECUTABLE(hello main.c foo/main.c) foo/CMakeLists.txt: INCLUDE_DIRECTORIES(${CMAKE_CURRENT_SOURCE_DIR}) On Tue, Nov 25, 2008 at 1:54 PM, Bill Hoffman <[EMAIL PROTECTED]> wro

Re: [CMake] INCLUDE_DIRECTORIES in sub-directories doesn't work?

Sean Soria wrote: CMakeLists.txt: ADD_EXECUTABLE(hello main.c foo/main.c) ADD_SUBDIRECTORY(foo) foo/CMakeLists.txt: INCLUDE_DIRECTORIES(${CMAKE_CURRENT_SOURCE_DIR}) It is order dependent. So, the include_directory will not affect the hello target because it comes after it. -Bill

Re: [CMake] INCLUDE_DIRECTORIES in sub-directories doesn't work?

CMakeLists.txt: ADD_EXECUTABLE(hello main.c foo/main.c) ADD_SUBDIRECTORY(foo) foo/CMakeLists.txt: INCLUDE_DIRECTORIES(${CMAKE_CURRENT_SOURCE_DIR}) main.c files are empty because this is just a test of checking the compile line. On Tue, Nov 25, 2008 at 1:31 PM, Bill Hoffman <[EMAIL PROTECTED]> wr

Re: [CMake] INCLUDE_DIRECTORIES in sub-directories doesn't work?

Sean Soria wrote: I wouldn't expect that to work since I can see that it got the memo to include that directory but just doesn't do it. But I tried it out by using INCLUDE_DIRECTORIES(${CMAKE_CURRENT_SOURCE_DIR}) and I got the same bad results. That should work, if you could provide a small e

Re: [CMake] Default parameters in macros

On Nov 25, 2008, at 11:40 AM, Robert Dailey wrote: Hi, Are all macro parameters optional by default? If not, how can I make them optional? I have a couple of required parameters and a few optional ones. Thanks. Here is some code from Boosts CMake files: == START BOOST CMAKE COD

Re: [CMake] INCLUDE_DIRECTORIES in sub-directories doesn't work?

I wouldn't expect that to work since I can see that it got the memo to include that directory but just doesn't do it. But I tried it out by using INCLUDE_DIRECTORIES(${CMAKE_CURRENT_SOURCE_DIR}) and I got the same bad results. On Tue, Nov 25, 2008 at 5:30 AM, Hugo Heden <[EMAIL PROTECTED]> wrote:

Re: [CMake] Default parameters in macros

Would that be all arguments or only unnamed ones? On Tue, Nov 25, 2008 at 12:46 PM, Alexander Neundorf <[EMAIL PROTECTED]> wrote: > On Tuesday 25 November 2008, Robert Dailey wrote: >> Hi, >> >> Are all macro parameters optional by default? If not, how can I make them >> optional? I have a couple

Re: [CMake] Default parameters in macros

On Tuesday 25 November 2008, Robert Dailey wrote: > Hi, > > Are all macro parameters optional by default? If not, how can I make them > optional? I have a couple of required parameters and a few optional ones. > Thanks. You can use the ${ARGV} special variable in macros to iterate over all provid

Re: [CMake] GetLibraryNamesInternal called on imported target

Boudewijn Rempt wrote: Hi, When I run (cvs head) cmake on my kde sources on OSX, I get lots of these errors: CMake Internal Error (please report a bug) in CMakeLists.txt: GetLibraryNamesInternal called on imported target: kparts What is going on? We're tracking it down. This is under di

[CMake] source_group(): Which project is it added to?

I'm having an issue right now where I'm trying to setup 2 projects in 1 CMakeLists.txt file. Basically what I do is: project( p1 ) add_executable() project( p2 ) source_group() add_library() For project p1, the visual studio project that is output (p1.vcproj) contains filters created by the sour

[CMake] Default parameters in macros

Hi, Are all macro parameters optional by default? If not, how can I make them optional? I have a couple of required parameters and a few optional ones. Thanks. ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] uninstall target & libraries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi thanks, shame on me, I should read the FAQ more often :) Pablo Jed Brown wrote: > On Tue 2008-11-25 16:27, Pablo Yanez Trujillo wrote: >> the file names should be: libmylib.so and libmylib.a instead of >> libmylib-shared.so and limylib-static.a?

Re: [CMake] CTest Subversion support and update handler

Please see submitted report and patch at http://www.cmake.org/Bug/view.php?id=8168 Bill Hoffman wrote: Number Cruncher wrote: Thanks for getting back to me. I'm working on a patch right now (with my best guess as to what was originally intended). Hopefully I'll have patch in the next day or s

Re: [CMake] uninstall target & libraries

On Tue 2008-11-25 16:27, Pablo Yanez Trujillo wrote: > the file names should be: libmylib.so and libmylib.a instead of > libmylib-shared.so and limylib-static.a? Also an FAQ http://www.cmake.org/Wiki/CMake_FAQ#How_do_I_make_my_shared_and_static_libraries_have_the_same_root_name.2C_but_different_

Re: [CMake] uninstall target & libraries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Michael Jackson wrote: > add_library (libname-shared SHARED ${SOURCES}) > add_library (libname-static STATIC ${SOURCES}) > > The target names need to be different. > well, I know that. Is there a posibility that the linked filenames get the same

Re: [CMake] uninstall target & libraries

add_library (libname-shared SHARED ${SOURCES}) add_library (libname-static STATIC ${SOURCES}) The target names need to be different. On Nov 25, 2008, at 10:02 AM, Micha Renner wrote: Me second question is: I create libraries in the following way: ADD_LIBRARY(libname SHARED ${SOURCES}) I wa

Re: [CMake] uninstall target & libraries

Am Dienstag, den 25.11.2008, 15:20 +0100 schrieb Pablo Yanez Trujillo: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi > > Is there a posibility to add a 'uninstall' target to remove installed files? Look here: http://www.cmake.org/Wiki/CMake_FAQ#Can_I_do_.22make_uninstall.22_with_CMake

[CMake] uninstall target & libraries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Is there a posibility to add a 'uninstall' target to remove installed files? Me second question is: I create libraries in the following way: ADD_LIBRARY(libname SHARED ${SOURCES}) I want to build shared (.so) and dynamic (.a) libraries as well (

Re: [CMake] CTest Subversion support and update handler

Number Cruncher wrote: Thanks for getting back to me. I'm working on a patch right now (with my best guess as to what was originally intended). Hopefully I'll have patch in the next day or so. Should I just post it here? Better to create a bug entry and post it there. Thanks! -Bill

Re: [CMake] CTest Subversion support and update handler

Thanks for getting back to me. I'm working on a patch right now (with my best guess as to what was originally intended). Hopefully I'll have patch in the next day or so. Should I just post it here? Simon. OK, so I am going to be brutally honest here... The person that wrote the CVS/SVN upd

Re: [CMake] CTest Subversion support and update handler

Bill Hoffman wrote: Number Cruncher wrote: Okay, I *think* I get that "svn log" is called for "U ", i.e. updated, but not for "M|C|G But why is "svn status" called when the file is updated to an older copy? Number Cruncher wrote: The more I look at the CVS logs for this, the more convinced I

Re: [CMake] CTest Subversion support and update handler

Number Cruncher wrote: Okay, I *think* I get that "svn log" is called for "U ", i.e. updated, but not for "M|C|G why is "svn status" called when the file is updated to an older copy? Number Cruncher wrote: The more I look at the CVS logs for this, the more convinced I am that there's a major

Re: [CMake] Bug? additional_clean_files not respected if no target present in directory

2008/11/18 Hugo Heden <[EMAIL PROTECTED]>: > Good day all, > > It seems that > > set_directory_propersties( properties additional_clean_files ... ) > > is not respected if no target present in the directory -- that is > 'make clean' will not remove the specified "additional clean file". Reported

Re: [CMake] Making ALL_BUILD be Visual Studio's "startup project"

Philip Lowman wrote: On Mon, Nov 24, 2008 at 2:45 PM, Tyler Roscoe <[EMAIL PROTECTED] > wrote: On Mon, Nov 24, 2008 at 02:22:22PM -0500, [EMAIL PROTECTED] wrote: > In a certain project where we started using CMake about five

Re: [CMake] INCLUDE_DIRECTORIES in sub-directories doesn't work?

2008/11/25 Sean Soria <[EMAIL PROTECTED]>: > CMakeLists.txt: > INCLUDE_DIRECTORIES(.) > ADD_SUBDIRECTORY(foo) > ADD_EXECUTABLE(hello main.c foo/main.c) > How about an absolute path instead of a relative? INCLUDE_DIRECTORIES( ${CMAKE_CURRENT_SOURCE_DIR} ) > foo/CMakeLists.txt: > INCLUDE_DIRECTORI

[CMake] INCLUDE_DIRECTORIES in sub-directories doesn't work?

CMakeLists.txt: INCLUDE_DIRECTORIES(.) ADD_SUBDIRECTORY(foo) ADD_EXECUTABLE(hello main.c foo/main.c) foo/CMakeLists.txt: INCLUDE_DIRECTORIES(.) I would expect foo/main.c to be compiled with: /usr/bin/gcc -I/code/xbmc/XBMC/build.test/. -I/code/xbmc/XBMC/build.test/foo/. -o CMakeFiles/hello.dir

Re: [CMake] Link in object files generated by another tool

2008/11/24 James Bigler <[EMAIL PROTECTED]>: > Is it possible to link in an object file generated by another tool? > > I want to create a custom command that generates an object file that I > could then link into a library or executable later. > > Is this possible from CMake? > An example follows.

Re: [CMake] CTest Subversion support and update handler

Okay, I *think* I get that "svn log" is called for "U ", i.e. updated, but not for "M|C|G why is "svn status" called when the file is updated to an older copy? Number Cruncher wrote: The more I look at the CVS logs for this, the more convinced I am that there's a major bug in the retrieval of

Re: [CMake] CTest Subversion support and update handler

The more I look at the CVS logs for this, the more convinced I am that there's a major bug in the retrieval of log information for modified files. Apologies if my last post was a bit blunt. I'm just a bit disappointed at not having any response to my bug submissions or patches. I'm trying to do