On Wed, Jan 29, 2003 at 11:03:20AM -0500, Cesare Zavattari wrote:
> Hi all,
> I'd like to port picoGUI on my own operating system 
> (http://mynos.sourceforge.net). At the moment DEPUI already works on 
> mynos, but I have very few POSIX syscalls implemented.
> I'd like to have an idea of the *basic* posix syscalls picoGUI *needs* to 
> run (signals calls? threads calls? select&ioctl?)
> Thank you very much!

Cool.
PicoGUI will need, from the top of my head:

  - C standard library functions including the printf family, malloc and
    friends, and standard file I/O

  - Several miscellaneous functions including timers, shared memory,
    and directory tree traversal- fortunately much of this can be safely
    omitted, and it's all quarantined within the 'pgserver/os' directory.

  - BSD sockets. All the networking code in PicoGUI currently assumes
    BSD-compatible sockets, as also provided by Linux, IRIX, and (sort of)
    win32. This will be eliminated when the network code is refactored.
    This includes the use of select() to wait on multiple sockets and/or
    input devices.

> 
> -- 
> Cesare
> 
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Pgui-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/pgui-devel

-- 
Only you can prevent creeping featurism!


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Pgui-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/pgui-devel

Reply via email to