On Wed, 10 Apr 2024 21:10:27 GMT, Magnus Ihse Bursie <i...@openjdk.org> wrote:
>> This is the pinnacle of the recent stream of refactorings in the build >> system. This patch introduces a more abstract concept of "JDK_LIBS", where >> only the library name (e.g. "java" or "java.desktop:jawt") is specified, and >> the build system turns this into suitable linker flags: `-ljawt -L<correct >> path>` or `jawt.lib -libpath:<correct path>`, depending on linker. It will >> also automatically create proper dependencies. > > Magnus Ihse Bursie has updated the pull request incrementally with one > additional commit since the last revision: > > Fix missing lib prefix Quick Question: On Windows, does it set LIBPATH to the path of the .lib import library? If so, are the import libraries in the same directories as the compiled .dll files? Reason is that gcc does not depend on .lib import libraries and directly links to the dll file, and if the path given is to the non-existent .lib file when compiling with gcc, linking will fail ------------- PR Comment: https://git.openjdk.org/jdk/pull/18649#issuecomment-2054974650
