nanogui: Thread: Nano-X on STLinux

Hi,
I have a set-top-box which is running STLinux. For developing UI I need some
kind of graphics library. I think Nano-X is a very option for embedded
system where memory size is a big issue. Can anybody tell whether Nano-X is
already ported on STLinux???
 
 [ STLinux is a Linux distribution targeted at  <http://www.st.com/>
STMicroelectronics Consumer electronics parts which are based around the
ST40 or ST200 CPUs.]
 
Regards,
Aveek

Aveek Adhya ha scritto:
> Hi,
> I have a set-top-box which is running STLinux. For developing UI I need some
> kind of graphics library. I think Nano-X is a very option for embedded
> system where memory size is a big issue. Can anybody tell whether Nano-X is
> already ported on STLinux???

Hi,
AFAICT, you just have to compile nano-x library with the same toolchain 
you use for your other userspace programs, using the correct options in 
the .config file (and particularly the SCREEN_PIXTYPE). If you have the 
framebuffer driver correctly running in your linux kernel, userspace 
programs linked with libnano-X.a will write directly onto /dev/fbN.

In my case the library is around 180kB.

Hope this helps,

-- 
Carlo Zinato
Viscount International S.p.A.
R&D Labs, Ancona, Italy
Tel. & fax 0039 071 2905127/2905142
####@####.####

No virus found in this outgoing message.
Checked by AVG. 
Version: 8.0.100 / Virus Database: 269.24.0/1461 - Release Date: 22/05/2008 16.44

: AFAICT, you just have to compile nano-x library with the same toolchain 
: you use for your other userspace programs, using the correct options in 
: the .config file (and particularly the SCREEN_PIXTYPE).

Actually, FYI, SCREEN_PIXTYPE isn't particularly important:
This value is only used to set the internal representation of the size
of a pixel.  Nano-X queries the framebuffer and will use the
correct framebuffer driver regardless of this setting.  This
value is important mostly for the results returned by GrReadArea()
as the default pixel type.


Regards,

Greg

Greg Haerr ha scritto:
> : AFAICT, you just have to compile nano-x library with the same toolchain 
> : you use for your other userspace programs, using the correct options in 
> : the .config file (and particularly the SCREEN_PIXTYPE).
> 
> Actually, FYI, SCREEN_PIXTYPE isn't particularly important:
> This value is only used to set the internal representation of the size
> of a pixel.  Nano-X queries the framebuffer and will use the
> correct framebuffer driver regardless of this setting.  This
> value is important mostly for the results returned by GrReadArea()
> as the default pixel type.

Thank you for pointing out!

Regards,

-- 
Carlo Zinato
Viscount International S.p.A.
R&D Labs, Ancona, Italy
Tel. & fax 0039 071 2905127/2905142
####@####.####

No virus found in this outgoing message.
Checked by AVG. 
Version: 8.0.100 / Virus Database: 270.2.0/1493 - Release Date: 09/06/2008 17.25