Great. Go ahead and try building it and then go to the test and troubleshooting topic
Most of the time, you’ll follow the instructions for building the application that are found in the project’s build instructions. If you don’t know how to build the application or don’t have the build instructions, or both, here are several things you can try:
Check availability of build instructions
Build instructions, which often specify the application dependencies and prerequisites are sometimes available at one of the following locations. Check each to see if they are useful or applicable to you either in part or in whole:
- Project web page
- GitHub home page of the project
- Project README file/install script
- Intel x86 Docker files
- Check if the community has an external CI engine, such as Travis or Jenkins
Often, build instructions can be interpreted from the build logs or the travis.yaml file.
Check for project specific dependency lists in the source code
This varies from project to project and to a large extent depends on the underlying language in which the source is written. Some examples:
- Gemfile (Ruby Projects)
- Requirements.txt (Python projects)
- package.json (Node.js projects)
- Makefile (C/C++ projects)
- Install common dependencies
This includes the common set that may or may not have been covered in in the previous bullet and includes build essentials such as gcc/g+++, make, node.js & npm (for Node.js packages), ruby/ruby-dev (for Ruby packages) and so on.
- Trial and error
This is generally the last and final step. Try what you were able to find and install using the recommendations above and attempt to build the package. Other dependencies will be identified and installed if the build fails.