Build from Source » History » Version 3
neels, 11/15/2016 02:29 PM
1 | 1 | neels | {{>toc}} |
---|---|---|---|
2 | |||
3 | h1. Build from Source |
||
4 | |||
5 | bq. *Before you consider building from source, be aware that there are [[Nightly Builds]] |
||
6 | available for Debian + Ubuntu platforms. These are recommended for normal users.* |
||
7 | |||
8 | Generally, Osmocom projects use autoconf/automake. |
||
9 | 2 | neels | The general pattern for building is: |
10 | 1 | neels | |
11 | <pre> |
||
12 | cd source-tree |
||
13 | autoreconf -fi |
||
14 | ./configure |
||
15 | make |
||
16 | make check |
||
17 | make install |
||
18 | </pre> |
||
19 | |||
20 | 3 | neels | The @./configure@ step may need further configuration options, and |
21 | @./configure@ will tell you which dependencies are still missing, if any. |
||
22 | See below for project specific details and troubleshooting. |
||
23 | 1 | neels | |
24 | The @make@ step may generally be sped up by using multiple CPU cores: |
||
25 | |||
26 | <pre> |
||
27 | make -j 8 |
||
28 | </pre> |
||
29 | |||
30 | We take care to make our builds parallelizable with @-j@, but in case |
||
31 | @make -j@ fails, issuing a simple @make@ could fix the problem (expecting |
||
32 | this only in libsmpp34). |
||
33 | |||
34 | |||
35 | h1. Dependencies |
||
36 | |||
37 | Which libraries are needed by various Osmocom programs is best resolved during |
||
38 | the @./configure@ step described below. This script checks for any missing |
||
39 | dependencies. |
||
40 | |||
41 | Here is a (probably incomplete) overview of dependencies between Osmocom |
||
42 | projects: |
||
43 | |||
44 | | _To build ..._ | _... you also need ..._ | |
||
45 | | osmo-bts | libosmocore, libosmo-abis, openbsc (source tree only), L1 headers depending on BTS model | |
||
46 | | osmo-pcu | libosmocore, L1 headers depending on BTS model | |
||
47 | | openbsc: osmo-nitb, osmo-bsc, osmo-sgsn, osmo-bsc_nat, osmo-bsc_mgcp | libosmocore, libosmo-abis, libosmo-netif, libosmo-sccp, libsmpp34 | |
||
48 | | openbsc: 3G osmo-cscn (branch sysmocom/iu) | libosmocore, libosmo-abis, libosmo-netif (branch sysmocom/sctp), libosmo-sccp (branch sysmocom/iu), asn1c, libasn1c, osmo-iuh | |
||
49 | | osmo-iuh | libosmocore, libosmo-netif, libosmo-sccp, asn1c, libasn1c | |
||
50 | |||
51 | h1. Download Sources |
||
52 | |||
53 | 3 | neels | The latest Osmocom sources are available from git at https://git.osmocom.org, |
54 | where each project's overview page displays the actual git URL. |
||
55 | |||
56 | The projects' repository URLs generally are of the pattern: |
||
57 | <pre>git://git.osmocom.org/project-name</pre> |
||
58 | |||
59 | For example, to verify libosmocore's git repository URL, browse to |
||
60 | https://git.osmocom.org/libosmocore/ and observe the URL shown at the |
||
61 | bottom of the page under _Clone_: @git://git.osmocom.org/libosmocore@ |
||
62 | |||
63 | To download the libosmocore sources using the @git@ client: |
||
64 | |||
65 | <pre> |
||
66 | git clone git://git.osmocom.org/libosmocore |
||
67 | </pre> |
||
68 | |||
69 | (To contribute, see [[Coding Standards#Submitting-Patches|Submitting Patches]]) |
||
70 | |||
71 | * To submit patches, see [[Gerrit]]. |
||
72 | |||
73 | * There are also Osmocom projects' clones at github, though these are merely |
||
74 | mirrors, and pull requests will be rejected by a bot. |