itiated, but with the Visual Studio generator it
> seems to just skip over it unless CMake has something else it needs to do.
>
> On Fri, Feb 8, 2019 at 8:44 PM frodak17 wrote:
>
>> I haven't tried it out but I'm not exactly surprised it wouldn't work
>> w
I haven't tried it out but I'm not exactly surprised it wouldn't work with
Visual Studio 2017.
It seems to be similar to the issue mentioned here:
https://stackoverflow.com/q/54557801/1028434
The problem I noticed in the case of the StackOverflow question,
"add_custom_target(testcmake2 ALL)" does
On Wed, Jan 16, 2019 at 3:27 PM Venedict Tchistopolskii
wrote:
> Pressing "STOP" in the CMake GUI interface halts CMake itself but does not
> stop any execute_process that is going on at the time. This makes it hang
> until the process finishes, since no interrupt is sent..
>
> Aggravating wh
On Sat, Dec 22, 2018 at 10:58 AM Torsten Robitzki
wrote:
> Hi,
>
> > Am 17.12.2018 um 21:18 schrieb Kyle Edwards via cmake-developers <
> cmake-developers@cmake.org>:
> >
> > Then, executables and libraries could have a toolchain specified:
> >
> > add_executable(BuildUtility TOOLCHAIN DEFAULT ..
On Tue, Dec 18, 2018 at 4:41 PM Kyle Edwards
wrote:
> On Tue, 2018-12-18 at 16:12 -0500, frodak17 wrote:
>
> What about conflicting build types when building a host tool target vs the
> cross compiler target?
> For instance the host tool may (should?) be built as a release pro
> How does this work with multiple languages and the project() command and
>> enable_language() commands?
>>
> Both project() and enable_language() could be extended with an optional
> TOOLCHAIN argument.
>
So it would be something like project( [TOOLCHAIN
[LANGUAGES] [...]) where TOOLCHAIN and i
How does this work with multiple languages and the project() command and
enable_language() commands?
For instance you want to use the host c++ compiler and a toolchain
specified compiler for c and c++.
When project() enables the c++ compiler it runs through a bunch of scripts
to find and test the
What first cross my mind with '"utilities" needed for build' is when you
have to build the cross-compiler in the first place before you build
anything for the target.
If so how do you handle verification of the tool-chain can build a working
executable or library?
Normally that is done at the time
