Lothar,
Hi Daniel,
BOOST_NO_EXCEPTIONS will disable all boost exceptions, but my problem is
not that exceptions are not thrown, the problem is that they cannot be
caught. And if I would disable them, I'd have no error handling.
How did you build boost? In case you used the default instructions from
boost.org, for me they do not work for two reasons:
1) No universal binaries are created
But even if I compile & link everything (including the application) as
non-universal:
2) I get loads of linker errors in boost::filesystem, it seems to use
non-MacOS-native-libs, which is bad (I need a native boost).
The only two ways I made it work were
i) cmake + boost 1.34.0 and
ii) asl (adobe source library)
But with the result that exceptions cannot be caught...
Regards,
Lothar
Daniel Lord wrote:
> UPDATE:
> Just came across this in the Boost documentation for filesystem which
> might be an explanation:
>
> "All exceptions thrown by the Filesystem Library are implemented by
> calling boost::throw_exception()
>
<file:///Users/daniello/Documents/Development/Lib/Boost/boost_1_34_1/libs/utility/throw_exception.html>.
> Thus exact behavior may differ depending on BOOST_NO_EXCEPTIONS at the
> time the filesystem source files are compiled."
>
> Daniel
> ---
> Some people building C++/Obj-C code on OS X with Xcode and have a
> problem think: "I know, I'll use the Boost Libraries". Now they have two
> problems--three if they used Boost for regular expressions. ;-)
>
_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users