From: Ned Ludd <solar@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Re: Cross Wrappers
Date: Mon, 23 Jun 2008 07:37:52 -0700 [thread overview]
Message-ID: <1214231872.17143.43.camel@media> (raw)
In-Reply-To: <200806220612.34908.vapier@gentoo.org>
On Sun, 2008-06-22 at 06:12 -0400, Mike Frysinger wrote:
> On Sunday 22 June 2008, Ned Ludd wrote:
> > On Sat, 2008-06-21 at 23:29 -0400, Mike Frysinger wrote:
> > > On Saturday 21 June 2008, Ned Ludd wrote:
> > > for the configure tests, ive been meaning to investigate switching over
> > > to a config.site rather than exporting them through the environment ...
> >
> > I'll see what I can snag from here.
> > https://dev.openwrt.org/browser/trunk/include/site (hate traq)
> > Any tips/links to some others?
>
> it's just an idea i had floating around. havent actually looked into
> implementation details. but if another project is already maintaining the
> site files, then we should push our little differences to them and then just
> start using their work ;).
> > > for the CHOST, how about checking $0 ? so people can symlink like:
> > > x86_64-pc-linux-gnu-emerge and then they can just run that without
> > > needing anything set in the
> > > environment ... that's how i generally multiplex my cross scripts for
> > > multiple targets.
> >
> > I have it right now as emerge-CHOST.
> > I figured the logic there that CHOST-* should be mostly
> > reserved for the toolchain, plus it's easier for me to emerge-\t\t and
> > pull in the right wrapper foo for whatever I'm working on.
>
> i think having it all be CHOST- prefixed rather than suffixed is better for
> consistency. or just provide both :).
done.
> > When you run emerge-wrapper --init
> > it sets up all the symlink love which would probably be run a
> > pkg_postinst().
>
> i mean when you do `crossdev FOO`, it'll create symlinks in /usr/bin/ to the
> wrappers already ... no need for the user to run any other commands in the
> default case ...
>
> cant really divine what targets need what love from a pkg_postinst()
That seems logical moving forward. But for ppl who installed crossdev
before "next-release" benefit from being able to quickly have everything
initialized without having to crossdev merge everything again.
> > > we could have crossdev manage the symlinks automatically as well so they
> > > get the ...-emerge and ...-pkg-config by default. and setup the
> > > PORTAGE_CONFIGROOT too ...
> >
> > Yep that's what it does. I'll move the pkg over to usr/share/crossdev/
> > Got a crossdev in cvs/svn some place so I can create a ./wrappers
> > subdir?
> ive been lazy and maintaining crossdev in $FILESDIR ... if you want to ask
> robbat2 for a crossdev git or svn, we can transition to that.
> -mike
done.
http://sources.gentoo.org/gitweb/?p=crossdev.git;a=summary
http://sources.gentoo.org/gitweb/?p=crossdev.git;a=snapshot;sf=tbz2
--
gentoo-embedded@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-06-23 14:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 15:33 [gentoo-embedded] Cross Wrappers Ned Ludd
2008-06-21 19:26 ` Jason
2008-06-22 3:29 ` [gentoo-embedded] " Mike Frysinger
2008-06-22 5:14 ` Ned Ludd
2008-06-22 10:12 ` Mike Frysinger
2008-06-23 14:37 ` Ned Ludd [this message]
2008-06-23 15:38 ` Mike Frysinger
2008-07-03 13:45 ` Christopher Friedt
2008-07-03 14:34 ` Ned Ludd
2008-06-26 22:54 ` [gentoo-embedded] " Beber
2008-06-26 23:13 ` Ned Ludd
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=1214231872.17143.43.camel@media \
--to=solar@gentoo.org \
--cc=gentoo-embedded@lists.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