aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/cc/link-rule.cxx
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2020-03-10 12:11:45 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2020-03-10 12:11:45 +0200
commitd932899aa393e36f59ddc0480f2675a340f7960c (patch)
tree718c4e5a11d2f1f029138e6e9187d6143308f590 /libbuild2/cc/link-rule.cxx
parent386c0bcda597914671dfeb4e1391f41e71465e91 (diff)
Force hard links inside backlinked DLL assembly directory
Windows does not allow the manifest file inside to be a symlink for some (probably security) reasons.
Diffstat (limited to 'libbuild2/cc/link-rule.cxx')
-rw-r--r--libbuild2/cc/link-rule.cxx3
1 files changed, 2 insertions, 1 deletions
diff --git a/libbuild2/cc/link-rule.cxx b/libbuild2/cc/link-rule.cxx
index 056c5c4..5917419 100644
--- a/libbuild2/cc/link-rule.cxx
+++ b/libbuild2/cc/link-rule.cxx
@@ -1076,7 +1076,8 @@ namespace build2
// The problem is the Windows DLL assembly "logic" refuses to
// recognize a junction as a valid assembly for some reason. So we
// are going to resort to copy-link (i.e., a real directory with a
- // bunch of links).
+ // bunch of links). Note also that while DLLs can be symlinked,
+ // the assembly manifest cannot (has to be hard-linked or copied).
//
// Interestingly, the directory symlink works just fine under
// Wine. So we only resort to copy-link'ing if we are running on