[Olympus developers 344]: Re: CMU Olympus *nix Conversion Status

[Alex Rudnicky]

Some work has been done on this but it is not complete.
The Ravenclaw code was written to minimize dependence on Windows (with a view to an eventual port).
The key issue is finding/writing a substitute for the Microsoft string library.
I expect there are syntax issues.
Note that the messaging layer is written in Python.

From: olympus-developers-bounces at mailman.srv.cs.cmu.edu [mailto:olympus-developers-bounces at mailman.srv.cs.cmu.edu] On Behalf Of Chris E
Sent: Monday, May 07, 2012 3:01 PM
To: olympus-developers at cs.cmu.edu
Subject: [Olympus developers 343]: CMU Olympus *nix Conversion Status

Hello,

I recently came across the CMU Olympus Framework and I am interested in learning about the challenges and progress in running Olympus in an embedded linux environment (e.g. robots, cars, smart phones, etc).

I read the following threads:
http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/2009-January/000082.html
http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/2009-January/000083.html

I was just wondering if anything has changed since then, and what kinds of issues would developers face when trying to port Olympus (memory, windows API dependencies, CPU, etc).

In particular I have been looking at the RavenClaw Dialogue system so I would be interested in learning more about the difficulties for this task with respect to this module.

Thank you so much for your time and help. I look forward to hearing from you.

Best regards,
Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20120507/fad03827/attachment.html