[fobbit-developer] Re: CVS Merges

[Anup M. <sk...@us...>]

Mark & fobbit team,

As I've commented in the public forums, I have a working OS X port with one 
known bug.  In order to exit the app, you have to unplug the usb 
device.  This is because I can't figure out how to best force my launched 
pthreads to quit.  I'm close to getting it working but I don't know enough 
about pthreads so my progress is a bit slow.  Barak, how are your efforts 
coming along?  I'd love to collaborate on the OS X port.

I'd also like to understand what clean-ups people have done in order to 
best figure out what to submit of my changes.  I've listed some areas that 
I'd propose changing:

1.  Platform macros
This is the most critical as the Darwin (the kernel in MacOS X) port uses 
most of the behavior from the unix port but has some elements from the 
windows port (threads to read from the USB pipes and dump that data into 
network buffers).  Just using the So the usb interface is almost windows 
like while the rest of the app is BSD like.  Setting VB_IS_UNIX doesn't 
work for Darwin.  I have some thoughts about reworking the platform macros 
but want to properly coordinate that with your efforts.

2.  Build process
I'd like to have the unix flavors using the configure/automake 
functionality.  I've not started this effort yet but I'm willing to take it 
on if there is interest in switching.  Not a high priority in my mind but 
it would make it more compatible with other porting/packaging efforts.

3.  vblast.h
Maybe it's just me but I'd love to find a way to break up this file into 
more manageable chunks.  If we all start contributing to the project, it 
might help not to have constant merges on one all-encompassing header file.

4.  exit()
This is the usual path if any error occurs.  I think the behavior is fine 
but it makes error reporting/recovery/cleanup more difficult.  Maybe this 
could change.

I'd love to hear what others are preparing...

anup