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
Philip Lowman wrote:
On Mon, Nov 24, 2008 at 2:45 PM, Tyler Roscoe [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
On Mon, Nov 24, 2008 at 02:22:22PM -0500, [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
In a certain project where we started using CMake about five
years
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 bug:
Number Cruncher wrote:
Okay, I *think* I get that svn log is called for U file, i.e.
updated, but not for M|C|G file, where local modifications exist. 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
Bill Hoffman wrote:
Number Cruncher wrote:
Okay, I *think* I get that svn log is called for U file, i.e.
updated, but not for M|C|G file, where local modifications exist.
But why is svn status called when the file is updated to an older copy?
Number Cruncher wrote:
The more I look at the
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
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
-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
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.3F
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
-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
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
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
-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?
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
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
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
provided
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 of
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:
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
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
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]
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
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]
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
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:
APPLE
CYGWIN
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
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
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
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
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.org
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})
On
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:
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
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 directory.
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
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
37 matches
Mail list logo
