Files
loongoffice/cli_ure/source/uno_bridge
Stephan Bergmann cbce40e965 Make content of OSL_ASSERT, DBG_ASSERT, etc. visiblie in non-debug builds
...to avoid lots of loplugin:staticmethods warnings.  Also enables DBG_ASSERT
etc. also for --enable-debug builds in addition to --enable-dbgutil builds.

Change-Id: Ib89ecd9ab8ce7abb2c64790ace248b31f9d2b64d
2015-07-13 18:14:11 +02:00
..
2015-05-15 17:55:15 +00:00
2015-07-04 10:23:17 +00:00

Because of the LoaderLock bug in .NET Framework 1.0 and 1.1 the cli_uno.dll is linked 
with the /NOENTRY switch, which prevent that the C-runtime is initialized when loading 
the dll.

Also I removed all static c++ objects which need construction by the CRT, 
exception handling seems to need an initialised CRT. Therefore
I added CRT initialization code in  uno_initEnvironment (cli_bridge.cxx)
However there is no deinitialization done because bridge libraries remain 
in memory until the process dies. There is actually no good place where 
this had to be called. If we would do that we would have to implement that
the bridge can be disposed.


Sell also:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechart/html/vcconmixeddllloadingproblem.asp
http://support.microsoft.com/?id=814472
http://www.ddj.com/dept/windows/184416689
http://blogs.msdn.com/cbrumme/archive/2003/08/20/51504.aspx
http://msdn2.microsoft.com/en-US/library/ms172219.aspx