• Russ Cox's avatar
    cmd/go: implement per-package asmflags, gcflags, ldflags, gccgoflags · 5993251c
    Russ Cox authored
    It has always been problematic that there was no way to specify
    tool flags that applied only to the build of certain packages;
    it was only to specify flags for all packages being built.
    The usual workaround was to install all dependencies of something,
    then build just that one thing with different flags. Since the
    dependencies appeared to be up-to-date, they were not rebuilt
    with the different flags. The new content-based staleness
    (up-to-date) checks see through this trick, because they detect
    changes in flags. This forces us to address the underlying problem
    of providing a way to specify per-package flags.
    
    The solution is to allow -gcflags=pattern=flags, which means
    that flags apply to packages matching pattern, in addition to the
    usual -gcflags=flags, which is now redefined to apply only to
    the packages named on the command line.
    
    See #22527 for discussion and rationale.
    
    Fixes #22527.
    
    Change-Id: I6716bed69edc324767f707b5bbf3aaa90e8e7302
    Reviewed-on: https://go-review.googlesource.com/76551
    Run-TryBot: Russ Cox <rsc@golang.org>
    Reviewed-by: 's avatarDavid Crawshaw <crawshaw@golang.org>
    5993251c
output_test.go 5.83 KB