Re: Do we still need pre-meson compatibility hacks?

[Michael Tokarev]

25.01.2024 14:04, Peter Maydell :
> On Thu, 25 Jan 2024 at 07:54, Paolo Bonzini <pbonzini@redhat.com> wrote:
> > Right now configure contains a couple hacks to preserve some of the semantics 
> > of the pre-meson build system:
> >
> > 1) emulation of ./configure by creating a build directory and a forwarding 
> > GNUmakefile (requested by Kevin)
> >
> > 2) creation of symlinks such as x86_64-softmmu/qemu-system-x86_64 and 
> > arm-linux-user/qemu-arm (requested by Peter)
> >
> > Neither of these are a lot of code, but if people aren't relying on them we 
> > might as well delete them. Do they have any users still?
>
> Personally I have moved away from using the old $TARGET/qemu-foo
> so I would not miss the symlinks if they went away. Can't
> speak for anybody else on that one.

Heh.  I still use `make qemu-system-arm` (or `ninja qemu-system-arm`), but only
because I haven't followed closely what's the "right" target to use.  I don't
care much which target it is exactly, but guess this is some info which needs
to be findable somewhere (again, maybe it's in the docs for a long time, and
I just need rtfm).

> I suspect that "just run configure in the source tree" is still
> popular with the kind of people who don't frequently build
> QEMU, though.

"Run configure" is popular indeed, -- configure might either be a startup script
or just something to tell which command to use.  Again, personally I don't care
much which it will be as long as I know what it is ;)

/mjt