Description of the bug:
Since bazelisk moved us to 6.3.0 yesterday, our libraries have not linked. This is a regression in 6.3.0 vs 6.2.0
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
http_archive('a')
cc_import(name='b', interface_library=b.lib, shared_library=b.dll)
cc_library(name='c_base', srcs=[x,y,z], deps=['@a//:b'])
cc_shared_library(name='c', deps=[":c_base"])
6.2.0: c_base links fine, linker params file includes b.lib
6.3.0: c_base not linked, linker params file is missing b.lib
Which operating system are you running Bazel on?
Windows
What is the output of bazel info release?
release 6.3.0
If bazel info release returns development version or (@non-git), tell us how you built Bazel.
No response
What's the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD ?
No response
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
Between 6.2.0 and 6.3.0, will try to run bisect
Have you found anything relevant by searching the web?
No
Any other information, logs, or outputs that you want to share?
No response
Description of the bug:
Since bazelisk moved us to 6.3.0 yesterday, our libraries have not linked. This is a regression in 6.3.0 vs 6.2.0
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
http_archive('a')
cc_import(name='b', interface_library=b.lib, shared_library=b.dll)
cc_library(name='c_base', srcs=[x,y,z], deps=['@a//:b'])
cc_shared_library(name='c', deps=[":c_base"])
6.2.0: c_base links fine, linker params file includes b.lib
6.3.0: c_base not linked, linker params file is missing b.lib
Which operating system are you running Bazel on?
Windows
What is the output of
bazel info release?release 6.3.0
If
bazel info releasereturnsdevelopment versionor(@non-git), tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse master; git rev-parse HEAD?No response
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
Between 6.2.0 and 6.3.0, will try to run bisect
Have you found anything relevant by searching the web?
No
Any other information, logs, or outputs that you want to share?
No response