Write scripts to set up development environments #475
Comments
@tst-lsavoie Looking at the jira tasks for this one:
Does the script compile the code? Also, can't assign this to me on here. |
Not answering any of your questions, but there's a script that does a lot of this for the Docker builds, which may save you some time: https://github.com/google/earthenterprise/pull/412/files#diff-00e002f840808e80a2c02dc2b9d5a19f |
@tst-basilhuffman the script shouldn't clone or compile the code. It should just install all the prerequisites for building. The way I envision it is that we would provide a link to the script on the main README.md and someone could download just the script, run it, and have a system ready for development. They would still need to clone the repo and build it, but everything up to that point would be taken care of. Optionally, you could include the clone step, but that becomes tricky because some people will want to clone the main repo and some will want to clone their own fork. |
Cloning doesn't seem to be much of a problem, especially cloning main. Compiling just isn't practical or relevant here I suppose. |
@tst-lsavoie @tst-ccamp It is a safe assumption that CentOS/RHEL users have some form of window manager installed, correct? |
Not necessarily. GEE Server can be installed without a window manager and I don't think the build environment requires it. I think it would be best to not require a UI. |
* Aadded build scripts * Created a root-level directory called scripts and moved top level scripts there * Modified BUILD.md to reference script
Instead of providing building instructions on the wiki we should write scripts for each platform that install the required dependencies for that platform. This will make it easier for developers to set up machines to build GEE. Also update the build documentation to refer to the new scripts. We have scripts that do this in our docker files, so that is a good place to start.
The text was updated successfully, but these errors were encountered: