busybox-w32/scripts/kconfig, branch tildeA mirror of https://github.com/rmyorston/busybox-w32.git
https://git.lua4.win/busybox-w32/atom?h=tilde2021-06-07T10:34:06+00:00Merge branch 'busybox' into merge2021-06-07T10:34:06+00:00Ron Yorstonrmy@pobox.com2021-06-07T10:34:06+00:00urn:sha1:abe872e2a0342357a5608342cb2892e94027b3e7build system: use SOURCE_DATE_EPOCH for timestamp if available2021-06-05T16:13:00+00:00Paul Spoorenmail@aparcar.org2021-05-13T21:39:05+00:00urn:sha1:947a22b33262c93e5c50286b723b9086a33a4c1f
The SOURCE_DATE_EPOCH is an effort of the Reproducible Builds
organization to make timestamps/build dates in compiled tools
deterministic over several repetitive builds.
Busybox shows by default the build date timestamp which changes whenever
compiled. To have a reasonable accurate build date while staying
reproducible, it's possible to use the *date of last source
modification* rather than the current time and date.
Further information on SOURCE_DATE_EPOCH are available online [1].
This patch modifies `confdata.c` so that the content of the
SOURCE_DATE_EPOCH env variable is used as timestamp.
To be independent of different timezones between builds, whenever
SOURCE_DATE_EPOCH is defined the GMT time is used.
[1]: https://reproducible-builds.org/docs/source-date-epoch/
Signed-off-by: Paul Spooren <mail@aparcar.org>
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
Merge branch 'busybox' into merge2021-05-14T07:17:12+00:00Ron Yorstonrmy@pobox.com2021-05-14T07:17:12+00:00urn:sha1:a3f5a1b7f4275f713acf22f534f95c0da8392e53fix "warning array subscript has type 'char'"2021-04-14T17:12:43+00:00Denys Vlasenkovda.linux@googlemail.com2021-04-14T17:12:43+00:00urn:sha1:1a45b2ccea94b0fc123798f276a0801413597880
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
.gitignore: support building on Windows2021-02-21T10:35:21+00:00Johannes Schindelinjohannes.schindelin@gmx.de2021-02-20T21:33:16+00:00urn:sha1:379e128a3a4f5343cbd4a9f1be3538cf76af82e2
These items are already listed, albeit without `.exe` suffix.
Presumably, this is because BusyBox-w32 is traditionally cross-compiled
on Linux.
However, we are about to introduce a CI build definition that builds
BusyBox-w32 in MSYS2 (using mingw-w64-gcc), meaning that those
executables might very well exist _with_ `.exe` suffix.
Let's ignore those, too.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
win32: fixes to build on Windows/MSYS2/mingw-w642021-02-21T09:51:08+00:00Ron Yorstonrmy@pobox.com2021-02-20T13:07:14+00:00urn:sha1:4bca7987f38b24867d93efc4a11a1ef661734056
To investigate GitHub issue #200 it was necessary to perform
build on Window using the MSYS2/mingw-w64 toolchain. This
threw up some issues:
- The settings for _WIN32_WINNT and __USE_MINGW_ANSI_STDIO differ
from those in Fedora resulting in compiler errors and warnings.
Force the defaults I'm used to.
- The workaround to allow native compilation of mconf.c was broken
by a subsequent upstream change. Make it work again.
Merge branch 'busybox' into merge2019-01-10T08:38:15+00:00Ron Yorstonrmy@pobox.com2019-01-10T08:38:15+00:00urn:sha1:f99a280743e877c14ee90a3f9e93a34ca3476a27build system: fix compiler warnings2019-01-06T19:12:16+00:00Denys Vlasenkovda.linux@googlemail.com2019-01-06T19:12:16+00:00urn:sha1:4bdc914ff97df0cea8d2c7b42bf7f57d5ebb8dcb
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
Merge branch 'busybox' into merge2018-04-09T07:50:34+00:00Ron Yorstonrmy@pobox.com2018-04-09T07:50:34+00:00urn:sha1:921c1ab66bad54d4ad8591bb74e41ac985248496scripts/kconfig/mconf.c: survive is SIGWINCH is not defined2018-04-06T17:05:53+00:00Denys Vlasenkovda.linux@googlemail.com2018-04-06T17:05:53+00:00urn:sha1:6b6a3d9339f1c08efaa18a7fb7357e20b48bdc95
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>