4 Commits

Author	SHA1	Message	Date
Zsolt Parragi	85e08370d0	bindexplib: Always export executable symbols, even they are also readable ... Previously bindexplib discarded read-only non-function symbols even in executable/code sections, but in some specific cases they could still mark functions. An example is provided by nop.asm in the AuoExportDll test, which exports a function only marked by a label. This symbol can be used from C/C++ code, but without this change it would result in an unresolved external symbol when built as a DLL on Windows.	2017-02-28 09:49:12 -05:00
Brad King	13a6ff31be	VS: Fix WINDOWS_EXPORT_ALL_SYMBOLS for object libraries ... Teach Visual Studio generators to include object files from object libraries in the list of objects whose symbols are to be exported. The Makefile and Ninja generators already did this. Update the test to cover this case. Reported-by: Bertrand Bellenot <Bertrand.Bellenot@cern.ch>	2016-07-21 11:05:22 -04:00
Yury Zhuravlev	9da725cb00	Windows: Honor WINDOWS_EXPORT_ALL_SYMBOLS for executables with exports ... For executables with ENABLE_EXPORTS set, export all symbols when instructed to do so by WINDOWS_EXPORT_ALL_SYMBOLS.	2016-07-11 09:41:04 -04:00
Bill Hoffman	8f86407cfd	Windows: Optionally generate DLL module definition files automatically ... Create target property WINDOWS_EXPORT_ALL_SYMBOLS to automatically generate a module definition file from MS-compatible .obj files and give it to the linker in order to export all symbols from the .dll part of a SHARED library.	2015-07-06 11:11:02 -04:00