Clinton Stimpson wrote:
On Aug 11, 2012, at 10:36 AM, Alexander Neundorf wrote:
On Friday 10 August 2012, Stephen Kelly wrote:
David Cole wrote:
I assume it's the qt4_use_modules branch on the stage?
Yes, sorry, I should have pointed that out.
What was the plan with the more
David Cole wrote:
I think we should understand this before we simply exclude the test:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5d44e7b15ab40ba4568ce7c584df587c03caed40
Can you point us to the dashboard failure that occurred that you did
not understand?
This was actually my exact intent (to re-involve the original
reporters via the notification system, since nobody else has picked up
on the bugs enough to assign them), and this was just step 1.
The bug tracker's roadmap page and what bugs are actually assigned to
active CMake developers are two
Hi everybody,
I need your help. In the next week, if you have time.
No doubt you're already sick of reading the emails about the bug
tracker from the last couple of days.
My main goal here is simply to be able to get a good picture of what's
really happening by inspecting bug tracker query
On 08/10/2012 09:27 AM, Brad King wrote:
Since the first step involves making 'master' and 'next' consistent
we plan to disable merge access to 'next' for the first couple days
of next week.
Push access to the stage and merge access to 'next' have been disabled
in preparation for this sweep.
Brad King wrote:
On 08/10/2012 10:30 AM, Stephen Kelly wrote:
I've updated the branch with the API change to use std::set. The XCode
generator does not use the cmLocalGenerator::AppendDefines method, but
the VisualStudio6Generator does.
That wasn't quite what I had in mind. The string of
Am 2012-08-13 13:35, schrieb David Cole:
Hi everybody,
I need your help. In the next week, if you have time.
No doubt you're already sick of reading the emails about the bug
tracker from the last couple of days.
My main goal here is simply to be able to get a good picture of
what's
really
On 8/13/2012 10:54 AM, Stephen Kelly wrote:
Bill Hoffman wrote:
There is a new failure here:
http://open.cdash.org/testDetails.php?test=156059931build=2506673
Is the output truncated somehow, or is that really all of it?
I ran it in a debugger, and cmake was crashing, this fixed it, but I
On Mon, Aug 13, 2012 at 10:26 AM, Rolf Eike Beer e...@sf-mail.de wrote:
Am 2012-08-13 13:35, schrieb David Cole:
Hi everybody,
I need your help. In the next week, if you have time.
No doubt you're already sick of reading the emails about the bug
tracker from the last couple of days.
My
On 08/13/2012 03:41 AM, Stephen Kelly wrote:
What was the plan with the more generic target_use_package() or how it
was named ? This would do something similar, right ?
target_use_targets() in the latest proposal.
The discussion thread was here:
On 06/11/2012 11:27 AM, Brad King wrote:
I've started a local topic branch and implemented $0:...,
$1:..., and $CONFIG: When I get a chance I'll add
some of the other queries, documentation, and tests for the
generator expression features.
I've been making occasional progress on this.
On 08/13/2012 08:35 AM, Brad King wrote:
On 08/10/2012 09:27 AM, Brad King wrote:
Since the first step involves making 'master' and 'next' consistent
we plan to disable merge access to 'next' for the first couple days
of next week.
Push access to the stage and merge access to 'next' have
On Monday 13 August 2012, David Cole wrote:
Hi everybody,
I need your help. In the next week, if you have time.
...
Done for my stuff.
Alex
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages
On 2012-08-13 06:54-0400 David Cole wrote:
This was actually my exact intent (to re-involve the original
reporters via the notification system, since nobody else has picked up
on the bugs enough to assign them), and this was just step 1.
The bug tracker's roadmap page and what bugs are
On Mon, Aug 13, 2012 at 3:37 PM, Alan W. Irwin
ir...@beluga.phys.uvic.ca wrote:
On 2012-08-13 06:54-0400 David Cole wrote:
This was actually my exact intent (to re-involve the original
reporters via the notification system, since nobody else has picked up
on the bugs enough to assign them),
Here are some simple facts:
- There are presently 1,204 open issues in the CMake bug tracker.
- We averaged 111 days per release from CMake 2.8.1 to CMake 2.8.9.
- Each release contained an average of 79 bug fixes from 2.8.3 to 2.8.9.
Hence.. I have a strong desire to focus in on
On 2012-08-13 17:23-0400 David Cole wrote:
I realize that this is a touchy subject, and tried very hard to word
my messages that went along with this action to make it very clear
that putting a bug into the 'backlog' is not in the least bit
permanent.
I think the politics of this could be
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=13467
==
Reported By:kMh3Bt2pBM
Assigned To:
Aaron Smith wrote:
Hey All,
First off I'm loving cmake, This thing makes my life so easy. Thank you!
I'm working on porting some code to Windows at the moment. I'm putting in
configure checks for stdint.h and it's types. The strange thing is that
finding the header works, but then finding
http://public.kitware.com/Bug/view.php?id=12373
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to
The offending line is this.
/tmp/$/build$ grep -H -n '/tmp/$/src/tutorial.cpp'
CMakeFiles/tutorial.exe.dir/build.make
CMakeFiles/tutorial.exe.dir/build.make:53:CMakeFiles/tutorial.exe.dir/tutorial.cpp.o:
/tmp/$/src/tutorial.cpp
This is obviously a bug in cmake but not a bug in make, as special
Did you make the mistake of relocating your Qt installation?
You could run qmake -query to see the paths it prints out, to make sure it
matches your installation.
Clint
On Aug 12, 2012, at 12:59 PM, Toronto Andrew wrote:
Yes to both John, I did point the CMake gui to the position of the
andreas@warnemuende /tmp/$/foo % cat main.cpp
int main()
{
return 0;
}
andreas@warnemuende /tmp/$/foo % cat CMakeLists.txt
add_executable(foo main.cpp)
Can you try that on your side to see wether it works?
The error still exits.
/tmp/$/foo_build$ cmake ../foo
-- The C compiler
Haha spot on mate.
I did so. To rectify, I reinstalled VTK and CMake, fixed the PATH var and
the QTDIR. FindQt4 now actually finds 4.8.2 as opposed to 4.8.0, however
some flags like QT_USE_FILE and QT_QTGUI_LIBRARY seem to still point at
4.8.0 prompting some linker issues during the build.
Hi,
I use the following command to generate the pdf file from cmake
manpage. But the pdf file does not have bookmarks. Does anybody know a
way to generated the manual in pdf with bookmarks and possibly
hyperlinks?
man -t $f | ps2pdf - $f.pdf
--
Regards,
Peng
--
Powered by
2012/8/13 Peng Yu pengyu...@gmail.com:
Hi,
I use the following command to generate the pdf file from cmake
manpage. But the pdf file does not have bookmarks. Does anybody know a
way to generated the manual in pdf with bookmarks and possibly
hyperlinks?
man -t $f | ps2pdf - $f.pdf
If
On 08/13/2012 04:18 PM, Peng Yu wrote:
Hi,
I use the following command to generate the pdf file from cmake
manpage. But the pdf file does not have bookmarks. Does anybody know a
way to generated the manual in pdf with bookmarks and possibly
hyperlinks?
man -t $f | ps2pdf - $f.pdf
On Friday 10 August 2012, David Cole wrote:
Hi all,
Replies requested. Short replies only. Read on. Just a short reply
with bug numbers or links to the bugs is all we need here.
Example one-line reply:
http://public.kitware.com/Bug/view.php?id=13463
Personally I would prefer this
$ docbook2pdf cmake-help.docbook
I got error message like the following on ubuntu.
openjade:/home/pengy/cmake-help.docbook:13:14:E: end tag for
itemizedlist which is not finished
openjade:/home/pengy/cmake-help.docbook:21:14:E: end tag for
itemizedlist which is not finished
On Mon, Aug 13, 2012 at 12:07 PM, Alexander Neundorf
a.neundorf-w...@gmx.net wrote:
On Friday 10 August 2012, David Cole wrote:
Hi all,
Replies requested. Short replies only. Read on. Just a short reply
with bug numbers or links to the bugs is all we need here.
Example one-line reply:
Hey All,
I'm trying to work my way through some windows configuration and running
into problems. I'm trying a few things: looking for headers, looking for
lib files, and looking for functions/symbols in them. I'm particularly
interested in Winsock stuff right now.
I have a couple things hard
2012/8/13 Peng Yu pengyu...@gmail.com:
$ docbook2pdf cmake-help.docbook
I got error message like the following on ubuntu.
openjade:/home/pengy/cmake-help.docbook:13:14:E: end tag for
itemizedlist which is not finished
openjade:/home/pengy/cmake-help.docbook:21:14:E: end tag for
Hi,
On Mon, Aug 13, 2012 at 4:16 PM, Toronto Andrew
andrew.loui...@gmail.com wrote:
Haha spot on mate.
I did so. To rectify, I reinstalled VTK and CMake, fixed the PATH var and
the QTDIR.
Relocating Qt requires either patching the qmake binary or installing
a qt.conf file to help qmake find
Bump.
On Mon, Jul 30, 2012 at 3:59 PM, Xu Wang xuwang...@gmail.com wrote:
Hi,
I'm curious as to whether there will be a 6th edition of this wonderful
book. If so, any (rough?) estimate on when it will be published?
Thanks so much!
Xu
--
Powered by www.kitware.com
Visit other Kitware
Hi,
I just want Hello World! to be shown and everything else be
suppressed. -Wno-dev seems not relevant. I don't find other options
seem to be useful in the manual. In case I miss anything in the
manual, is there an option to suppress these messages? Thanks!
Hi,
The following directory has 'cmake ../src1' run before. I get the
following error when I run the following command. One way to solve the
problem is to run rm -rf *, but I'm wondering if there is a way to
force cmake to run even when the source directory changes. I don't see
such a command
Andreas Pakulat-2 wrote
Hi,
Relocating Qt requires either patching the qmake binary or installing
a qt.conf file to help qmake find the libs in the new position. The
absolute include/lib dirs are hardcoded into qmake when its being
built. See http://doc.qt.nokia.com/4.7/qt-conf.html for
Hi,
On Mon, Aug 13, 2012 at 9:48 PM, Peng Yu pengyu...@gmail.com wrote:
Hi,
The following directory has 'cmake ../src1' run before. I get the
following error when I run the following command. One way to solve the
problem is to run rm -rf *, but I'm wondering if there is a way to
force cmake
Hi,
you can't tell cmake to do this and usually you don't want to either.
These are status messages indicating what cmake is using so you can
easily spot if cmake chose the wrong compiler or found a library in a
place where you didn't expect it.
To suppress all non-error output you can do:
On 8/11/2012 5:43 PM, Jerry Krinock wrote:
That's a good question, Bill. The answer is that, starting with
recent versions, Xcode 4.3 or 4.4 I think, the Xcode Command-Line
Tools are not installed with Xcode, but are a separate download
which must be installed after installing Xcode.
Yes,
Hi,
On Mon, Aug 13, 2012 at 9:40 PM, Toronto Andrew
andrew.loui...@gmail.com wrote:
Andreas Pakulat-2 wrote
Relocating Qt requires either patching the qmake binary or installing
a qt.conf file to help qmake find the libs in the new position. The
absolute include/lib dirs are hardcoded into
On Mon, Aug 13, 2012 at 3:37 PM, Andreas Pakulat ap...@gmx.de wrote:
Hi,
you can't tell cmake to do this and usually you don't want to either.
These are status messages indicating what cmake is using so you can
According to the common linux philosophy, mostly status messages like
this are
On 8/13/2012 5:38 PM, Peng Yu wrote:
According to the common linux philosophy, mostly status messages like
this are suppressed in other tools unless otherwise instructed.
Therefore, I think that it may be better to suppress these messages by
default and add an option in cmake to enable them when
Hi,
The following command output shows that when I touch a source without
changing the content, the source are compiled and linked, which is a
waste.
This post shows how to use the checksum to decide whether a file is
changed or not, if changed then update target. This feature seems to
be
CMake really leaves the decision when to recompile something to the
backend, i.e. GNU Make, Xcode, Visual Studio, ninja etc. It merely
defines dependencies and then lets the actual build tool handle the
rest, and most of them choose to use simple time-stamps instead of
hashes. Also note that
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 ec8ad7088144d0907889310d97e0b062d2a427e1 (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, next has been updated
via 1c6cf47bc197b58fe5ff949c51042a3d849f92c4 (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 bed44c2cc1d308166a7c00d5f1b6506ad118cd99 (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 e85650909332f6ca84917e1b003192e6207ef304 (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 e93d9c5c2b8095cf94ebb92763604db0108e0818 (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 85f843a7b4aaf1b25e1e1e60ecdae3a3e2d7a9cb (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 20f56a7eed52a4ab113bb6973d0107bb892e3366 (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 11a9ea35dece1f720a2cfcc1f5eb3928c0858ad2 (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 92b11383d9507d157fb323faba0784bb3afca57f (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 4bdbdfbfefa7bd492530bd5db1152bb02765fb81 (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 0d28661999feed72e00555a410184670dc82edf7 (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 c1163632de2467f44c3774d401a04a76f1444c2f (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 396bc2847750e6a48d3e059a012f7ebf268f676c (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 1f793ab6baf47ce6564f02a5540840c727a48d52 (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 e0f7d7fe5a52613bc23cc596fbf6bde8f54f367a (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 f0295575d7fa4b554abc4d6b2af07b9f6cbde437 (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, next has been updated
via 26d12b38e464d4345e164ac13df5a4d1586e297a (commit)
via
62 matches
Mail list logo
