<div dir="ltr">[inlibne]<br><div><div class="gmail_extra"><br><div class="gmail_quote">On 14 May 2015 at 15:20, D. Hugh Redelmeier <span dir="ltr"><<a href="mailto:hugh@mimosa.com" target="_blank">hugh@mimosa.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">| From: Andrew Cagney <<a href="mailto:andrew.cagney@gmail.com">andrew.cagney@gmail.com</a>><br>
<span class=""><br>
| First, as discussed on IRC, it turns out that the sequence:<br>
|<br>
| make programs ; sudo make install<br>
|<br>
| is very much entrenched as a standard way to get everything installed.<br>
| Consequently, to avoid having "make install" build stuff, "make programs"<br>
| will need to build everything - it can't just build programs. Effectively<br>
| "programs" and "all" are synonyms.<br>
<br>
</span>Ouch.<br>
<br>
I frequently do "make programs" to build JUST userland.<br>
<br></blockquote><div><br></div><div>Just to clarify, up until a few days ago "make programs install" built/installed:<br><br></div><div>- binaries<br></div><div>- scripts<br></div><div>- configs<br></div><div>- just docs (aka man pages) install worked - if xmlto was in your path the build tended to die; and it if wasn't, good luck is what let things continue<br></div><div><br>As proposed, I changed things, and fixed some bugs, so that "make all install" did all the above (including docs) and worked; and then set up "make programs install-programs" to do binaries, scripts and configs but not docs/manpages.<br><br>Unfortunatly, it turned out that "make programs; sudo make install" was more entrenched than I realized.<br><br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
It seems really dumb to make "make programs" do something other than make<br>
programs.<br></blockquote><div><br></div><div><br>See above, that initial mistake was made long ago.<br><br>My suggestion here is to remove "programs" from any and all documentation; but accept it as an undocumented alias for building all of userland including manuals.<br><br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Surely<br>
make ; sudo make install<br>
or<br>
<span class=""> make all ; sudo make install<br></span></blockquote><div><br><br>I personally think "all" should build modules as
well; but that seems to get messy. The argument for not having
"make" default to building everything including modules is that the user needs to
select which modules to build; hence "make" prints a help message and lets the user decide.<br><br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">
</span>would be the right way to do what people misuse<br>
<span class=""> make programs ; sudo make install<br>
</span>to do.<br></blockquote><div><br></div><div>The other complication is that we need some short cuts (aka targets) to:<br><br>- build/install all but documentation - linux cross compiles apparently can't deal with documentation<br></div><div>- build/install just binaries and scripts - to speed up test builds (this one would be less of an issue if the test-build process didn't rm -rf OBJDIR)<br></div><div><br></div><div>Andrew<br><br></div></div></div></div></div>