From: Ilya Dmitrichenko <errordeveloper@gmail.com>
To: yocto <yocto@yoctoproject.org>
Cc: "“robert.berger@reliableembeddedsystems.com”"
<robert.berger@reliableembeddedsystems.com>
Subject: Re: Build appliance
Date: Sat, 24 Jan 2015 22:00:47 +0000 [thread overview]
Message-ID: <CAPhDKbHJ9uXeuJ0O3Eg2v2zHGS5AZvL4cTYVoJFbd6VOkZQ8jA@mail.gmail.com> (raw)
In-Reply-To: CAPhDKbHip+UWSpfckRBo+=QBWGnMg+Bq55DcUS77zkxNmZHd2A@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
Adding Robert to CC list...
On Sat Jan 24 2015 at 9:53:32 PM Ilya Dmitrichenko <errordeveloper@gmail.com>
wrote:
> Hi List,
>
> I have attempted to define a custom build appliance image, with some
> degree of success. The only problem is that I have noticed is there is
> still a whole lot of `*-native` packages being pulled in when trying to
> build something. So I have attempted adding all of those to my image and
> set `ASSUME_PROVIDED` accordingly, it was still trying to build
> pseudo-native and sqlite3-native for some reason... Ideally, I'd like to
> have all of the `*-native` deps pre-installed on my build appliance's base
> filesystem, I believe this should work and I shouldn't have to bootstrap
> `tmp/work/sysroots/` and use the sysroot in `/usr` instead.
>
> More specifically, I am trying to build a container image that would cover
> the purpose of the build appliance and SDKs/ADTs, I think container could
> simplify a lot for Yocto... I haven't fully figured it out yet, still
> exploring the options, so hope the idea makes sense overall.
>
> Cheers,
> Ilya
>
[-- Attachment #2: Type: text/html, Size: 1357 bytes --]
next prev parent reply other threads:[~2015-01-24 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-24 21:53 Build appliance Ilya Dmitrichenko
2015-01-24 22:00 ` Ilya Dmitrichenko [this message]
2015-01-26 10:40 ` Ilya Dmitrichenko
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=CAPhDKbHJ9uXeuJ0O3Eg2v2zHGS5AZvL4cTYVoJFbd6VOkZQ8jA@mail.gmail.com \
--to=errordeveloper@gmail.com \
--cc=robert.berger@reliableembeddedsystems.com \
--cc=yocto@yoctoproject.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.