1 |
yeah it seems to be doable only with say x86 embedded devices, cuz i |
2 |
doubt there is many mips, xscale, etc desktops out there ;). I do run |
3 |
my system like that since it is an x86, I just disconect the storage |
4 |
attach it to the desktop and work on it there and then move it back to |
5 |
the device. |
6 |
|
7 |
|
8 |
On Thu, 2003-11-27 at 01:07, Philippe Coulonges wrote: |
9 |
> Le Wed, 26 Nov 2003 23:43:43 -0600 |
10 |
> Andrew Gaffney <agaffney@×××××××××××××××××××.net> écrivait : |
11 |
> |
12 |
> > Zachery Hostens wrote: |
13 |
> > > Hi, |
14 |
> > > |
15 |
> > > i was unable to make the meeting Nov. 23rd, been really busy lately. |
16 |
> > > |
17 |
> > > I was kinda curious, as to why dont you make the toolchain like a |
18 |
> > > chrooted environment, install uclibc and all that grand old stuff in |
19 |
> > > |
20 |
> > > /home/crossdev then have like "/ROOT" for the root of the actual |
21 |
> > > project.... (yea i realize this requires a shell and probably a |
22 |
> > > little more) im assuming that may make development a little easier, |
23 |
> > > but maybe not needed for how im looking at it. |
24 |
> > > |
25 |
> > > I kinda think it should be like a secluded environment from the |
26 |
> > > actual system its running on... |
27 |
> > |
28 |
> > Are you talking about chrooting for the build environment, or |
29 |
> > chrooting into the system image you are building? |
30 |
> |
31 |
> Chrooting into a cross-compiled system image seems hard to realize, |
32 |
> unless you can install a good simulator for the target processor and all |
33 |
> the devices of your target machine. |
34 |
> |
35 |
> Chrooting in a build environment brings constraints for no great |
36 |
> benefits. IMHO, some environments variables and simlinks should be |
37 |
> enough to have an ergonomic dev environment. |
38 |
> |
39 |
> CU |
40 |
> CPHIL |
41 |
|
42 |
|
43 |
-- |
44 |
gentoo-embedded@g.o mailing list |