On Wed, Feb 28, 2024 at 13:36:00 +0100, Oliver Steffen wrote:
> Add a new keyword, "depends", to the module definition syntax
> used in Makefile.core.def. This allows specifying explicit module
> dependencies together with the module definition.
>
> Do not track the &qu
Add a new keyword, "depends", to the module definition syntax
used in Makefile.core.def. This allows specifying explicit module
dependencies together with the module definition.
Do not track the "extra_deps.lst" file in the repository anymore,
it is now auto-generated.
On Thu, Feb 22, 2024 at 14:32:31 +0100, Oliver Steffen wrote:
> Add a new keyword, "depends", to the module definition syntax
> used in Makefile.core.def. This allows specifying explicit module
> dependencies together with the module definition.
>
> Do not track the &qu
Adding Vladimir...
On Thu, Feb 22, 2024 at 02:32:31PM +0100, Oliver Steffen wrote:
> Add a new keyword, "depends", to the module definition syntax
> used in Makefile.core.def. This allows specifying explicit module
> dependencies together with the module definition.
&
Add a new keyword, "depends", to the module definition syntax
used in Makefile.core.def. This allows specifying explicit module
dependencies together with the module definition.
Do not track the "extra_deps.lst" file in the repository anymore,
it is now auto-generated.
Quoting Julian Andres Klode (2023-12-08 18:29:52)
> On Fri, Dec 08, 2023 at 01:20:37PM +0100, Daniel Kiper wrote:
> > On Wed, Dec 06, 2023 at 05:39:53PM +0100, Daniel Kiper wrote:
> > > On Wed, Dec 06, 2023 at 04:39:29PM +0100, Olaf Hering wrote:
> > > > Wed, 6 Dec 2023 16:24:53 +0100 Daniel Kiper
On Fri, Dec 08, 2023 at 01:20:37PM +0100, Daniel Kiper wrote:
> On Wed, Dec 06, 2023 at 05:39:53PM +0100, Daniel Kiper wrote:
> > On Wed, Dec 06, 2023 at 04:39:29PM +0100, Olaf Hering wrote:
> > > Wed, 6 Dec 2023 16:24:53 +0100 Daniel Kiper :
> > >
> > > > Could you provide us exact steps to reprod
On Wed, Dec 06, 2023 at 05:39:53PM +0100, Daniel Kiper wrote:
> On Wed, Dec 06, 2023 at 04:39:29PM +0100, Olaf Hering wrote:
> > Wed, 6 Dec 2023 16:24:53 +0100 Daniel Kiper :
> >
> > > Could you provide us exact steps to reproduce the problem?
> >
> > Something like this?
> >
> > mkdir .b
> > cd $_
On Wed, Dec 06, 2023 at 04:39:29PM +0100, Olaf Hering wrote:
> Wed, 6 Dec 2023 16:24:53 +0100 Daniel Kiper :
>
> > Could you provide us exact steps to reproduce the problem?
>
> Something like this?
>
> mkdir .b
> cd $_
> ../grub-src-dir/configure [options]
Ugh, yeah, the file is missing in this c
Wed, 6 Dec 2023 16:24:53 +0100 Daniel Kiper :
> Could you provide us exact steps to reproduce the problem?
Something like this?
mkdir .b
cd $_
../grub-src-dir/configure [options]
A brief look at the sources indicates the new file could be generated during
build, with "echo content > $@".
Ola
Hi Olaf,
On Wed, Dec 06, 2023 at 09:19:06AM +0100, Olaf Hering wrote:
> Thu, 16 Nov 2023 16:37:38 +0100 Oliver Steffen :
>
> > +syminfo.lst: gensyminfo.sh kernel_syms.lst extra_deps.lst $(MODULE_FILES)
> > + cat kernel_syms.lst extra_deps.lst > $@.new
>
> There are rules to create gensyminfo.sh
Thu, 16 Nov 2023 16:37:38 +0100 Oliver Steffen :
> +syminfo.lst: gensyminfo.sh kernel_syms.lst extra_deps.lst $(MODULE_FILES)
> + cat kernel_syms.lst extra_deps.lst > $@.new
There are rules to create gensyminfo.sh and kernel_syms.lst, but there is no
rule to create extra_deps.lst.
As a resul
The build system deduces inter-module dependencies from the symbols
required and exported by the modules. This works well, except for some
rare cases where the dependency is indirect or hidden. A module might
not make use of any function of some other module, but still expect its
functionality to
The build system deduces inter-module dependencies from the symbols
required and exported by the modules. This works well, except for some
rare cases where the dependency is indirect or hidden. A module might
not make use of any function of some other module, but still expect its
functionality to
The build system deduces inter-module dependencies from the symbols
required and exported by the modules. This works well, except for some
rare cases where the dependency is indirect or hidden. A module might
not make use of any function of some other module, but still expect its
functionality to
Adding Vladimir...
On Thu, Oct 19, 2023 at 04:50:10AM -0700, Oliver Steffen wrote:
> Quoting Daniel Axtens (2023-10-05 08:07:47)
> > (Unless anything has changed dramatically in the last year:) Dependencies
> > are calculated automatically on the basis of symbols that you use in your
> > module.
> There is the problem with the new bli module, that it requires the
> part_gpt module to be loaded beforehand, but the module dependency list
> for bli is emplty (see moddep.lst).
>
> The part_gpt module only exports one function,
> grub_gpt_partition_map_iterate(). This is not used in the bli m
Quoting Daniel Axtens (2023-10-05 08:07:47)
> (Unless anything has changed dramatically in the last year:) Dependencies are
> calculated automatically on the basis of symbols that you use in your module.
> If you look at genmoddep.awk and work out from there you can get a handle on
> the process
(Unless anything has changed dramatically in the last year:) Dependencies are
calculated automatically on the basis of symbols that you use in your module.
If you look at genmoddep.awk and work out from there you can get a handle on
the process. If you only use symbols provided by the ‘kernel’,
Hi,
Is there a way to specify dependencies for a module? As in a list of
other modules that need to be loaded before?
I found a macro named GRUB_MOD_DEP in dh.h, but when I use it in the
module's .c file I get errors about a missing .moddeps section. It also
does not seem to be in use anywhere.
20 matches
Mail list logo
