1 |
On Thu, 2003-11-06 at 19:05, nDiScReEt wrote: |
2 |
<snip> |
3 |
> Since we are committing to uClibc (I have no complaints and am in complete |
4 |
> agreement, except....) that raises a new issue. Well, not entirely new but an |
5 |
> issue nonetheless. Familiar is now trying to krack down on developers and |
6 |
> contributors to provide links to their source code used to make their current |
7 |
> binary programs. The downside is that without the special patches and what |
8 |
> not, alot of useful and great programs can not be ported readily to uClibc. |
9 |
> Not saying that this is an impossibility, just saying that how do we design |
10 |
> the ebuild to port current gentoo applications to fit and function in our |
11 |
> embedded environments. Not all PDAs have the same screen size and memory |
12 |
> constraints as noted in an earlier post. As memory is an important factor, it |
13 |
> shouldn't be a penalty for those with bigger memory and displays. There |
14 |
> should be a tool that works like genmenu, in which where you use this program |
15 |
> (let us call it "genembedconf") to set the parameters for your particular |
16 |
> build of a embedded system (ie the HP iPAQ H3955 is a 400MHz Intel XScale |
17 |
> PXA250 hwhich has 32MB flash ROM, 64MB SDRAM, and 240x320 16-bit display.) |
18 |
> We would want it to be compiled for a pxa and have all apps be ported to a |
19 |
> display size of 240x320 with rotation capability. On the other hand, Sharp |
20 |
> Zaurus C-7[56]0 display is 640x480 with 128MB of storage (of which 64MB is |
21 |
> always for storage), and it's hardware processor is a Intel XScale PXA255. |
22 |
> Then, of course, there is the ARM. So creating an gentoo embedded |
23 |
> configuration tool I think would simplify creating cross-compiling toolchains |
24 |
> and target-specific compiled code. I hope I conveyed my thoughts clearly |
25 |
> enough so that everyone understands what I am talking about. As I have been |
26 |
> up for far too long to mention and am now in dire need of some much needed |
27 |
> sleep. |
28 |
I don't see the need for a configuration tool. All you have to set are |
29 |
CFLAGs and chose a libc, a choice which will be influenced by the amount |
30 |
of memory on the device. Screen resolution has little effect when |
31 |
building the package, unless it has multiple front ends, such as a QT |
32 |
front end, a GTK one, a QT/E one, and the list goes on. In such cases I |
33 |
feel USE flags should be used to determine which front ends are built. I |
34 |
have yet to see applications with built in rotation. Environments such |
35 |
as OPIE or I'm sure X handle this AFAIK. You use the same toolchain for |
36 |
building ARM and PXA binaries, just with different CFLAGS(and obviously |
37 |
the toolchain has to support PXA, but it is not a separate toolchain). |
38 |
Just my 2 cents, |
39 |
-- |
40 |
Abhishek Amit <abhishek@g.o> |