Am Freitag, 7. September 2012 um 18:59:49 schrieb Bill Hoffman:
On 9/7/2012 12:13 PM, Benjamin Eikel wrote:
Yes, I have seen that in the beginning when the generator did not work as
expected. At the moment, it builds from the command line, but only if you
give it access to a display (a
On 08.09.2012 11:51, Benjamin Eikel wrote:
Am Freitag, 7. September 2012 um 18:59:49 schrieb Bill Hoffman:
On 9/7/2012 12:13 PM, Benjamin Eikel wrote:
Yes, I have seen that in the beginning when the generator did not work as
expected. At the moment, it builds from the command line, but only if
Am Samstag, 8. September 2012 um 16:53:56 schrieb David Cole:
On Sat, Sep 8, 2012 at 6:38 AM, Peter Kümmel syntheti...@gmx.net wrote:
On 08.09.2012 11:51, Benjamin Eikel wrote:
Am Freitag, 7. September 2012 um 18:59:49 schrieb Bill Hoffman:
On 9/7/2012 12:13 PM, Benjamin Eikel wrote:
Yes,
I was a bit bored and decided to hack a bit on a bug I filed long ago
(http://cmake.org/Bug/view.php?id=10895). I have attached the first 3 patches I
came up with. I think #1 should just be applied without any further checks ;)
The other 2 are currently only compile tested. I think they should
On Sat, Sep 8, 2012 at 11:02 AM, Benjamin Eikel cm...@eikel.org wrote:
Am Samstag, 8. September 2012 um 16:53:56 schrieb David Cole:
On Sat, Sep 8, 2012 at 6:38 AM, Peter Kümmel syntheti...@gmx.net wrote:
On 08.09.2012 11:51, Benjamin Eikel wrote:
Am Freitag, 7. September 2012 um 18:59:49
Does this happen regardless of which Xcode you select, or only with
the -DP4 one?
Does this still happen for you if you use CMake from the 'next' branch?
On Fri, Sep 7, 2012 at 6:30 PM, Sean McBride s...@rogue-research.com wrote:
Hi all,
I believe I am seeing this too. I have 3 versions of
This should be fixed already in 'next' and 'master'.
This bug report:
http://public.kitware.com/Bug/view.php?id=13463
And this git commit:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e88bae77
use xcode-select to determine the Xcode to use...
That fix is in 'master' already and will be
Hi, all!
I was googled about how to change the PDB file name. it seems the PDB name
still hardcode in cmTarget.cxx?
There exist any way to change the PDB filename for now?
I don't want to adding /FdXXX.pdb for compile, and /PDB:XXX.pdb for
link.
It's will given overwriting warning because in
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 ad6211368707d24350bbdfd057c3024ab52093f5 (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 9d7c77e2eb24ca7a8292001fb0cdafd87903951c (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 ec5b04781d14ee70ef1424a6f8e52ade40495cfe (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 0550c387ed25147c9abc58efece72e2a6726a0d5 (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 fe24f1f961d2449ddfaef1208b67b03e124f52b6 (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 e2bc80608f0eda255d59a2f593ea9df6eb5fac39 (commit)
via
14 matches
Mail list logo
