On 10/14/2013 04:40 PM, Evgeniy Dushistov wrote:
I wonder, does cmake support more then 8 bits for text encoding?
Looking at source code there is nothing about wchar_t or converting
utf-16/utf-32 to utf-8 on the fly. So what sence to support
anything except utf-8 BOM?
I wrote it that way to
On 10/15/2013 05:57 AM, Eric Noulard wrote:
However, from my understanding of the cmRST::ProcessModule
assumes that all markup are in a header I think it would be more convenient
to allow #.rst: anywhere in a module
It is allowed anywhere in the module already. Any #.rst: line
enables
On 10/14/2013 05:10 PM, Raphael Kubo da Costa wrote:
This was probably broken for a long while, but the problem was not apparent
because the check for execinfo.h would fail by default because
-I/usr/local/include was not being passed to the compiler when making the
checks for the header's
On 10/10/2013 09:46 AM, Brad King wrote:
Since this topic makes sweeping changes throughout the source code
we'll have to schedule a flag day on which I will freeze the
repository and apply the permanent conversion. Currently I plan
for this to be just after 2.8.13 is released.
As discussed
On 10/15/2013 11:06 AM, Eric Noulard wrote:
The fact that CPack uses cmake scripts does not mean the cmake **command**
is processing the CPack scripts.
I'm sure you know that but cpack -G NSIS does not call cmake command,
it is simply creating a cmake script processing object instance.
In
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14485
==
Reported By:irwin
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14486
==
Reported By:irwin
Assigned To:
On 2013-10-15 10:21-0400 Brad King wrote:
On 10/14/2013 02:22 PM, Alan W. Irwin wrote:
Therefore, I think a good compromise would be to provide both of these
possibilities to users, with the first one being used by default, but
with the second one used instead if a specific variable or
Hi!
I have the test succesfully running using the provided framework for
CTestUpdate, so I have a new CTest.UpdateP4 test. Right now it runs against
a local p4d server instance that you can download for free from Perforce.
I'm imagining that, depending on the testing machine, we might need to be
On 2013-10-15 18:44, Pedro Navarro wrote:
I'm imagining that, depending on the testing machine, we might need to be
able to specify where the perforce server is located, if it's not the local
machine (using either a command line switch or an environment variable). Is
there any infrastructure for
10 matches
Mail list logo
