On 09/08/2010 11:35 AM, Andreas Schneider wrote:
On Tuesday 31 August 2010 03:07:16 Miguel A. Figueroa-Villanueva wrote:
...oo master
. \
. ooo topic
.\\
...oooo *next, origin/next
Is this what should be done in such cases? Is
Let's say I have many different potential names for a library and the
following filesystem
/usr/lib/libnspr4.so
${CMAKE_CURRENT_SOURCE_DIR}/libnspr4a.so
find_library(TEST_LIBRARY
NAMES nspr4 nspr4a
HINTS ${CMAKE_CURRENT_SOURCE_DIR}
)
I'm somewhat surprised that the following code finds
On 8. Sep, 2010, at 8:25 , Philip Lowman wrote:
Let's say I have many different potential names for a library and the
following filesystem
/usr/lib/libnspr4.so
${CMAKE_CURRENT_SOURCE_DIR}/libnspr4a.so
find_library(TEST_LIBRARY
NAMES nspr4 nspr4a
HINTS ${CMAKE_CURRENT_SOURCE_DIR}
Hi,
What I meant was that the curses and Qt UI's should behave more like 'cmake'.
What does cmake actually do? The following code runs into an infinite loop on
ccmake (like intended), but cmake seems to finish after the first pass (it just
prints
out on once), though there is a newly
Hi all,
I would like to inform you that I'm volunteering to become the
maintainer of FindSubversion.cmake.
Best regards,
Marcel Loose.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
On Wed, Sep 8, 2010 at 3:43 AM, Diablo 666 thediablo...@hotmail.de wrote:
Hi,
What I meant was that the curses and Qt UI's should behave more like
'cmake'.
What does cmake actually do? The following code runs into an infinite loop
on
ccmake (like intended), but cmake seems to finish
Wow, that's pretty bad. I even replied to one of those threads. Sorry for
the noise. The official bug post for this issue is here:
http://public.kitware.com/Bug/view.php?id=10718
I agree with Alan Irwin that it will continue to haunt users well into the
future.
On Wed, Sep 8, 2010 at 2:38 AM,
On 09/08/2010 08:38 AM, Michael Wild wrote:
On 8. Sep, 2010, at 8:25 , Philip Lowman wrote:
Let's say I have many different potential names for a library and the
following filesystem
/usr/lib/libnspr4.so
${CMAKE_CURRENT_SOURCE_DIR}/libnspr4a.so
find_library(TEST_LIBRARY
NAMES nspr4
On Wed, Sep 8, 2010 at 8:56 AM, Michael Hertling mhertl...@online.dewrote:
...which shows that 10718 is still alive. ;-)
Hi Philip,
what's your opinion on this topic, in particular
- swapping loops and the required effort, the related risks
and the expected results,
I'd like to know if
Hi
I am experimenting with using CMake to replace our manually written gnu
makefiles on Linux. I have a couple of questions:
1) VERBOSITY
I would like to see the compiler command on the console when running make. I
know that one can run:
make VERBOSE=1
but that displays a lot of detail, for
On 8. Sep, 2010, at 16:33 , David Aldrich wrote:
Hi
I am experimenting with using CMake to replace our manually written gnu
makefiles on Linux. I have a couple of questions:
1) VERBOSITY
I would like to see the compiler command on the console when running make. I
know that one can
Hi Michael
Thanks for your answers.
One other thing was worrying me. Currently, if a user changes our manually
written makefile and checks it into svn, other users can do an svn update and
then invoke make to construct a new build.
If we move to cmake, users would modify and commit
Hi David
Yes, this is correct. And before you even get the idea: Never add the
CMake-generated files (Makefile, CMakeCache.txt, etc.) to your version control
system. They are not relocatable.
Michael
On 8. Sep, 2010, at 17:23 , David Aldrich wrote:
Hi Michael
Thanks for your answers.
Hi Michael
Yes, this is correct.
Thanks.
And before you even get the idea: Never add the
CMake-generated files (Makefile, CMakeCache.txt, etc.) to your version
control system. They are not relocatable.
Ah yes. You told me that before ;-) I will take your advice!
David
Hi there,
I'm using CMake with SDCC. Currently, support for SDCC in CMake does not also
include dialects for its various assemblers. So I've created one, for the
asx8051 assembler. The problem is that the asx8051 assembler shows nonstandard
behavior, and does not let you arbitrarily name the
Folks,
Is there an easy way (best practice) to add prebuilt .o files (external
to my build) to a .a easily?
--
Cheers,
Timothy St. Clair
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
On Wed, Sep 8, 2010 at 4:54 PM, Tim St. Clair timoth...@gmail.com wrote:
Folks,
Is there an easy way (best practice) to add prebuilt .o files (external
to my build) to a .a easily?
--
Cheers,
Timothy St. Clair
___
Powered by
On 09/08/2010 07:35 PM, Nick Foster wrote:
Hi there,
I'm using CMake with SDCC. Currently, support for SDCC in CMake does not also
include dialects for its various assemblers. So I've created one, for the
asx8051 assembler. The problem is that the asx8051 assembler shows
nonstandard
I guess a follow on to that would be the opposite to composition. If I
wanted to decompose a cmake library to determine what object files it
contains is there an easy mechanism for this?
Cheers,
Tim
On Wed, Sep 8, 2010 at 4:30 PM, David Cole david.c...@kitware.com wrote:
On Wed, Sep 8, 2010
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 8fe5c2ae216a2dbd61d671df5f436fe606924ca8 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via c9b0e1da5cf449ad54f873bc2b4d45df9197efb5 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 81fa6bbcc7daca38517da1f347de91d70db6a02f (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 4ea441eaf9a7a5dda266db9a6862fc9f8ed1c8cc (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 2079424568d92b97bb4f56340271bd924f64722c (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 02e3f42a6a4bc2b94befd35c908750c10f612d44 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 28edb70a9e22314da875a8fa104636461b71d8c6 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 795676062e4e6ddb4d471c42063b190b51507cea (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 18c71e3c79560f4577b7edb2910bfcac7cd0bfef (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 661d5166b06c30a7a490d28a8476989200744b87 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via fcbdd3129e7edec4b07f96662aa21371d671cb83 (commit)
from
30 matches
Mail list logo
