Building Linux client -- is -fno-exceptions required?

[Plinker1961]

While porting our (modified) CEF Client code to the Linux version of CEF, I discovered that parts of our client did not build because CMakeList.txt instructs CMake to compile with -fno-exceptions. But our version of the CEF client includes a smattering of try/catch blocks in support of limited serial I/O and database support, which don't work with the -fno-exceptions switch.

My quick workaround was to add add_compile_options(-fexceptions) to the CMakeLists.txt file for CEFClient. This way, the wrapper library is still built with -fno-exceptions, but the client is built with exceptions enabled. Is this acceptable? Will it cause any unexpected problems?

[magreenblatt]

It should be OK if you build both libcef_dll_wrapper and your application with -fexceptions.

[Plinker1961]

It's easy enough to set those both to use -fexceptions, just curious though as to why. Is the concern that I might get unexpected results if these are compiled with different settings?

[magreenblatt]

It's easy enough to set those both to use -fexceptions, just curious though as to why. Is the concern that I might get unexpected results if these are compiled with different settings?

Right. They both link and share the standard library so you want to build them with the same configuration.

[Plinker1961]

Is there a technical reason the sample client uses -fno-exceptions?

[magreenblatt]

Is there a technical reason the sample client uses -fno-exceptions?

Yes. Because it doesn't use exceptions.