[llvm-bugs] [Bug 36456] New: #pragma comment(lib) with relative path does not work in LLD
via llvm-bugs
llvm-bugs at lists.llvm.org
Tue Feb 20 06:43:27 PST 2018
https://bugs.llvm.org/show_bug.cgi?id=36456
Bug ID: 36456
Summary: #pragma comment(lib) with relative path does not work
in LLD
Product: lld
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: COFF
Assignee: unassignedbugs at nondot.org
Reporter: alexandre.ganea at ubisoft.com
CC: llvm-bugs at lists.llvm.org
We've got a case where a #pragma comment(lib...) directive is used in a
compilation unit, however with a relative path. Such as:
#define LIB_PATH "..\\..\\..\\..\\..\\extern\\OpenExr220\\lib\\"
#pragma comment(lib, LIB_PATH "IlmImf-2_2.lib")
This works happily with link.exe, however lld doesn't like it and reports the
library as "not found". The path is relative to the compilation unit. I'm not
sure if link.exe uses that, or the fact that /LIBPATH: already specifies a path
to the correct lib.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20180220/e757b383/attachment.html>
More information about the llvm-bugs
mailing list