Hi,
I've had a look at the CMAKE_GENERATOR_TOOLSET option now. I think the
correct approach for WP8 is to hardcode v110_wp80 as it's the only option
that will properly give a working WP8 project. Thanks Brad for pointing this
out though - this might be useful for targeting versions in future
Brad King wrote:
Steve,
Thanks for working on this. Please update the documentation
of tll() to mention this behavior.
Also, the use of CollapseFullPath to evaluate /.. seems more
complicated than necessary. A single CollapseFullPath of the
original input followed by a check against a
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14302
==
Reported By:Jason Spiro
Assigned To:
On 07/19/2013 06:32 AM, Daniele E. Domenichelli wrote:
On 18/07/13 21:54, Brad King wrote:
Please update your topic to fix this and make sure tests pass
locally before publishing.
Done! Sorry about that!
Great, thanks.
-Brad
--
Powered by www.kitware.com
Visit other Kitware open-source
On 07/19/2013 05:42 AM, Paul Annetts wrote:
I think the first (and largest) stage of this is to support Windows Store
apps for Win32/ARM multiple architecture. Am I right in thinking this is
what Visual Studio 11 ARM generates?
That generates for the ARM architecture. It was a contributed
On 07/19/2013 12:02 AM, clin...@elemtech.com wrote:
- Original Message -
It looks to me like CMAKE_SYSROOT and CMAKE_OSX_SYSROOT are
pretty much identical other than the logical name mapping.
At a minimum we need to make them mutually exclusive (at most
one can be set in a single
Sorry wrong ML :(.
On Fri, Jul 19, 2013 at 4:36 PM, Nicolas Desprès
nicolas.desp...@gmail.comwrote:
Hi,
In Unix shell we can do that:
$ VAR=foo cmd in out
This way the environment variable is only set in the environment of the
process of the command and not the in current shell like when
Hi,
In Unix shell we can do that:
$ VAR=foo cmd in out
This way the environment variable is only set in the environment of the
process of the command and not the in current shell like when using the
export built-in.
I would like to be able to do the same for a custom command in CMake.
Ideally I
On 07/19/2013 10:36 AM, Nicolas Desprès wrote:
Hi,
In Unix shell we can do that:
$ VAR=foo cmd in out
This way the environment variable is only set in the environment of the
process of the command and not the in current shell like when using the
export built-in.
I would like to be
On 2013-07-19 10:36, Nicolas Desprès wrote:
In Unix shell we can do that:
$ VAR=foo cmd in out
This way the environment variable is only set in the environment of the
process of the command and not the in current shell like when using the
export built-in.
I would like to be able to do the same
On 2013-07-19 12:35-0400 Matthew Woehlke wrote:
On 2013-07-19 10:36, Nicolas Desprès wrote:
In Unix shell we can do that:
$ VAR=foo cmd in out
This way the environment variable is only set in the environment of the
process of the command and not the in current shell like when using the
export
Alexander Neundorf wrote:
On Monday 29 April 2013, Rolf Eike Beer wrote:
Alexander Neundorf wrote:
On Sunday 28 April 2013, Rolf Eike Beer wrote:
One question I see increasingly often is how do I test for C++11
support or for specific parts of that. For 2.8.12 I plan to include
12 matches
Mail list logo
