[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PULL 04/10] build: fix device module builds
|
From: |
Gerd Hoffmann |
|
Subject: |
Re: [PULL 04/10] build: fix device module builds |
|
Date: |
Fri, 3 Jul 2020 12:25:41 +0200 |
On Fri, Jul 03, 2020 at 11:01:43AM +0200, Claudio Fontana wrote:
> On 7/2/20 2:20 PM, Gerd Hoffmann wrote:
> > See comment. Feels quite hackish. Better ideas anyone?
>
> A better idea could be to investigate what and why gets into the variable.
I see paths prefixed by "../", which seems to come from recursing into
target directories and not properly handling -m there.
I think this stop-gap will do the job fine as long as we don't have
target-specific modules.
With the pending switch to a meson-based build system which I hope
simplifies all this I didn't feel like investing too much effort into
finding the real root cause. Debugging the Makefiles is a PITA ...
I'm open to any hints though.
take care,
Gerd
[PULL 03/10] qdev: device module support, Gerd Hoffmann, 2020/07/02
[PULL 05/10] ccid: build smartcard as module, Gerd Hoffmann, 2020/07/02
[PULL 01/10] module: qom module support, Gerd Hoffmann, 2020/07/02
[PULL 06/10] usb: build usb-redir as module, Gerd Hoffmann, 2020/07/02
[PULL 10/10] chardev: enable modules, use for braille, Gerd Hoffmann, 2020/07/02
[PULL 08/10] vga: build virtio-gpu only once, Gerd Hoffmann, 2020/07/02
[PULL 07/10] vga: build qxl as module, Gerd Hoffmann, 2020/07/02
[PULL 09/10] vga: build virtio-gpu as module, Gerd Hoffmann, 2020/07/02