rust/tests/run-make/link-native-static-lib-to-dylib/foo.c

// ignore-license

#ifdef _WIN32
__declspec(dllexport)
#endif
void foo() {}
Clean up tidy scripts, coverage, performance This restructures tidy.py to walk the tree itself, and improves performance considerably by not loading entire files into buffers for licenseck. Splits build rules into 'tidy', 'tidy-basic', 'tidy-binaries', 'tidy-errors', 'tidy-features'. 2015-01-24 17:18:19 -06:00			`// ignore-license`
rmake: Get all tests passing on MSVC 2015-08-26 18:57:56 -05:00
			`#ifdef _WIN32`
			`__declspec(dllexport)`
			`#endif`
rustc: Link entire archives of native libraries As discovered in #15460, a particular #[link(kind = "static", ...)] line is not actually guaranteed to link the library at all. The reason for this is that if the external library doesn't have any referenced symbols in the object generated by rustc, the entire library is dropped by the linker. For dynamic native libraries, this is solved by passing -lfoo for all downstream compilations unconditionally. For static libraries in rlibs this is solved because the entire archive is bundled in the rlib. The only situation in which this was a problem was when a static native library was linked to a rust dynamic library. This commit brings the behavior of dylibs in line with rlibs by passing the --whole-archive flag to the linker when linking native libraries. On OSX, this uses the -force_load flag. This flag ensures that the entire archive is considered candidate for being linked into the final dynamic library. This is a breaking change because if any static library is included twice in the same compilation unit then the linker will start emitting errors about duplicate definitions now. The fix for this would involve only statically linking to a library once. Closes #15460 [breaking-change] 2014-07-30 09:44:20 -05:00			`void foo() {}`