I use many libraries, I learned bjam because I use boost in Windows and linux. I use ACE, fltk, and compile many. Overall, I do not fully trust any convention of INSTALL.txt and README.txt. Sometimes they have compilation instructions in README (fltk). Or in ACE-INSTALL.html. Or on the website. Or a text file refers to another source. Or under program option help (cmake openalsoft). If I have a configure, then I don't even read anything. ./configure --help to see options. ./configure, make, sudo make install If not, then I look at any binaries or special files in the directory that tell me what type of build system it uses, or at any text files. I look for "To install, do this: ...". I usually first ignore html files, since I can't vi them. (Sometimes I'm on the console or network.) Vladimir Prus wrote:
Chris wrote:
Hi, just some comments, I'm a user.
Maybe you can make a file configure.txt, or configure-gnu-deprecated.txt non-executable and then when a person runs: ./configure<tab> they come up with that file, and in one it is says: run bjam That would not confuse me.
Many Linux project have file named INSTALL or INSTALL.txt (I believe GNU project have the as a matter of policy, even). Would that be sufficiently discoverable?
- Volodya
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost