Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions

Jump to navigation Jump to search
m
→‎Compilation errors: fix tinny typo inside a big and nice article
m (→‎Compilation errors: fix tinny typo inside a big and nice article)
Line 69: Line 69:


===Compilation errors===
===Compilation errors===
Here we are, no fear, if you wish to use programs from the cvs/svn repositories, you will face anytime compilation errors that will prevent you to have a working copy of one or more of the programs provided by this script. What can be the causes that prevent us from a successful compiling ? as fas as I know this:
Here we are, no fear, if you wish to use programs from the cvs/svn repositories, you will face anytime compilation errors that will prevent you to have a working copy of one or more of the programs provided by this script. What can be the causes that prevent us from a successful compiling ? as far as I know this:
# Software developers introduce a new functionality with a new piece of code that prevents the compilation under your architecture, this can happen working with cvs/svn sources.
# Software developers introduce a new functionality with a new piece of code that prevents the compilation under your architecture, this can happen working with cvs/svn sources.
# The program refuses to compile because of a divergence in the libraries it depends. For example can happen the Flightgear does not compile because osg has been modified, while osg itself compiles fine, fg wont.
# The program refuses to compile because of a divergence in the libraries it depends. For example can happen the Flightgear does not compile because osg has been modified, while osg itself compiles fine, fg wont.
136

edits

Navigation menu