public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Shinkan <shinkan@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Cross Dev Tricks + Hardened questions
Date: Tue, 1 Dec 2009 09:44:06 +0100	[thread overview]
Message-ID: <166af1cf0912010044l5ecf11ebkcc93dbbfe4603ebc@mail.gmail.com> (raw)
In-Reply-To: <20091130211241.27358.qmail@stuge.se>

[-- Attachment #1: Type: text/plain, Size: 1925 bytes --]

2009/11/30 Peter Stuge <peter@stuge.se>

>
> USE CATALYST!
>
> To do this you will create stage2, stage3 and stage4 spec files
> (maybe also stage1, I'm not sure on that) for catalyst. It can
> produce exactly what you want.
>
> Fine, I believe this would be controlled by USE flags for stage2 and
> up.
>
> Please just start playing with the catalyst examples. I hope you will
> quickly learn what they produce.
>

I already looked a lot into Catalyst but some points doesn't fit to my plans
:
- I have to use a profile if I want to specify things (for instance ports
version) for base stage. I really don't want to build a profile because
they're hard to maintain in a wide use scheme, and because that's overkill.
- Catatalyst seems to build by substraction (I mean on livecd, it builds
from a stage3, then unmerges and removes things). I want to build with
additive steps (from nothing).
- I want to be able to just emerge one new port or update one on a target,
and with Catalyst I cant. I must rebuild all (yeah, cache is there but...),
and I really need to build just one port on some cases.

That's why I thought about a "build" directory built from my host with
crossdev. Then I use this build env to build my target with gcc/libc I want.
If I have to build just one port, I can use my build env for this target
again.
Since I choose what to build from nothing, I don't have to use profile to
define what I put in my target or build. I don't break system by removing
things.
My build standard "make.conf" serves as usual, I have nothing more than a
crossdev, a make.conf filling, and some emerge to a given root.

That's what I want, but I don't know how to achieve this.
If Catalyst can offer me this control, I would be glad to use it.


-- 
Pierre.
"Sometimes when I'm talking, my words can't keep up with my thoughts. I
wonder why we think faster than we speak. Probably so we can think twice." -
Bill Watterson

[-- Attachment #2: Type: text/html, Size: 2461 bytes --]

  reply	other threads:[~2009-12-01 10:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 18:24 [gentoo-embedded] Cross Dev Tricks + Hardened questions Shinkan
2009-11-30 21:12 ` Peter Stuge
2009-12-01  8:44   ` Shinkan [this message]
2009-12-01 17:48     ` Ned Ludd
2009-12-01 19:03       ` Ed W
2009-12-01 20:51         ` Peter Stuge
2009-12-01 22:24           ` Shinkan
2009-12-02  0:17             ` Peter Stuge
2009-12-02  9:28               ` Shinkan
2009-12-01 19:03       ` Peter Stuge
2009-12-01 20:52         ` Shinkan
2009-12-01 23:57           ` Peter Stuge
2009-12-02  8:02             ` [OT] Catalyst, was: " Eckard Brauer
2009-12-02  9:04               ` Ed W

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=166af1cf0912010044l5ecf11ebkcc93dbbfe4603ebc@mail.gmail.com \
    --to=shinkan@gmail.com \
    --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