trunk/Makefile: missing 'install' target

[GoogleCodeExporter]

Traditionally, running `make` builds a project in place, while `make
install` installs the software. Currently `make` builds and then installs
crusty, much to the dismay of the hapless builder.

1. Modify `make` such that the project is built in place but not installed.

2. Add target `make install` which installs the built project on the user's
system.

Original issue reported on code.google.com by david.a....@gmail.com on 17 Jan 2007 at 3:18

[GoogleCodeExporter]

Tried an initial stab at fixing this.  I pretty much split out the building of
snownews from its install.  Then I turned the old all target into the install 
target.
 The new all target just builds snownews.  

Original comment by scott.he...@gmail.com on 19 Jan 2007 at 4:25

[GoogleCodeExporter]

I don't entirely understand your change...

It seems counterintuitive that `make all` only builds one application. If this 
is
because there's only a single app that needs compiled right now, perhaps the 
target
should be named `make compile` or something a bit more accurate.

Original comment by david.a....@gmail.com on 19 Jan 2007 at 6:55

[GoogleCodeExporter]

Standard schemes seem to suggest that all should do the compiling and install 
should
do the installing.  Hence why every install instructions use make && make 
install.

Original comment by scott.he...@gmail.com on 23 Jan 2007 at 9:55

[GoogleCodeExporter]

I think we should adopt standards. So I like the "make" and "make install" 
option.

Original comment by menzies....@gmail.com on 4 Feb 2007 at 2:49

• Changed state: Fixed