Setting -e in hashbang is not a good idea as users might just run it by
some other interpreter and that way removing (without noticing it) that
option.

This checks generated config after Kconfig pass if it still contains
preferences we have in files in configs directory.

This also drops some of the options in our config that are obsolete or
invalid.

CONFIG_VERSION_REPO is overwritten by setting pushed dynamically in
config by compile_pkgs so it makes no sense to have it here.

CONFIG_BUSYBOX_DEFAULT_CROND seems to be impossible to change and is
also default value that we later override with
CONFIG_BUSYBOX_CONFIG_CROND.

All PACKAGE options are not necessary. They are all enabled to 'm' but
getting them to 'y' would require a lot of works with gain that build
would in some cases failed instead of passed without that package. Not
worth it.

CONFIG_DEFAULT_TARGET_OPTIMIZATION is not applies so it is dropped here
without replacement. Same as one occurrence of CONFIG_CPU_TYPE.

This was renamed in HBL to report.

Karel Koci authored 5 years ago and Karel Koci committed 5 years ago

This locks git mirror directory when we are updating mirrors. This
should solve race condition with multiple builds failing to update
mirrors and failing that way completely.

Only update is protected. The expectation is that initialization is
happenning only once and is protected by non-existence of directory. If
there is going to be problem with initialization as well then we can add
locking as well.

This was colliding with OpenWrt's own configuration push and was kind of
hack. Replacement is to use OpenWrt's approach. That is same but in
OpenWrt configuration. To ensure that configuration is used by OpenWrt
KConfig in OWrt tree has to be added.
The new approach also simplifies some stuff because we can let KConfig
to do configuration for us. There is no need to specify specific
options to configuration in this repository. An example can be Turris
Omnia LEDS support (file target/linux/mvebu/image/Config.in):

config KERNEL_LEDS_OMNIA
	bool "Build Turris Omnia LEDS support to kernel"
	depends TARGET_mvebu
	default y if TARGET_mvebu_cortexa9_DEVICE_cznic_turris-omnia
	default n

This adds option CONFIG_KERNEL_LEDS_OMNIA that is copied to kernel
configuration as CONFIG_LEDS_OMNIA. It is available only for
TARGET_mvebu as it is part of patch for that target. In default it is
set to no. No is copied to kernel configuration as "# CONFIG_LEDS_OMNIA
is not set" and that e...

There are various changes done to configuration on top of just general
cleanup.

All constants from compile_pkgs were moved to configs as it makes sense
that they are in one location not in script.

The settings to use specific version of toolchain was removed. Now we
use upstream default toolchain version which prevents problems with some
packages not being compiled because of old toolchain is used.

All options settings support and capabilities of target were dropped as
they are overriden by target setting non the less so they make no sense.
These should be modified in OpenWrt target not in configuration.

All package settings were dropped with exception of essential packages
and package disablements.
The reason why essential packages were not dropped is to ensure that all
failed build won't be deployed. With future tests done as part of build
this file can be dropped.
And lastly we have to preserve disablement of packages to not build
them as intended.

All DEFAULT options wer...

This was missed in previous commit cd222783

This can be shared between multiple scripts so move it to centralized
file.

This moves version file generation right after clean. This ensures that
we really report OpenWrt hash and not our patch commit that is created
to extend ignore list.

This also uses different git command that has lower overhead and is
intended more for this kind of operation.

This replaces automatic hash insertion by our hash. The reason is that
default is hash of tip but we patch our feed so that hash is
effectively nonsense. This uses remote hash instead.

This does the same thing as git status but is safe for script usage. It
just goes from tip (HEAD) trough all commit hashes and requests git to
name them using symbolic link. We limit that to only references from
origin so default remote references. This is to get commit that is in
upstream instead of commit hash of tip that is patch.

This reverts commit 8da67619.

We do not use this and I consider board specific patching as a hack.

Karel Koci authored 5 years ago and Karel Koci committed 5 years ago

This is not clean patching and we do not pretend it is so just ignore
those warnings.

Karel Koci authored 5 years ago and Karel Koci committed 5 years ago

This is not clean patching and we do not pretend it is so just ignore
those warnings.

Karel Koci authored 5 years ago and Karel Koci committed 5 years ago

This is not clean patching and we do not pretend it is so just ignore
those warnings.

Disabled packages add unnecessary complexity and introduce no big gain.
Furthermore they might and do hide if package is fixed by upstream.

There are two reason why package can be disabled. Either id does not
compile because it is broken and in that case we should build it in hope
that it will be fixed. Or it might be because it just does not apply on
given board or architecture and in that case that package should be
marked as incompatible with that architecture in package itself not
somewhere outside.

This adds support for applying patches only for a specific board.
This should be a temporary solution for a regression on Mox (patch for
Omnia multi CPU DSA broke Mox Peridot-Topaz configuration).

Signed-off-by: Marek Behún <marek.behun@nic.cz>

Upstream renamed it to config.buildinfo.

They also introduced new file feeds.buildinfo. We could use that instead
of our git-hash generated file.

Configuration override options was misleading. In reality those are
options you most probably don't want to mess too much with so let's call
them rather advanced options.

This also moves PUBLISH_BRANCH in example configuration file to
section: don't mess with. This is because now we provide it from
defaults and user just should not mess with it unless he know what he is
doing.

OpenWRT commit to be used is specified in feeds.conf file with rest of
feeds now so it makes not sense to overwrite it. This is just confusing
without any real gain in here. You can always modify feeds.conf file to
achieve the same.

Configuration override options was misleading. In reality those are
options you most probably don't want to mess too much with so let's call
them rather advanced options.

This also moves PUBLISH_BRANCH in example configuration file to
section: don't mess with. This is because now we provide it from
defaults and user just should not mess with it unless he know what he is
doing.

OpenWRT commit to be used is specified in feeds.conf file with rest of
feeds now so it makes not sense to overwrite it. This is just confusing
without any real gain in here. You can always modify feeds.conf file to
achieve the same.

Thanks to midnightmagic, who pointed out it on IRC channel #turris on Freenode

Karel Koci authored 5 years ago and Josef Schlehofer committed 5 years ago

Parameter -e is now obsolete and by default, we want to build everything.
Removed it from turris-build.conf.example

Because of that we or users don't need to select packages in make
menuconfig which we or they want to build. Now each package will be selected
but not compiled which depends on user choice.

Also, compile_pkgs shouldn't be run under root or with sudo. Do it as
normal user.

Thanks to midnightmagic, who pointed out it on IRC channel #turris on Freenode

Karel Koci authored 5 years ago and Josef Schlehofer committed 5 years ago

Parameter -e is now obsolete and by default, we want to build everything.
Removed it from turris-build.conf.example

Because of that we or users don't need to select packages in make
menuconfig which we or they want to build. Now each package will be selected
but not compiled which depends on user choice.

Also, compile_pkgs shouldn't be run under root or with sudo. Do it as
normal user.

This is more appropriate naming for Turris 1.x routers because otherwise
just plain turris is confusing.

This is more appropriate naming for Turris 1.x routers because otherwise
just plain turris is confusing.

This should make much more clearer what are usable and what are not
configuration options.

This should make much more clearer what are usable and what are not
configuration options.