From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: tommy@gentoo.org
Subject: Re: [gentoo-dev] Re: [RFC] multilib-build.eclass and restricting unsupported ABIs
Date: Sun, 3 Mar 2013 17:35:46 +0100 [thread overview]
Message-ID: <20130303173546.0ce7ab31@portable> (raw)
In-Reply-To: <51337A06.20400@gentoo.org>
On Sun, 03 Mar 2013 17:27:50 +0100
Thomas Sachau <tommy@gentoo.org> wrote:
> Alexis Ballier schrieb:
> > On Sun, 03 Mar 2013 16:47:43 +0100
> > Thomas Sachau <tommy@gentoo.org> wrote:
> >
> >> Alexis Ballier schrieb:
> >>> On Sun, 03 Mar 2013 14:02:58 +0100
> >>> Thomas Sachau <tommy@gentoo.org> wrote:
> >>>>
> >>>> Once the eclass has per-ABI header
> >>>
> >>> I think this is needed.
> >>>
> >>>> and binaries support,
> >>>
> >>> but here, could you enlighten me on its use cases ? I can't
> >>> imagine why having multi binaries support would be useful.
> >>>
> >>> Alexis.
> >>>
> >>
> >>
> >> At least some binaries do have abi-specific output, which is used
> >> by other applications. As a good example of this, have a look at
> >> qmake and qmake based build systems.
> >
> > hmm, qmake doesnt seem to be the perfect example: how do you handle
> > this?
> >
> > - install qmake-${abi}
>
> ok
>
> > - ln -s qmake-${DEFAULT_ABI} qmake
>
> Just the same as with headers:
>
> You dont symlink the headers for the default ABI, but instead a
> wrapper is placed, which does then call/include the real target, so
> in this case, qmake is then a symlink to the abiwrapper, which does
> execute the real abi-specific binary, depending on the current ABI.
> We can of course place this abiwrapper in every place, where it is
> needed instead of the symlink, but having one central and package
> provided wrapper instead is easier to maintain and update.
>
> > - modify eqmake4 to call the right qmake when doing multilib?
>
> not needed at all (with multilib-portage), since when any package
> calls qmake to get any abi-specific details, the abiwrapper executes
> the binary, that matches the ABI and you get the right details for
> your ABI.
>
Indeed, nice idea. The wrapper can just call argv[0]-${ABI} or argv[0]
if ABI is unset or argv[0]-${ABI} does not exist.
Do you install this abiwrapper with multilib-portage? What would you
think about splitting it and adding such a package to the tree?
Alexis.
next prev parent reply other threads:[~2013-03-03 16:36 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 23:02 [gentoo-dev] [RFC] multilib-build.eclass and restricting unsupported ABIs Michał Górny
2013-03-03 11:41 ` Alexis Ballier
2013-03-03 12:37 ` Michał Górny
2013-03-03 13:02 ` [gentoo-dev] " Thomas Sachau
2013-03-03 15:24 ` Alexis Ballier
2013-03-03 15:47 ` Thomas Sachau
2013-03-03 16:10 ` Alexis Ballier
2013-03-03 16:27 ` Thomas Sachau
2013-03-03 16:35 ` Alexis Ballier [this message]
2013-03-03 21:39 ` Thomas Sachau
2013-03-04 9:42 ` Alexis Ballier
2013-03-03 16:58 ` Michał Górny
2013-03-03 17:18 ` Alexis Ballier
2013-03-03 22:25 ` Michał Górny
2013-03-04 10:02 ` Alexis Ballier
2013-03-04 20:17 ` Thomas Sachau
2013-03-07 16:29 ` Alexis Ballier
2013-03-07 18:59 ` Thomas Sachau
2013-03-08 3:17 ` Davide Pesavento
2013-03-08 14:33 ` Thomas Sachau
2013-03-08 4:47 ` Michał Górny
2013-03-08 11:13 ` Alexis Ballier
2013-03-08 11:10 ` Alexis Ballier
2013-03-08 14:44 ` Thomas Sachau
2013-03-09 10:45 ` Alexis Ballier
2013-03-04 20:49 ` Michał Górny
2013-03-04 22:21 ` Thomas Sachau
2013-03-04 22:49 ` Michał Górny
2013-03-08 18:25 ` [gentoo-dev] " Steven J. Long
2013-03-07 16:25 ` [gentoo-dev] " Alexis Ballier
2013-03-08 16:30 ` Michał Górny
2013-03-09 10:10 ` Alexis Ballier
2013-03-10 13:42 ` Michał Górny
2013-03-15 10:32 ` Alexis Ballier
2013-03-15 14:25 ` Michał Górny
2013-03-03 16:00 ` Chí-Thanh Christopher Nguyễn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130303173546.0ce7ab31@portable \
--to=aballier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=tommy@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox