I think the basic idea is that Go projects do not have makefiles because
they do not need makefiles.
Ideally the Go command does the right thing, including fetching and
building dependencies, and building
entire trees of projects. Go is opinionated, and dictates where each
package can be found
On Aug 23, 2021, at 12:48, Roland Müller wrote:
>
> What are the alternatives to Makefile that are used by Go developers? Please
> comment :-)
Well, there’s mage, which aims to more or less replace the functionality of
Make for Go. I’m not really sold on *needing* a replacement for Make, and i
*** Roland Müller [2021-08-23 19:47]:
>What are the alternatives to Makefile that are used by Go developers?
>Please comment :-)
The best thing I saw, that literally completely changed my life is DJB's
redo build system. I replaced everything related to Makefile in all my
projects, gaining simplic
Dnia 2021-08-23, o godz. 19:47:47
Roland Müller napisał(a):
> What are the alternatives to Makefile that are used by Go developers?
https://github.com/magefile/mage
yw.
--
Wojciech S. Czarnecki
<< ^oo^ >> OHIR-RIPE
--
You received this message because you are subscribed to the Google Group
Am Mo., 23. Aug. 2021 um 18:48 Uhr schrieb jake...@gmail.com <
jake6...@gmail.com>:
> On Sunday, August 22, 2021 at 11:11:23 PM UTC-4 jlfo...@berkeley.edu
> wrote:
>
>>
>> I've noticed that few, if any, Go programs use Makefiles. Is that because
>> the overhead of using make is greater than the ov
On Sunday, August 22, 2021 at 11:11:23 PM UTC-4 jlfo...@berkeley.edu wrote:
>
> I've noticed that few, if any, Go programs use Makefiles. Is that because
> the overhead of using make is greater than the overhead of just always
> compiling and linking everything?
>
Go had built in build caching
