| 1 |
On Tue, Jan 20, 2004 at 08:54:05PM -0500, Ned Ludd wrote: |
| 2 |
> > This could just be default (no trigger) - I think lisa has done it a few times |
| 3 |
> > in her ebuilds. |
| 4 |
> > |
| 5 |
> |
| 6 |
> I'd rather have a trigger here. The reason for that is I'd prefer to |
| 7 |
> allow the ebuild to continue to attempt to set all the latest settings |
| 8 |
> dynamically and having a missing option in a .config could/might cause |
| 9 |
> some interactivity out of the build process which I want to avoid. |
| 10 |
> |
| 11 |
> This might be a little extreme but do you think we should slap an extra |
| 12 |
> ARCH || CHOST|| CCHOST directory into the ${ROOT}/etc/busybox/whatever/ |
| 13 |
> to allow for unique cross compiling busybox configs? |
| 14 |
> |
| 15 |
|
| 16 |
that sounds like a good idea |
| 17 |
|
| 18 |
${ROOT}/etc/busybox/${CCHOST} maybe ? |
| 19 |
arch's can have different 'sub-archs', for example x86 can be pentium4 or |
| 20 |
athlon-mp |
| 21 |
|
| 22 |
|
| 23 |
-- |
| 24 |
gentoo-embedded@g.o mailing list |
Archives