That sounds good, except I'd give the directories clearer names, like builds/win_vs2010 builds/mac_xcode_60 builds/win_mingw packages/win_installshield_2011 packages/mac_xcode_60
Also, and maybe more importantly, the documentation needs to be improved. Someone wanting to build the BOINC client would start by looking at http://boinc.berkeley.edu/trac/wiki/CompileClient not by poking around the source tree. If they find clear instructions here, it doesn't really matter where the build files. This document is currently deficient. E.g. the instructions for building the client on Linux are mixed up with stuff about how to install and run the client, which doesn't belong here. Also, there are no references about how to build the Win client with MinGW. -- D On 11/30/2015 1:13 PM, Rom Walton wrote:
Howdy Folks, Our source tree directory structure is looking a little unwieldy and requires somebody to hunt around for project files if they are not already familiar with the BOINC system. How does everyone feel about moving the various IDE project files, platform build scripts, and CI build scripts to a 'builds' directory? For instance: * ./win_build would be moved to ./builds/vs2010 * ./mac_build would be moved to ./builds/xc60 * ./build and ./mac3rdParty would be moved too ./builds/travis-ci. * ./xcompile would be moved to ./builds/xcompile. How does everyone feel about moving the installer project files to packages? For instance: * ./win_build/installerv2 would be moved to ./packages/is2011 * ./mac_installer would be moved to ./packages/xc60 Thoughts? ----- Rom _______________________________________________ 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.
_______________________________________________ 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.
