On 22.03.2012 19:20, Dave Mielke wrote:
How do you prepare brltty for compilation? Do you use its configure script?
I cheat. I've adjusted config.h manually and have put it in grub-core/braille. There is a conflict with our own config.h in the variables like PACKAGE_NAME but I've just removed PACKAGE_NAME for brltty for time being.
async should now be okay (now meaning the latest development code). If neither
poll() nor select() is available, it leaves out all of the I/O monitoring stuff
except that asyncRead() and asyncWrite() report ENOSYS (function not
supported). The alarm stuff still works, though.
What kind of monitoring would you like to have? In GRUB network and usb are currently async, rest is sync.

Does grub have nanosleep()? If not, what's the best way to delay for a known
small amount of time?
grub_millisleep
> Can you tell me which gcc options to specify, including getting it to point to the right set of headers, so that I can compile for a grub environment without
> using the actual grub build system?
That's not currently possible.
> That, for me, would probably be the easiest. I intend to go through all of the code to remove all of those warnings which you've had to suppress for the time
> being.
Warnings are secondary. We can add -Wno- for brltty.
> How easy is it for you to incorporate new brltty revisions as they're committed to our repository?
Fairly easily: copy it to grub-core/braille/brltty and apply the patch.



--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko

_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: [email protected]
For general information, go to: http://mielke.cc/mailman/listinfo/brltty

Reply via email to