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
..
sub	Fix auto export symbols for Dlls containing /bigobj for 64bit builds.	2015-11-19 17:21:03 -05:00
AutoExport.cmake	bindexplib: Always export executable symbols, even they are also readable	2017-02-28 09:49:12 -05:00
AutoExportBuild-stderr.txt	Windows: Optionally generate DLL module definition files automatically	2015-07-06 11:11:02 -04:00
CMakeLists.txt	Windows: Optionally generate DLL module definition files automatically	2015-07-06 11:11:02 -04:00
foo.c	Windows: Optionally generate DLL module definition files automatically	2015-07-06 11:11:02 -04:00
hello2.c	Windows: Honor WINDOWS_EXPORT_ALL_SYMBOLS for executables with exports	2016-07-11 09:41:04 -04:00
hello.cxx	Revise C++ coding style using clang-format	2016-05-16 16:05:19 -04:00
hello.h	Windows: Optionally generate DLL module definition files automatically	2015-07-06 11:11:02 -04:00
nop.asm	bindexplib: Always export executable symbols, even they are also readable	2017-02-28 09:49:12 -05:00
objlib.c	VS: Fix WINDOWS_EXPORT_ALL_SYMBOLS for object libraries	2016-07-21 11:05:22 -04:00
RunCMakeTest.cmake	Drop Visual Studio 6 generator	2016-03-09 09:42:18 -05:00
say.cxx	bindexplib: Always export executable symbols, even they are also readable	2017-02-28 09:49:12 -05:00
world.cxx	Windows: Optionally generate DLL module definition files automatically	2015-07-06 11:11:02 -04:00