Opened 7 years ago
Closed 7 years ago
#12047 closed Bugs (invalid)
Drive letter in Windows is ignored for Build --libdir option
| Reported by: | Edward Diener | Owned by: | Vladimir Prus |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | build |
| Version: | Boost 1.61.0 | Severity: | Problem |
| Keywords: | libdir | Cc: |
Description
If the b2 command line specifies --libdir=DriveLetter:/somepath the DriveLetter is completely dropped when Boost build calculates the path and so Boost build considers the --libdir path as /somepath on the current drive.
Change History (3)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
You are right and my report is erroneous. The 'install' rule was hardcoding a path instead of using --libdir in the jam file I was executing.
comment:3 by , 7 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I can't reproduce this:
boost-git$ b2 --libdir=D:\Boost\lib -n --with-system install ... common.copy D:\Boost\lib\libboost_system-vc140-mt-1_61.lib copy /b "bin.v2\libs\system\build\msvc-14.0\release\link-static\threading-multi\libboost_system-vc140-mt-1_61.lib" + this-file-does-not-exist-A698EE7806899E69 "D:\Boost\lib\libboost_system-vc140-mt-1_61.lib"