[2016-07-22] Points need to be fixed about apig HOT 5 CLOSED

If we create makefile, we should follow make standard flow:

In this case make is unlikely to be responsible for ensuring dependencies or environments to be ready for following build and installation processes.

In a custom of Unix development, we often do this by ./configure.

from apig.

@creasty

In my understanding ./configure creates makefile by considering environments of the machine.
To install/link dependency is always in make command.

from apig.

Hmm. I think it does both.

from apig.

Anyway, we wrote makefile directly so considering ./configure makes problem difficult.
I understand go-like dependency is somehow new concept for makefile. So make deps is not too bad if other major go vendor uses it. So I just want to get examples of make deps
Other than that, if makefile already exists, make & make install must be natural.

from apig.

Other point is to consider usability.

If there are users who want to use make deps and make separately, we should split the command.
For example, make and make install should be separated since there are users who do not want to install command globally.

However, in make deps case, since we use glide, we can safely assume installing dependencies does not break other go programs. So almost all people always execute make deps and make. That is waste of time. So I think we should run both deps part and build part in make command

from apig.