|
Building our own targets: msg#00053t2.devel
Is there any how-to on how to build a completely custom target from scratch? We are trying to build a target, that frankly would be of no use to anyone else, because it would be specifically targeted at a specific hardware platform. I keep looking at T2 because what I actually need is several variations of the same base software package. Some of these packages are custom, most are standard packages. The structure of T2 seems ideal for our needs, but I have been having more than just a few issues working with some of the prebuilt targets. Since the previously defined targets are not what I really want anyway, I feel that I am spinning my wheels needlessly. So, what I was hoping to do is start from a base package that fires up using uClibc and busybox, and boots to a ash shell. Nothing more. If any of you have built the default buildroot target, that is what I want, plus the boot loader and kernel. Once that is built, I can start incorporating our custom applications. In our case, we are not building a general purpose machine, so the line between OS and APP will be nearly non-existent. Is there any type of how-to that can help me do this in T2? Thx -- Kevin Fries Linux Engineer CCT, US http://www.cctus.com (303) 708-9228 x326 |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Touchscreen: 00053, Rene Rebe |
|---|---|
| Next by Date: | Re: Building our own targets: 00053, Rene Rebe |
| Previous by Thread: | Touchscreeni: 00053, Hahn\, Harald |
| Next by Thread: | Re: Building our own targets: 00053, Rene Rebe |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |