-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use modules-file instead of generating it from config.mk and feeds.conf #781
Conversation
I am currently building with these changes cherry-picked into a private branch of the "next" branch. The goal is to prototype kernel 5.4 on the erx-sfp. One thing that I noticed, is that I have to put a commit ID into the modules file. If not, I get the following error:
It would be really cool if this code would use the HEAD of the branch if no commit-id is given. |
Running "make clean" deletes the modules file. Afterwards running make again results in
Also, it seems like that if I change the commit-id (for example in luci) in the modules file, and run make again, then the new commits are not integrated and built. |
789c95f
to
3443833
Compare
fixed in 3443833 |
Switch from defining the upstream-repos and relating commit in config.mk and feeds.conf to define all in the modules-file. The modules-files is the real file used by the build-system to setup the working checkout. It originates from the Gluon-buildsystemand some documentation is avail at https://gluon.readthedocs.io/en/latest/dev/build.html
When using the modules-file in place of config.mk and feeds.conf to define the upstream-repos, there is no need to keep the code which will synthesize it. This primarily reverts 7a72a84.
3443833
to
aed5088
Compare
Any additional feedback? |
I still haven't gotten around to testing alternative git repos. Specifically I would like to try the equivalent of src-lnk, which I have found to be very useful for prototyping |
I havn't test this, but I like the goals to be achieved by this PR. Sounds like a good Idea. |
I'm having trouble being able to use alternative git feed types. How are we supposed to be able to use the different types of feeds support by openwrt and shown here: https://openwrt.org/docs/guide-developer/feeds |
this PR is only about solving the problem described in #780 (interpreting external GIT repos from config.mk and feeds.conf to build the modules-file). In addition this PR should also fix #772. |
@pmelange can you put this into a separate issue? |
See issue #789 |
I'm going to merge this by this week, as it solves to issues and doesn't break anything. I tested it for some time in the "SAm0815-experimental" branches. |
Switch from defining the upstream-repos and relating commit in config.mk and feeds.conf to define all in the modules-file. The modules-files is the real file used by the build-system to setup the working checkout. It originates from the Gluon-buildsystemand some documentation is avail at https://gluon.readthedocs.io/en/latest/dev/build.html This also relates to * PR freifunk-berlin#781 * Issue freifunk-berlin#780 * Issue freifunk-berlin#772
When using the modules-file in place of config.mk and feeds.conf to define the upstream-repos, there is no need to keep the code which will synthesize it. This primarily reverts 7a72a84. This also relates to * PR freifunk-berlin#781 * Issue freifunk-berlin#780 * Issue freifunk-berlin#772
Switch from defining the upstream-repos and relating commit in config.mk and feeds.conf to define all in the modules-file. The modules-files is the real file used by the build-system to setup the working checkout. It originates from the Gluon-buildsystemand some documentation is avail at https://gluon.readthedocs.io/en/latest/dev/build.html This also relates to * PR freifunk-berlin#781 * Issue freifunk-berlin#780 * Issue freifunk-berlin#772
When using the modules-file in place of config.mk and feeds.conf to define the upstream-repos, there is no need to keep the code which will synthesize it. This primarily reverts 7a72a84. This also relates to * PR freifunk-berlin#781 * Issue freifunk-berlin#780 * Issue freifunk-berlin#772
Switch from defining the upstream-repos and relating commit in config.mk and feeds.conf to define all in the modules-file. The modules-files is the real file used by the build-system to setup the working checkout. It originates from the Gluon-buildsystemand some documentation is avail at https://gluon.readthedocs.io/en/latest/dev/build.html This also relates to * PR #781 * Issue #780 * Issue #772
Switch from defining the upstream-repos and relating commit in config.mk and feeds.conf to define all in the modules-file. The modules-files is the real file used by the build-system to setup the working checkout. It originates from the Gluon-buildsystemand some documentation is avail at https://gluon.readthedocs.io/en/latest/dev/build.html This also relates to * PR #781 * Issue #780 * Issue #772
Switch from defining the upstream-repos and relating commit in config.mk and feeds.conf to define all in the modules-file. The modules-files is the real file used by the build-system to setup the working checkout. It originates from the Gluon-buildsystemand some documentation is avail at https://gluon.readthedocs.io/en/latest/dev/build.html This also relates to * PR freifunk-berlin#781 * Issue freifunk-berlin#780 * Issue freifunk-berlin#772
When using the modules-file in place of config.mk and feeds.conf to define the upstream-repos, there is no need to keep the code which will synthesize it. This primarily reverts 7a72a84. This also relates to * PR freifunk-berlin#781 * Issue freifunk-berlin#780 * Issue freifunk-berlin#772
Switch from defining the upstream-repos and relating commit in config.mk and feeds.conf to define all in the modules-file. The modules-files is the real file used by the build-system to setup the working checkout. It originates from the Gluon-buildsystemand some documentation is avail at https://gluon.readthedocs.io/en/latest/dev/build.html This also relates to * PR #781 * Issue #780 * Issue #772
Switch from defining the upstream-repos and relating commit in config.mk and feeds.conf to define all in the modules-file. The modules-files is the real file used by the build-system to setup the working checkout. It originates from the Gluon-buildsystemand some documentation is avail at https://gluon.readthedocs.io/en/latest/dev/build.html This also relates to * PR freifunk-berlin#781 * Issue freifunk-berlin#780 * Issue freifunk-berlin#772
When using the modules-file in place of config.mk and feeds.conf to define the upstream-repos, there is no need to keep the code which will synthesize it. This primarily reverts 7a72a84. This also relates to * PR freifunk-berlin#781 * Issue freifunk-berlin#780 * Issue freifunk-berlin#772
55a8827 batman-adv: update to version 2022.0 911a4ba batctl: update to version 2022.0 3aa4cfb alfred: update to version 2022.0 d7adf18 Merge pull request freifunk-berlin#781 from ecsv/batadv-2022.0
The modules-file controls which code of the upstream-repos is used. With the implementation of PR #714 we added some "glue-code" to create the
modules
file from the currently used files (config.mk
,feeds.conf
).This "glue-code" works well with the official Upstream-repos but seems to have some problems with alternative repos as shown by issue #780. This PR drops the "very brittle" code and moves the repo-definitions to
modules
directly.