On Fri, Nov 4, 2016 at 8:28 PM, Ian Lance Taylor <i...@golang.org> wrote:
> On Fri, Nov 4, 2016 at 7:37 AM, <chhatoipri...@gmail.com> wrote: > > Incremental build support in `go build` would be much appreciated. > > > > AIUI, the only way to have incremental builds using standard go tools are > > through `go install`; but `go install` is not a compiler/linker/builder > and > > it doesn't simply build a go project. > > > > Even if `go build` doesn't handle incremental builds, if I can use > whatever > > the equivalent of `gcc -c example.c -o example.o` and `gcc -o binary > > example.o example2.o ...` are, I'd be happy, since then I could > integrate it > > with make. I'm guessing this has been asked before, since it sounds like > a > > wish I expect many people would have had, but I couldn't find any > > discussions related to this. > > `go build` takes a -o option that you can use to put the results where > you please. > Yes, I use that. But that's only `-o`. In my original comment about gcc's `-o` I meant to point to the ability to link together compiled object files, not to choose the output file name and location. > I'm not sure what it means to have `go build` do an incremental build > It would mean to not recompile source files/packages that haven't changed. without using `go install`. Where would the intermediate files go, > A place of the user's choosing, with a safe default of "right beside the corresponding source code". For comparison, whatever people do with gcc's `-c`. As it stands now, there's no way for me to even instruct `go build` to place the files specifically somewhere, or to not delete them after a run. and why would we want them in a place different than there `go > install` puts them? > You may not want that. And that's fine. I'm not asking to change `go install`'s default behaviour. Some people might, like at my work, where we use separate workspaces and projects with non github repos (and non go-gettable urls). Like the difference between the conventional meanings of `make` and `make install`. The former builds it locally, within the project; and the latter does the actual installation to an intended location. Both support incremental building (it's just make, after all). But `go install` is like `make && make install`, and there's no way to split that into two operations. See also `go build -i`. > That makes `go build` fetch any dependencies it encounters, right? Does it do anything relevant to incremental building? > Ian > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
