search for: test_ansi_c_plugin_la_cflags

...ES += test-ansi-c-plugin.la > +test-ansi-c.sh: test-ansi-c-plugin.la > + > +test_ansi_c_plugin_la_SOURCES = \ > + test-ansi-c-plugin.c \ > + $(top_srcdir)/include/nbdkit-plugin.h > +test_ansi_c_plugin_la_CPPFLAGS = \ > + -std=c90 -pedantic \ > + -I$(top_srcdir)/include > +test_ansi_c_plugin_la_CFLAGS = \ > + $(WARNINGS_CFLAGS) > +# For use of the -rpath option, see: > +# https://lists.gnu.org/archive/html/libtool/2007-07/msg00067.html > +test_ansi_c_plugin_la_LDFLAGS = \ > + -module -avoid-version -shared -rpath /nowhere Looks sane, if it still works without <config.h&...

We previously discussed allowing the plugin API to be consumed by non-GCC/non-Clang/old compilers. This implements a test. Rich.

...this and add a dependency. +noinst_LTLIBRARIES += test-ansi-c-plugin.la +test-ansi-c.sh: test-ansi-c-plugin.la + +test_ansi_c_plugin_la_SOURCES = \ + test-ansi-c-plugin.c \ + $(top_srcdir)/include/nbdkit-plugin.h +test_ansi_c_plugin_la_CPPFLAGS = \ + -std=c90 -pedantic \ + -I$(top_srcdir)/include +test_ansi_c_plugin_la_CFLAGS = \ + $(WARNINGS_CFLAGS) +# For use of the -rpath option, see: +# https://lists.gnu.org/archive/html/libtool/2007-07/msg00067.html +test_ansi_c_plugin_la_LDFLAGS = \ + -module -avoid-version -shared -rpath /nowhere + if HAVE_CXX # This builds a plugin and a filter using the C++ compiler....

...310,6 +312,7 @@ test_shutdown_plugin_la_CFLAGS = $(WARNINGS_CFLAGS) test_shutdown_plugin_la_LDFLAGS = \ -module -avoid-version -shared $(NO_UNDEFINED_ON_WINDOWS) -rpath /nowhere \ $(NULL) +test_shutdown_plugin_la_LIBADD = $(LINK_LIBNBDKIT_ON_WINDOWS) endif HAVE_PLUGINS @@ -364,6 +367,7 @@ test_ansi_c_plugin_la_CFLAGS = $(WARNINGS_CFLAGS) test_ansi_c_plugin_la_LDFLAGS = \ -module -avoid-version -shared $(NO_UNDEFINED_ON_WINDOWS) -rpath /nowhere \ $(NULL) +test_ansi_c_plugin_la_LIBADD = $(LINK_LIBNBDKIT_ON_WINDOWS) endif CAN_TEST_ANSI_C if HAVE_CXX @@ -389,6 +393,7 @@ test_cxx_plugin_la_CXXFLAGS = $(WARN...

This is an incomplete port to Windows. Currently the server compiles and starts up successfully, but goes into an infinite loop when you connect to it. Nevertheless I think the approach is ready for feedback. This being Windows the changes go quite deep. Rich.

This creates libnbdkit.so as discussed in the following thread: https://www.redhat.com/archives/libguestfs/2020-March/thread.html#00203 test-delay-shutdown.sh fails for unclear reasons. This series starts by reverting "tests: Don't strand hung nbdkit processes" which is because several other tests fail randomly unless I revert this patch. I didn't investigate this yet so it

Also available here: https://github.com/rwmjones/nbdkit/tree/2020-windows-mingw This is the port to Windows using native Windows APIs (not MSYS or Cygwin). This patch series is at the point where it basically now works. I can run the server with the memory plugin, and access it remotely using guestfish, creating filesystems and so on without any apparent problems. Nevertheless there are many

Also available here: https://github.com/rwmjones/nbdkit/tree/2020-windows-mingw-nolib After a lot of work I have made the port to Windows work without using a separate library. Instead, on Windows only, we build an "import library" (library of stubs) which resolves references to nbdkit_* functions in the main program and fixes up the plugin, basically the first technique outlined in