Bazel support about dlfcn-win32 HOT 5 OPEN

Hi @carlfm01 ,
as far as I know, there is no Bazel BUILD file available for dlfcn-win32.
However, the library is quite simple (it is just composed of the dlfcn.h header file and
the dlfcn.c source file. There are a few more details (you need to define the SHARED macro
if you are building it as a shared library, and you need to link the psapi library) but it should be fairly simple to compile in any build system, and bazel
has some nice docs on how to build C++ projects: https://docs.bazel.build/versions/master/tutorial/cpp.html and https://github.com/bazelbuild/examples/tree/master/cpp-tutorial .

As the library is relatively simple, it is not a problem to maintain several build systems upstream, so if you want to work on Bazel support I will be happy to review a PR.

from dlfcn-win32.

Thanks, really appreciate that you take the time to reply, I'll look into that. My final goal with this is to finally bring a DeepSpeech client to Windows. I'll share the results.

from dlfcn-win32.

For people interested in Bazel support, the rules_foreign_cc may be interesting.

from dlfcn-win32.

Hi, I finally compiled it using this BUILD file for Bazel

cc_library(
name = "dlfnwin",
srcs = ["dlfcn.c"],
hdrs = ["dlfcn.h"],
linkopts = ["-DEFAULTLIB:psapi.lib"],

)

cc_library(
name = "testdl",
srcs = ["testdll.c"],
deps = [
":dlfnwin",
],

)

cc_binary(
name = "test",
srcs = ["test.c"],
deps = [
":testdl",
],

)

The problem is when I run the .exe the file the lib didn't load.

I found https://github.com/kkm000/openfst for my project. When I finish my project I'll try again.

from dlfcn-win32.

I am not a bazel user, but I have two doubts:

• Are you sure that cc_library for testdll.c is generating a shared library with the correct name testdll.dll ? The test hardcoded that that is the expected name of the plugin to load:

  dlfcn-win32/test.c

  Line 90 in f1acf5d

  library = dlopen( "testdll.dll", RTLD_GLOBAL );

  .
• Are you running the test executable in the same directory that contains the testdll.dll file? Again, that is something that is hardcoded in the test.

from dlfcn-win32.