mirror of
https://github.com/reactos/reactos.git
synced 2025-02-22 08:25:03 +00:00
e104ebd33e
I double-checked and although the crash in Motorbike does *not* happen by default in all of those builds:
0.4.14-RC-54-g6a6672d (hidden by opt-in apisets-default in release branch)
0.4.13-release-1-g2ac9d98 (hidden by opt-in apisets-default in release branch)
0.4.12-release-17-g79780cd (hidden also, I don't understand why)
0.4.11-release-28-gc4d930d (hidden also, I don't understand why)
0.4.10-release-35-g94b4a3e (hidden also, I don't understand why)
0.4.9-release-41-gd3a79fe (hidden also, I don't understand why)
0.4.8-release-46-gd4d58d7 (hidden, does not have apisets yet)
0.4.7-release-56-g835b508 (hidden, does not have apisets yet)
It was really only crashing in master by default, not on the release branches.
I decided to port the proper fix back nevertheless, because:
- the exports are wrong for our target
- I can not guarantee otherwise that it would not pop up all of a sudden later
- avoids the crash in rls-branches in case the app was intentionally started in Vista-compat-mode
- and the fix also decreases the binary size of that apiset.
Fix picked from 0.4.15-dev-179-g 02825c20e4
12 lines
468 B
Ruby
12 lines
468 B
Ruby
|
|
# This file is autogenerated by update.py
|
|
|
|
@ stub -version=0x602+ RoActivateInstance
|
|
@ stub -version=0x602+ RoGetActivationFactory
|
|
@ stub -version=0x602+ RoGetApartmentIdentifier
|
|
@ stub -version=0x602+ RoInitialize
|
|
@ stub -version=0x602+ RoRegisterActivationFactories
|
|
@ stub -version=0x602+ RoRegisterForApartmentShutdown
|
|
@ stub -version=0x602+ RoRevokeActivationFactories
|
|
@ stub -version=0x602+ RoUninitialize
|
|
@ stub -version=0x602+ RoUnregisterForApartmentShutdown
|