On Fri, Nov 4, 2016 at 2:55 PM, Brad King wrote:
>
> On 11/03/2016 06:04 PM, John Drescher wrote:
> > I opened a project in cmake-gui using the open project button from a
> > vc 2010 build of a project. The open project opened the project in
> > Visual Studio 2010. Later I opened the same project
On Thu, Jan 28, 2016 at 3:36 PM, Ben Boeckel wrote:
> On Thu, Jan 28, 2016 at 15:15:58 -0500, Taylor Braun-Jones wrote:
>> That's too bad. I understand the perspective of the Ninja developers,
>> but it's not clear to me what the proposed alternative should be.
>
On Thu, Jan 28, 2016 at 11:28 AM, Nicolas Desprès
wrote:
> Unfortunately, Ninja won't offer it:
> https://github.com/ninja-build/ninja/pull/1079
That's too bad. I understand the perspective of the Ninja developers,
but it's not clear to me what the proposed alternative should be.
Should CMake be
On Sat, Mar 28, 2015 at 10:38 AM, Taylor Braun-Jones
wrote:
>
> See htop screenshot below for an example of what I mean. Note that
`ninja` in the original command line invocation is just a bash alias for
ninja-build (the name of the ninja binary on Fedora-based systems)
>
> Should I e
On Mon, Jan 11, 2016 at 5:16 PM, Stephen Kelly wrote:
> Taylor Braun-Jones wrote:
>
>> Consider library project Foo that uses a header-only project Bar. In
>> FooConfig.cmake, it is a important to ensure any projects using Foo also
>> use the exact same version of Bar
On Fri, Jan 8, 2016 at 9:12 AM, Nils Gladitz wrote:
>
>
> On 01/08/2016 02:50 PM, Yves Frederix wrote:
>
>> You are explicitly mentioning 'setting' of a property. IMHO there is a
>> big difference between setting and getting a property. If
>> white/blacklisting is enforced during setting only, wo
Hi all,
I'm looking for a template or example project that shows the how to
setup a cmake-based project in the cleanest and simplest way (i.e.
using all the latest features of 3.3 release) and with support for the
following build features:
- Superbuild mode that can be turned on or off (on by def
Does the CMake Ninja generator support a way to skip dependencies when
building a target? Something like the target_name/fast feature for the
Makefile generator? [1]
Thanks,
Taylor
[1]
http://www.cmake.org/Wiki/CMake_FAQ#Is_there_a_way_to_skip_checking_of_dependent_libraries_when_compiling.3F
--
On Mon, May 18, 2015 at 8:48 AM, Brad King wrote:
> On 05/17/2015 12:35 AM, Taylor Braun-Jones wrote:
> > CMake already has an ENVIRONMENT property for tests ...
> > symmetric feature would be to support an ENVIRONMENT property
> > for targets as well.
>
> We can p
On May 16, 2015 12:18 PM, "Dan Kegel" wrote:
> Write a wrapper script that sets the variables and invokes the compiler,
> and tell cmake that's your compiler.
>
Ya, I thought about this but aside from having an interceptor for an
interceptor there are also other complexities like:
(1) One of th
ut
for the sake of simplicity, I'd prefer to just export the environment
variable for any target and not worry about polluting the environment for
targets that don't need/care about the special environment variables.
Thanks again,
Taylor
On Fri, May 15, 2015 at 11:48 AM, Taylor Braun-Jones
Is it possible for CMake to generate a Makefile that exports environment
variables whenever a target is executed? I want all invocations of gcc to
see the environment variables COVFILE=xxx and COVSRCDIR=xxx
Thanks,
Taylor
--
Powered by www.kitware.com
Please keep messages on-topic and check the
See htop screenshot below for an example of what I mean. Note that `ninja`
in the original command line invocation is just a bash alias for
ninja-build (the name of the ninja binary on Fedora-based systems)
[image: Inline image 1]
Should I expect to see the -l3 option to be propagated automatical
Hi all,
I'm curious if anyone has attempted to integrate Artifactory with the
ExternalData framework?
Unfortunately the Artifactory REST API is a two step process where you
first search for a file based on MD5 or SHA1 hash[1] which returns JSON
results the file's URI. You then issue a second requ
14 matches
Mail list logo
