Using dlfcn-win32 as a subproject of libbacktrace, gollvm about dlfcn-win32

[advancedwebdeveloper]

I presume that this header

-- Looking for link.h
-- Looking for link.h - not found

is also related.

https://github.molgen.mpg.de/git-mirror/glibc/blob/master/include/link.h#L1 threw https://github.molgen.mpg.de/git-mirror/glibc/blob/master/include/link.h#L2 contains such a claim:

Data structure for communication from the run-time dynamic linker for loaded ELF shared objects.
. It looks like it would have zero sense to have this header checked, if dlfcn-win32 would be used (as a drop-in replacement).

Ivan

[traversaro]

Hi @advancedwebdeveloper,
the dlfcn-win32 library is composed only by the dlfcn.h and dlfcn.c, that can be either be used compiled as a library on its own and then used in your build system, or including directly the files in your project (in this case anyhow note that you need to comply with the LGPL license under which dlfcn-win32 is licensed.

As explained by ianlancetaylor/libbacktrace#46 (comment), some build systems check if the system provides headers such as dlfcn.h, but depending on the project it is possible that the project is able to compile even if a given system header is not found.

Regarding the link.h header, dlfcn-win32 does not provide it.

If this answer is ok for you, feel free to close the issue, thanks.

[traversaro]

I am closing the issue due to the lack of further responses, feel free to comment if there are further doubts.