blob: de3379909c05baf452b8fbdfad07897dad78f3ba (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
|
## SECTION=project_name
#
# rules/project-name.in
#
# Copyright (C) 2002-2006, 2009 by Robert Schwebel <r.schwebel@pengutronix.de>
#
comment "------------------------------------"
menu "Project Name & Version "
comment "Project Name & Version "
config PROJECT_VENDOR
string
prompt "Vendor Name"
help
Type in here your favorite vendor name. It gets displayed
whenever your system starts.
config PROJECT
string
prompt "Project Name"
help
Name of this project; each PTXdist "Project" specifies a
unique configuration for an Embedded Linux project.
config PROJECT_VERSION
string
prompt "Project Version"
default "-${PTXDIST_BSP_AUTOVERSION}"
help
The version of your project.
The string is supposed to start with a "-".
comment "------------------------------------"
comment "pre-built package handling"
comment "------------------------------------"
config PROJECT_CREATE_DEVPKGS
bool
prompt "create pre-built archives"
help
Enable the creation of pre-built package archives. Read the
"How to become a PTXdist Guru" documentation for further details.
config PROJECT_USE_DEVPKGS
bool
select HOST_CHRPATH
prompt "use pre-built archives"
help
Use pre-built package archives to build or re-build the project if
corresponding package archives with the same configuration are found.
config PROJECT_DEVPKGDIR
string
prompt "pre-built archive directory"
depends on PROJECT_USE_DEVPKGS
default "/opt/OSELAS.BSP/${PTXCONF_PROJECT_VENDOR}/OSELAS.BSP-${PTXCONF_PROJECT_VENDOR}-${PTXCONF_PROJECT}${PTXCONF_PROJECT_VERSION}"
help
This entry defines the path to a directory where pre-built archives
are expected.
config PROJECT_DEVMIRROR
string
prompt "Mirror for pre-built archives"
depends on PROJECT_USE_DEVPKGS
help
Enter a URL where *-dev.tar.gz packages can be downloaded
Use: ptxdist getdev
comment "------------------------------------"
comment "license information handling"
comment "------------------------------------"
config PROJECT_CHECK_LICENSES
bool
prompt "check licenses during normal build"
help
If this is enabled <pkg>.report is build during the normal build
process. As a result all specified md5 sums for license files are
verified.
config PROJECT_GENERATE_REPORTS
bool
prompt "generate reports with all relevant images"
help
If this es enabled <image>.reports is build before the
corresponding image. This is only relevant for images that are
build from packages since the document covers all packages that
are part of the image.
config PROJECT_STORE_SOURCE_GIT_COMMITS
bool
prompt "query and store git commits for source archives"
help
PTXdist usually downloads source archives. But if that comes from a
git server then it can be possible to determine the corresponding git
commit.
If enabled, the git commit will be determined if possible and stored
with the source archive.
comment "------------------------------------"
comment "reproducible builds"
comment "------------------------------------"
choice
prompt "SOURCE_DATE_EPOCH timestamps source"
default REPRODUCIBLE_TIMESTAMP_PTXDIST
help
Use the specifies source to provide a stable SOURCE_DATE_EPOCH.
This helps making builds more reproducible. See
https://reproducible-builds.org/specs/source-date-epoch/ for more
details about SOURCE_DATE_EPOCH.
For development this can be disabled in 'ptxdist setup'.
config REPRODUCIBLE_TIMESTAMP_PTXDIST
bool
prompt "ptxdist version"
help
Use the year and month of the PTXdist version to generated the
timestamp.
config REPRODUCIBLE_TIMESTAMP_TOOLCHAIN
bool
prompt "toolchain version"
help
Use the year and month of the toolchain version to generated the
timestamp. This only works for OSELAS.Toolchain.
This is useful to keep the timestamp stable across PTXdist
version updates. When a toolchain update happens, then the
compiler will probably produce different code, so a different
timestamp is ok as well.
config REPRODUCIBLE_TIMESTAMP_CUSTOM
bool
prompt "custom timestamp"
endchoice
config REPRODUCIBLE_TIMESTAMP
string
default "toolchain" if REPRODUCIBLE_TIMESTAMP_TOOLCHAIN
default "ptxdist" if REPRODUCIBLE_TIMESTAMP_PTXDIST
default "custom" if REPRODUCIBLE_TIMESTAMP_CUSTOM
if REPRODUCIBLE_TIMESTAMP_CUSTOM
config REPRODUCIBLE_TIMESTAMP_STRING
string
prompt "custom timestamp"
help
Supply a custom fake timestamp to be injected to the build.
The timestamp is passed to 'date --date', e.g. "2018-11-01 UTC".
Note: the timestamp should contain include the timezone.
Otherwise timezone changes may produce different results.
endif
endmenu
|
