Searched hist:"64 e326c7" (Results 1 – 4 of 4) sorted by relevance
| /aoo42x/main/jvmaccess/inc/jvmaccess/ |
| H A D | unovirtualmachine.hxx | diff 64e326c7 Sat Mar 31 08:16:54 UTC 2018 Damjan Jovanovic <damjan@apache.org> The main/jvmaccess module stubbornly refuses to build on all setups.
As per https://gcc.gnu.org/wiki/Visibility
it turns out that GCC needs a typeinfo lookup when exceptions are
thrown between different shared libraries. This means main/jvmaccess
needs to export typeinfos for its exception classes. However on
Windows this breaks the build due to missing array new in its
base class, so typeinfos mustn't be exported for the build to
succeed. Thus, we don't export the typeinfo from the exception
classes on Windows, but we do export it on other setups.
(The more I work with C++, the more I hate it.)
Patch by: me
git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1828087 13f79535-47bb-0310-9956-ffa450edef68
|
| H A D | virtualmachine.hxx | diff 64e326c7 Sat Mar 31 08:16:54 UTC 2018 Damjan Jovanovic <damjan@apache.org> The main/jvmaccess module stubbornly refuses to build on all setups.
As per https://gcc.gnu.org/wiki/Visibility
it turns out that GCC needs a typeinfo lookup when exceptions are
thrown between different shared libraries. This means main/jvmaccess
needs to export typeinfos for its exception classes. However on
Windows this breaks the build due to missing array new in its
base class, so typeinfos mustn't be exported for the build to
succeed. Thus, we don't export the typeinfo from the exception
classes on Windows, but we do export it on other setups.
(The more I work with C++, the more I hate it.)
Patch by: me
git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1828087 13f79535-47bb-0310-9956-ffa450edef68
|
| /aoo42x/main/jvmaccess/util/ |
| H A D | gcc3.map | diff 64e326c7 Sat Mar 31 08:16:54 UTC 2018 Damjan Jovanovic <damjan@apache.org> The main/jvmaccess module stubbornly refuses to build on all setups.
As per https://gcc.gnu.org/wiki/Visibility
it turns out that GCC needs a typeinfo lookup when exceptions are
thrown between different shared libraries. This means main/jvmaccess
needs to export typeinfos for its exception classes. However on
Windows this breaks the build due to missing array new in its
base class, so typeinfos mustn't be exported for the build to
succeed. Thus, we don't export the typeinfo from the exception
classes on Windows, but we do export it on other setups.
(The more I work with C++, the more I hate it.)
Patch by: me
git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1828087 13f79535-47bb-0310-9956-ffa450edef68
|
| H A D | mingw.map | diff 64e326c7 Sat Mar 31 08:16:54 UTC 2018 Damjan Jovanovic <damjan@apache.org> The main/jvmaccess module stubbornly refuses to build on all setups.
As per https://gcc.gnu.org/wiki/Visibility
it turns out that GCC needs a typeinfo lookup when exceptions are
thrown between different shared libraries. This means main/jvmaccess
needs to export typeinfos for its exception classes. However on
Windows this breaks the build due to missing array new in its
base class, so typeinfos mustn't be exported for the build to
succeed. Thus, we don't export the typeinfo from the exception
classes on Windows, but we do export it on other setups.
(The more I work with C++, the more I hate it.)
Patch by: me
git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1828087 13f79535-47bb-0310-9956-ffa450edef68
|
Completed in 27 milliseconds