> Hi,
>
> Where do I start if I'm going to consider porting Japhar to BeOS?
Well, get BeOS running as a start. That was stopping me from porting
it in the first place. :-/
> We've got a working version of NSPR for BeOS that was ported for the
> BeZilla project. If we use build Japhar with NSPR enabled, what
> other platform dependent code do we need to worry about?
The main things to think about is
- DLL [dynamic_loading.c]
- threads [threads.c] / monitors [monitors.c]
- signal handling [signals.c]
The rest of the files in arch/ (fmodf.c, scandir.c, snprintf.c,
strerror.c and vsnprintf.c) are replacement functions
I suggest doing a native port, and not try to use NSPR. The
arch-dependent source should be located in arch/.
There are test programs to check if threads and mutexes are working.
If you want to write a test for DLL and signals, I would be glad.
> ps. does anyone use egcs (cygnus) to build Japhar?...
I do sometimes. No problems that I know about.
Happy hacking,
--
##> Petter Reinholdtsen <## | [EMAIL PROTECTED]
O- <SCRIPT Language="Javascript">window.close()</SCRIPT>
http://www.hungry.com/~pere/ | Go Mozilla, go! Go!
