> *Goal*: someone can go to the BOINC web site,
> click on "Built the BOINC client",
> and get cookbook for the platform and IDE of their choice.
> ("cookbook" means a complete list of instructions,
> no figuring out anything required).Wouldn't it be nice to have a two line documentation that says: If you want to build the Client please clone the git repository and run the ./build/<yourPlatform>/buildClient.sh script. This will setup all dependencies and build the Client you'll find all the files you need in dist/<yourPlatform>/. Yeah that would be nice. > > *Non-goal*: someone can explore the BOINC source tree > and figure out how to build the client. That is a non-goal for the user who just wants to build the Client for own use but what about a developer who wants to contribute to the project? How should they test if changes are working and don't break other things they didn't know about? Regards Christian _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
