Boost and Real Time

Hi, I'm an experienced C++ programmer, but very new to Boost. I'm looking into making use of it for my next project, which will run on LynxOS, a real time system. Does anyone have any experience, knowledge of pitfalls, or words of wisdom to share about building and running with Boost, or more likely a subset of Boost's libraries, for a real time system? Thanks for any help. -Brian

Brian - You pose a very broad set of questions, whose only answer would be another set of questions. (It depends on what you are doing...) I use boost in numerous "real time/embedded" environments (VxWorks, Linux, ...) and find the extensibility is a greater advantage to "gut-busting" performance, but again this depends upon what you are doing. First thing you should do is evaluate compiler support and attempt to build the libraries. Vlad has instructions on cross-build environments, or you can chroot, or kvm, it's up to you how you wish to build. You may come across some anomalies with some libraries, and the users & build group can help you with that. Next I would be to take a serious look at your requirements and the problem domain. It's been my experience that "real-time" usually involves small sub-sections of code which are super important, and mountains of other code for doing other things. For that mountain of other code, I would suggest using boost where it "makes sense". Good Luck, Tim On Wed, Feb 18, 2009 at 10:35 AM, Brian Wrenn <dcbrianw@gmail.com> wrote:
Hi,
I'm an experienced C++ programmer, but very new to Boost. I'm looking into making use of it for my next project, which will run on LynxOS, a real time system. Does anyone have any experience, knowledge of pitfalls, or words of wisdom to share about building and running with Boost, or more likely a subset of Boost's libraries, for a real time system?
Thanks for any help. -Brian _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
-- Regards, Timothy St. Clair [timothysc@gmail.com]
participants (2)
-
Brian Wrenn
-
Tim St. Clair