From: Sergey 'Jin' Bostandzhyan <jin@mediatomb.cc>
To: openembedded-devel@lists.openembedded.org
Cc: Using the OpenEmbedded metadata to build Distributions
<openembedded-devel@openembedded.org>
Subject: Re: building uClinux using OE
Date: Tue, 19 Feb 2008 14:01:04 +0100 [thread overview]
Message-ID: <20080219130104.GC27792@deadlock.dhs.org> (raw)
In-Reply-To: <47B4708B.6050008@student.utwente.nl>
Hi,
On Thu, Feb 14, 2008 at 05:47:07PM +0100, Koen Kooi wrote:
[...]
> | What is missing?
> |
> | - applying elf2flt processing to produced binaries
>
> That should happen automagically, we just need to stage some more
> binutils-cross headers for elf2flt to build
OK, I'll see that I get elf2flt to build, I'll surely have some questions
about the "automagically" part later on :)
> | - have a way of knowing that the particular build is done for the uClinux
> | targets (maybe for some tweaks in .bb files if required or to apply
> patches
> | only when necessary, allthough ifdef __uClinux__ defines could be used)
> |
> | - not sure what else?
>
> Since you can't (practically) do shared libraries, all packaging (and
> probably staging) will be wrong, since you won't have libfoo.so.1, but
> something different.
OK, I'll keep that in mind.
> | I do not have any uClinux experience yet, and it seems to be quite
> difficult
> | to gather all the bits and pieces of information, so I'd appreciate
> comments
> | and suggestions, especially if you see that I am missing something.
> |
> | I'd also be interested in your thoughts on what would be the best way to
> | integrate it into OE.
>
> I had a go at this a while ago, but I had to halt working on it since
> the uboot on the blackfin site refuses to load the uImage on the
> blackfin site, leaving me without a good testing target.
> I think forcing static linking would be the fastest way to get an image
> built, we can work on details (flat, shared-flat, fdpic, etc) after that.
How far did you come with the stuff you did back then? Did you merge anything
of it into OE and if yes, could you please point me to the things you did
so I can pick up from there?
Thanks,
Jin
next prev parent reply other threads:[~2008-02-19 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 15:55 building uClinux using OE Sergey 'Jin' Bostandzhyan
2008-02-14 16:47 ` Koen Kooi
2008-02-19 13:01 ` Sergey 'Jin' Bostandzhyan [this message]
2008-02-22 18:32 ` Sergey 'Jin' Bostandzhyan
2008-02-17 15:28 ` Alan Carvalho de Assis
2008-02-19 13:07 ` Sergey 'Jin' Bostandzhyan
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=20080219130104.GC27792@deadlock.dhs.org \
--to=jin@mediatomb.cc \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.