nanogui: port question
Subject:
Re: [nanogui] Re: AW: port question
From:
Ed Sutter ####@####.####
Date:
7 Jul 2005 19:07:13 +0100
Message-Id: <42CD6F35.30801@lucent.com>
Aaron,
Ok, that's encouraging. The libc/malloc stuff isn't a problem.
Here's the approach I started with (please comment if it's
barking up the wrong tree)...
I minimized the build (via config and include/device.h) and
managed to build the libraries (no demos).
Then I modified the mdemo code just enough to get it to run as
a MicroMonitor application. My logic was this... build a complete
application and let the linker tell me what isn't there.
In doing that I had three "stubs"...
MwSelect()
gen_gettextbits()
and
scrdev
I've rebuilt a MicroMonitor-equivalent for MwSelect() and I'm now
working on the other two. Figuring that scrdev is the snippet that
will hook MicroWindows up to my display.
Does this make sense?
Thanks again
Ed
>>Thanks for the response; however, let me re-phrase my question.... I
>>am considering use of Microwindows in an embedded system that has no
>>RTOS at all. No multitasking, no OS-like facilities and certainly no
>>sockets. I'm not interested in the 'X' stuff, just the GUI.
>
>
> you'll have a little legwork to do, but with LINK_APP_INTO_SERVER (or
> whatever it's called these days) it's doable without needing socket() or
> select() calls. fonts can be directly linked in.
>
> the only possibly problematic bits I can think of off the top of my head
> are requirements for a C library (primarily string manipulation) and
> dynamic memory allocation via malloc() and free().
>
