From: Ned Ludd <solar@gentoo.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gentoo-embedded <gentoo-embedded@lists.gentoo.org>
Subject: [gentoo-embedded] Re: Cross Wrappers
Date: Sat, 21 Jun 2008 22:14:21 -0700 [thread overview]
Message-ID: <1214111661.17143.22.camel@media> (raw)
In-Reply-To: <200806212329.40156.vapier@gentoo.org>
On Sat, 2008-06-21 at 23:29 -0400, Mike Frysinger wrote:
> On Saturday 21 June 2008, Ned Ludd wrote:
> > Ok with how you have SYSROOT + ROOT + PORTAGE_CONFIG working I think
> > I've been able to come up with a decent set of cross compile wrappers
> > that should be usable by everybody for the ideal cross compile setups.
> > No more of the 'xmerge' foo. This should do it right.
>
> for pkg-config, you may want to merge many of the things ive done here:
> http://blackfin.uclinux.org/gf/project/uclinux-dist/scmsvn/?action=browse&path=%2Ftrunk%2Ftools%2Fstaging-pkg-config&revision=5937&view=markup
Ok I snagged the error checking and QA check.
> 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?
> you should change the shebang to #!/bin/bash for all of those since they arent
> POSIX ... easier that way too
ok
> 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. When you run emerge-wrapper --init
it sets up all the symlink love which would probably be run a
pkg_postinst(). 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.
> 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?
> > I want you to review.. And then tell me if it should be apart of
> > crossdev or another pkg.
>
> crossdev should be fine i think
> -mike
--
gentoo-embedded@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-06-22 5:14 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 [this message]
2008-06-22 10:12 ` Mike Frysinger
2008-06-23 14:37 ` Ned Ludd
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=1214111661.17143.22.camel@media \
--to=solar@gentoo.org \
--cc=gentoo-embedded@lists.gentoo.org \
--cc=vapier@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