Skip to content
Snippets Groups Projects
Select Git revision
  • experimental default protected
  • nrb/airmax-test
  • v2023.2.4-ffs
  • nrb/ar9344-reset-sequence
  • autinerd/experimental-openwrt-24.10
  • v2023.2.3-ffs
  • v2023.2.2-ffs
  • v2023.2-ffs
  • v2023.1-ffs
  • v2022.1.4-ffs
  • feature/addMikrotikwAP
  • v2022.1.3-ffs
  • v2021.1.2-ffs
  • v2022.1.1-ffs
  • master protected
  • v2021.1.1-ffs
  • nrb/gluon-master-cpe510
  • v2021.1-ffs
  • v2020.2.3-ffs
  • nrbffs/fastd-remove-delay
  • experimental-2025-05-18
  • experimental-2025-05-18-base
  • experimental-2025-05-15
  • experimental-2025-05-15-base
  • experimental-2025-05-13
  • experimental-2025-05-13-base
  • experimental-2025-05-08
  • experimental-2025-05-08-base
  • experimental-2025-05-05
  • experimental-2025-05-05-base
  • experimental-2025-05-02
  • experimental-2025-05-02-base
  • experimental-2025-05-01
  • experimental-2025-05-01-base
  • experimental-2025-04-29
  • experimental-2025-04-29-base
  • experimental-2025-04-27
  • experimental-2025-04-27-base
  • experimental-2025-04-26
  • experimental-2025-04-26-base
40 results

basic_openwrt_config.sh

Blame
    • David Bauer's avatar
      6b22b742
      build: fix duplicate building of host-tools · 6b22b742
      David Bauer authored
      Upstream introduced two different methods for determining the state of a
      package within the OpenWrt buildsystem. While both are based around the
      md5 hash-function, one taks filename & mtime into account while the
      other one uses the actual md5 hash of the file-content.
      
      Ever wondered why Gluon suddenly took considerably longer to build?
      The messy part is how the build-system chooses which method to use. This
      is based around the AUTOREMOVE configuration. Gluon sets this variable
      conditionally when built with GLUON_AUTOREMOVE set to 1.
      
      Enter the Gluon build-system. It first compiles Lua, without the
      AUTOREMOVE configuration passed to OpenWrt. This compiles the packages
      with the old hash-method based around filename & mtime. Afterwards, it
      builds with AUTOREMOVE enabled, changing the hash-function and
      rebuilding all host-packages.
      
      Fix this by setting AUTOREMOVE for both build-processes according to the
      setting of GLUON_AUTOREMOVE.
      
      Link: https://github.com/openwrt/openwrt/commit/53a08e37437972ba0a8fbf953a93a70a6b784ef4
      
      
      
      Signed-off-by: default avatarDavid Bauer <mail@david-bauer.net>
      6b22b742
      History
      build: fix duplicate building of host-tools
      David Bauer authored
      Upstream introduced two different methods for determining the state of a
      package within the OpenWrt buildsystem. While both are based around the
      md5 hash-function, one taks filename & mtime into account while the
      other one uses the actual md5 hash of the file-content.
      
      Ever wondered why Gluon suddenly took considerably longer to build?
      The messy part is how the build-system chooses which method to use. This
      is based around the AUTOREMOVE configuration. Gluon sets this variable
      conditionally when built with GLUON_AUTOREMOVE set to 1.
      
      Enter the Gluon build-system. It first compiles Lua, without the
      AUTOREMOVE configuration passed to OpenWrt. This compiles the packages
      with the old hash-method based around filename & mtime. Afterwards, it
      builds with AUTOREMOVE enabled, changing the hash-function and
      rebuilding all host-packages.
      
      Fix this by setting AUTOREMOVE for both build-processes according to the
      setting of GLUON_AUTOREMOVE.
      
      Link: https://github.com/openwrt/openwrt/commit/53a08e37437972ba0a8fbf953a93a70a6b784ef4
      
      
      
      Signed-off-by: default avatarDavid Bauer <mail@david-bauer.net>