Project

General

Profile

DeprecatedReplicant60SourceCode » History » Version 6

Wolfgang Wiedmeyer, 03/17/2017 08:02 PM
typo

1 1 Wolfgang Wiedmeyer
h1. Replicant source code
2
3
h2. Browsing the source code
4
5
The Replicant source code is currently hosted by the "FSF":https://www.fsf.org/ at: "git.replicant.us":https://git.replicant.us/replicant
6
7
There is one branch per Replicant version, such as @replicant-2.2@.
8
9
h2. Disk space
10
11 6 Wolfgang Wiedmeyer
Before downloading the Replicant source code, make sure there is a considerable amount of disk space left on the drive you intend to build Replicant on.
12 5 Wolfgang Wiedmeyer
It is advised to have 60-70GiB available for the Replicant source code and the produced files for one device. If you intend to build for multiple devices, every additional device will need ca. 17GiB.
13 1 Wolfgang Wiedmeyer
14
h2. Source tree root folder
15
16
The path to the source tree root folder *must not contain spaces*.
17
18
h2. Installing the repo tool
19
20
To be able download the complete source code, the "@repo@ tool":https://android.googlesource.com/tools/repo needs to be installed. The distribution you are using may already have the tool packaged and it may already been installed as part of the [[BuildDependenciesInstallation|Build dependencies installation]].
21
22
If the @repo@ tool is not available on your system, you can download and install it locally:
23
24
<pre>
25
mkdir tools
26
cd tools
27
wget https://commondatastorage.googleapis.com/git-repo-downloads/repo
28
chmod a+x repo
29
cd ../
30
</pre>
31
32
In the following, the local installation in @../tools/repo@ is assumed. If you have installed @repo@ from your system's package manager, replace
33
34
<pre>
35
../tools/repo
36
</pre>
37
38
with just
39
40
<pre>
41
repo
42
</pre>
43
44
at the beginning of the following commands.
45
46
h2. Initializing the repository
47
48
The source manifest is the list of all the git repositories that are present in the Replicant tree.
49
Each Replicant version has a dedicated branch with the proper source manifest.
50
51 2 Wolfgang Wiedmeyer
h3. Replicant 6.0 release version
52
53
<pre>
54
mkdir replicant-6.0
55
cd replicant-6.0
56
../tools/repo init -u https://git.replicant.us/replicant/manifest.git -b replicant-6.0
57
</pre>
58
59 1 Wolfgang Wiedmeyer
h3. Replicant 6.0 development version
60
61
<pre>
62
mkdir replicant-6.0-dev
63
cd replicant-6.0-dev
64
../tools/repo init -u https://git.replicant.us/replicant/manifest.git -b replicant-6.0-dev
65
</pre>
66
67
h3. Replicant 4.2
68
69
<pre>
70
mkdir replicant-4.2
71
cd replicant-4.2
72
../tools/repo init -u https://git.replicant.us/replicant/manifest.git -b replicant-4.2
73
</pre>
74
75
h3. Replicant 4.0
76
77
<pre>
78
mkdir replicant-4.0
79
cd replicant-4.0
80
../tools/repo init -u https://git.replicant.us/replicant/manifest.git -b replicant-4.0
81
</pre>
82
83
h3. Replicant 2.3
84
85
<pre>
86
mkdir replicant-2.3
87
cd replicant-2.3
88
../tools/repo init -u https://git.replicant.us/replicant/manifest.git -b replicant-2.3
89
</pre>
90
91
h3. Replicant 2.2
92
93
<pre>
94
mkdir replicant-2.2
95
cd replicant-2.2
96
../tools/repo init -u https://git.replicant.us/replicant/manifest.git -b replicant-2.2
97
</pre>
98
99
h2. Downloading/Updating the source code
100
101
Now that you have configured @repo@, you can start downloading Replicant sources for the desired version.
102
103
*This step is very long and can take hours to complete!*
104
105
<pre>
106
../tools/repo sync
107
</pre>
108
109 4 Wolfgang Wiedmeyer
Once the source code is ready, you need to get the prebuilt applications (they are downloaded from F-Droid). Since Replicant 6.0, the prebuilt applications are checked if they were signed with the "F-Droid signing key":https://f-droid.org/wiki/page/Release_Channels_and_Signing_Keys. The signing key can be retrieved and added to your GPG keyring using:
110 2 Wolfgang Wiedmeyer
111
<pre>
112
gpg --recv-key 7A029E54DD5DCE7A
113
</pre>
114
115
Then you can download the prebuilts:
116
117 1 Wolfgang Wiedmeyer
<pre>
118
vendor/replicant/get-prebuilts
119
</pre>
120
121
You must redo these steps each time you want to sync your tree, in order to keep it up to date. Future syncs are faster than the first one.