diff options
| author | aggieNick02 <nick@pcpartpicker.com> | 2021-04-08 14:01:25 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-04-08 12:01:25 -0700 |
| commit | 83f3896fc839379b85a2bf54665e14c91b7f08d0 (patch) | |
| tree | 1455e8fe995908fe3a48a0940743c23ce63c5cb8 /scripts/toolchains | |
| parent | d46fc1f4433c27c402313ae75292314e755e7af3 (diff) | |
| download | vcpkg-83f3896fc839379b85a2bf54665e14c91b7f08d0.tar.gz vcpkg-83f3896fc839379b85a2bf54665e14c91b7f08d0.zip | |
Add disable-exceptions feature to portfile for tbb (#16068)
* Add disable-exceptions feature to portfile to pass exceptions=0 to tbb_build in the non-windows case, and set TBB_USE_EXCEPTIONS=0 in the vcxproj files in the windows case. This removes the try/catch(...) wrappers around user code run by TBB. While these exception facilities can be nice in some cases, their removal allows for much easier debugging of a crash due to an unhandled exception in code that a TBB client provides to a TBB algortihm. With the try/catch(...) wrappers removed, the unhandled exception and crash dump are generated at the point of the thrown exception, versus significantly later in a different thread with the originally throwing thread no longer having the stack from when the exception was thrown.
* commit for changes from running x-add-version tbb to update for new port version
* Remove feature and undo changes made by x-add-version
* Rerun x-add-version
Diffstat (limited to 'scripts/toolchains')
0 files changed, 0 insertions, 0 deletions