When we use dllexport properly for shared libraries on windows, there's no longer any issue with linking the object files for e.g. libavcodec statically into checkasm. (It's still not possible to link the built object files for e.g. libavformat statically to libavcodec though, since libavformat exepcts to load av_export_* symbols from a DLL.)
This reverts commit 4e62b57ee03928c12a3119dcaf78ffa1f4d6985f. --- tests/fate/checkasm.mak | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/fate/checkasm.mak b/tests/fate/checkasm.mak index 5721f1f..939eb56 100644 --- a/tests/fate/checkasm.mak +++ b/tests/fate/checkasm.mak @@ -19,5 +19,5 @@ $(FATE_CHECKASM): tests/checkasm/checkasm$(EXESUF) $(FATE_CHECKASM): CMD = run tests/checkasm/checkasm --test=$(@:fate-checkasm-%=%) $(FATE_CHECKASM): REF = /dev/null -FATE-$(CONFIG_STATIC) += $(FATE_CHECKASM) +FATE += $(FATE_CHECKASM) fate-checkasm: $(FATE_CHECKASM) -- 2.7.4 _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
