On Mon, Apr 01, 2013 at 10:03:42PM +0200, Sam Ravnborg wrote:
> On Mon, Apr 01, 2013 at 09:18:50PM +0200, Jiri Olsa wrote:
> > Adding kbuild support into Makefile.kbuild. The 'legacy'
> > Makefile still stays untouched as it was.
>
> When readign the Kbuild file I get confused.
> the obj-y syntax
On Mon, Apr 01, 2013 at 09:18:50PM +0200, Jiri Olsa wrote:
> Adding kbuild support into Makefile.kbuild. The 'legacy'
> Makefile still stays untouched as it was.
When readign the Kbuild file I get confused.
the obj-y syntax is used for kernel built-in stuff,
and obj-m for modules.
I had expected
Adding kbuild support into Makefile.kbuild. The 'legacy'
Makefile still stays untouched as it was.
It's possible to use kbuild by running 'make -f Makefile.kbuild'
with any option supported by 'legacy' Makefile.
We now have 2 config files:
'.config' - user configured setup
'.config-detected'
Adding kbuild support into Makefile.kbuild. The 'legacy'
Makefile still stays untouched as it was.
It's possible to use kbuild by running 'make -f Makefile.kbuild'
with any option supported by 'legacy' Makefile.
We now have 2 config files:
'.config' - user configured setup
'.config-detected'
On Mon, Apr 01, 2013 at 09:18:50PM +0200, Jiri Olsa wrote:
Adding kbuild support into Makefile.kbuild. The 'legacy'
Makefile still stays untouched as it was.
When readign the Kbuild file I get confused.
the obj-y syntax is used for kernel built-in stuff,
and obj-m for modules.
I had expected
On Mon, Apr 01, 2013 at 10:03:42PM +0200, Sam Ravnborg wrote:
On Mon, Apr 01, 2013 at 09:18:50PM +0200, Jiri Olsa wrote:
Adding kbuild support into Makefile.kbuild. The 'legacy'
Makefile still stays untouched as it was.
When readign the Kbuild file I get confused.
the obj-y syntax is used
6 matches
Mail list logo
