Thank you for your question.
If your system likes some T-kernel-based system,
you will edit ws/src/btron/devfb.cpp for your system and
use library libwste.a.
If your system likes some posix-based system,
you will edit ws/src/devfb/devfb.cpp, devfb_dep.cpp, devfb_linuxfb.cpp
for your system and use library libwsdevfb.a, I think...
To acess the frame buffer of your system,
you must rewrite the function: _init_frame_buffer() and
If you want to call "OSSemCreate",
you must rewrite cre_sem() in ws/src/devfb/devfb.cpp to call "OSSemCreate"..
Bhaskar Das (RBIN/ECM4) wrote:
> Hello Hirabayashi-san,
>Is it possible to separate Widestudio sources into platform-independent
>and platform-dependent section? The aim is to "integrate" Widestudio
>sources into my existing system software which already has file system,
>graphics, tcp/ip stack and other required middleware functionality.
>While integrating, I would use the direct frame buffer version of
>After going through Widestudio sources, I observed that Widestudio
>internally relies on generic system calls like "cre_sem" etc. However I
>could not find any header file which maps such generic system calls to
>"underlying RTOS" calls. Something like if I use Widestudio with
>uC/OS-II kernel then I need to use "OSSemCreate" and for T-Kernel,
>Is there a way(via some header file) using which I can make Widestudio
>link to my board-specific system calls?