|
|
|
|
|
by _ph_
2385 days ago
|
|
I avoid using makefiles, unless I need them :). Yes, plain Go projects which are supposed to produce an executable probably won't need a makefile and I haven't used any for those. But if your project should produce a shared library, it is nice to wrap the build command in a makefile, as it is easier to type "make". Also, when integrating into larger projects or when other tasks in addition to building the Go project are required, unifying them with makefiles can be helpful. |
|