Boosters: In our embedded environment, we compile everything with -fno-exceptions. I'm getting errors in the new program_options library because it has naked throw calls in it. I did see a definition of boost::throw_exception and changed the naked throw calls to use that. That seems to work. However, naked throw calls are littered throughout many of the libraries. Is there some generic way to get these libraries to compile with -fno-exceptions or do I have to go through and change all calls to throw to boost::throw_exception? Thanks, David Ward Acterna
"David Ward" wrote:
Is there some generic way to get these libraries to compile with -fno-exceptions or do I have to go through and change all calls to throw to boost::throw_exception?
Libraries may or may not honor such request (indicated by BOOST_NO_EXCEPTIONS). Those who don't need manual update. /Pavel
David Ward wrote:
Boosters:
In our embedded environment, we compile everything with -fno-exceptions. I'm getting errors in the new program_options library because it has naked throw calls in it. I did see a definition of boost::throw_exception and changed the naked throw calls to use that. That seems to work.
What do you mean by "work". That converts all error handling into abort()s, no? Is that what you want? And a side question, if you don't mind -- how do you use program_options in embedded system? For reading config files? - Volodya
participants (3)
-
David Ward
-
Pavel Vozenilek
-
Vladimir Prus