On 12/03/19 5:09 PM, Khem Raj wrote:
On Mon, Mar 11, 2019 at 5:47 PM Douglas Royds
wrote:
On 12/03/19 6:18 AM, Khem Raj wrote:
On Sun, Mar 10, 2019 at 10:53 PM Douglas Royds
wrote:
Since the dawn of time, we have set CMAKE_VERBOSE_MAKEFILE=1 in cmake.bbclass.
Back in 2016, we also explicitl
On Mon, Mar 11, 2019 at 5:47 PM Douglas Royds
wrote:
>
> On 12/03/19 6:18 AM, Khem Raj wrote:
>
> On Sun, Mar 10, 2019 at 10:53 PM Douglas Royds
> wrote:
>
> Since the dawn of time, we have set CMAKE_VERBOSE_MAKEFILE=1 in cmake.bbclass.
> Back in 2016, we also explicitly set VERBOSE=1 in cmake_do
On 12/03/19 6:18 AM, Khem Raj wrote:
On Sun, Mar 10, 2019 at 10:53 PM Douglas Royds
wrote:
Since the dawn of time, we have set CMAKE_VERBOSE_MAKEFILE=1 in cmake.bbclass.
Back in 2016, we also explicitly set VERBOSE=1 in cmake_do_compile(),
to ensure that make (and ninja) output were verbose in
On Sun, Mar 10, 2019 at 10:53 PM Douglas Royds
wrote:
>
> Since the dawn of time, we have set CMAKE_VERBOSE_MAKEFILE=1 in cmake.bbclass.
> Back in 2016, we also explicitly set VERBOSE=1 in cmake_do_compile(),
> to ensure that make (and ninja) output were verbose in log.do_compile.
>
> Turning off
Since the dawn of time, we have set CMAKE_VERBOSE_MAKEFILE=1 in cmake.bbclass.
Back in 2016, we also explicitly set VERBOSE=1 in cmake_do_compile(),
to ensure that make (and ninja) output were verbose in log.do_compile.
Turning off CMAKE_VERBOSE_MAKEFILE=1 means that make (or ninja)
invocations fr
