Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions

Jump to navigation Jump to search
Use the 'fgmeta clone' template instead of explicit 'git clone' commands for FGMeta
(→‎For the curious: the SSH way: Update, add prominent note)
(Use the 'fgmeta clone' template instead of explicit 'git clone' commands for FGMeta)
Line 57: Line 57:
  mkdir -p ~/flightgear/dnc-managed
  mkdir -p ~/flightgear/dnc-managed
  cd ~/flightgear
  cd ~/flightgear
  <nowiki>git clone https://gitlab.com/flightgear/fgmeta.git</nowiki>
  {{fgmeta clone | protocol = https}}
  cd ~/flightgear/dnc-managed
  cd ~/flightgear/dnc-managed
  ~/flightgear/fgmeta/download_and_compile.sh -s -j$(nproc)
  ~/flightgear/fgmeta/download_and_compile.sh -s -j$(nproc)
Line 99: Line 99:
  $ mkdir -p ~/flightgear
  $ mkdir -p ~/flightgear
  $ cd ~/flightgear
  $ cd ~/flightgear
  <nowiki>$ git clone -b next https://gitlab.com/flightgear/fgmeta.git</nowiki>
  $ {{fgmeta clone | protocol = https}}
You now have a fresh FGMeta clone in <tt>~/flightgear/fgmeta</tt> and your brand new <tt>download_and_compile.sh</tt> script is located in that directory. You can already try it to see the available options:
You now have a fresh FGMeta clone in <tt>~/flightgear/fgmeta</tt> and your brand new <tt>download_and_compile.sh</tt> script is located in that directory. You can already try it to see the available options:
<pre>$ ~/flightgear/fgmeta/download_and_compile.sh --help
<pre>$ ~/flightgear/fgmeta/download_and_compile.sh --help
417

edits

Navigation menu