Re: Some thoughts about our tests and the build time

Stephan Bergmann <sbergman -AT- redhat.com>
Wed, 25 May 2016 13:22:24 +0200

On 05/25/2016 12:50 PM, Bjoern Michaelsen wrote:

On Wed, May 25, 2016 at 09:11:21AM +0200, Stephan Bergmann wrote:

To me at least, the build-nocheck target looks like a useful tool for
developers, not a "travesty".


Im not suggesting to kill what it does (building without running checks). Im
suggesting that we get module and toplevel targets to be consistent.

So you're suggesting that top-level "make build" will do what top-level"make build-nocheck" does today? Fine with me.

Context

Re: Some thoughts about our tests and the build time (continued)
- Re: Some thoughts about our tests and the build time · Bjoern Michaelsen
  - Re: Some thoughts about our tests and the build time · Markus Mohrhard
    - Re: Some thoughts about our tests and the build time · Bjoern Michaelsen
- Re: Some thoughts about our tests and the build time · Michael Stahl
  - Re: Some thoughts about our tests and the build time · Bjoern Michaelsen
    - Re: Some thoughts about our tests and the build time · jan iversen
      - Re: Some thoughts about our tests and the build time · Bjoern Michaelsen
    - Re: Some thoughts about our tests and the build time · Stephan Bergmann
    - (message not available)
      - Re: Some thoughts about our tests and the build time · Bjoern Michaelsen
        
        Re: Some thoughts about our tests and the build time · Stephan Bergmann

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.