| 1 |
Hi. Model |
| 2 |
|
| 3 |
> /usr/ |
| 4 |
> arm-none-linux-gnueabi/ -> projectA/ |
| 5 |
> arm-none-linux-gnueabi.orig/ |
| 6 |
> projectA/ |
| 7 |
> projectB/ |
| 8 |
> ... |
| 9 |
> projectN/ |
| 10 |
> |
| 11 |
> with arm-none-linux-gnueabi.orig/ being the original contents after |
| 12 |
> crossdev built the toolchain. As I create projects, I would 'cp -a |
| 13 |
> arm....orig/* projectN/' |
| 14 |
> |
| 15 |
|
| 16 |
there is one drawback here - compiler version. Looks like gentoo |
| 17 |
stores libc files in /usr/lib/gcc/arm-projectA-linux-gnueabi/1.2.3 |
| 18 |
so it will probably break something if you use different gcc for your projects. |
| 19 |
|
| 20 |
> How do folks out there handle multiple projects with the same toolchain? |
| 21 |
> I'm thinking, since crossdev worked so well, to just build a |
| 22 |
> 'arm-projectA-linux-gnueabi' and then 'arm-projectB-linux-gnueabi' to |
| 23 |
> keep the roots separate. |
| 24 |
> What do you guys use? |
| 25 |
|
| 26 |
I use 'arm-projectA-linux-gnueabi' approach. It works, but still not |
| 27 |
ideal - For example, I can't just copy the whole folder to another |
| 28 |
gentoo machine and continue use emerge-projectA there. |
| 29 |
|
| 30 |
I would prefer toolchain to be in a single directory, like |
| 31 |
codesourcery does. Maybe there is another solution, does anybody know? |
| 32 |
|
| 33 |
Sergey |
Archives