aboutsummaryrefslogtreecommitdiffstats
path: root/appveyor.yml
diff options
context:
space:
mode:
authorPavel Samolysov <samolisov@gmail.com>2019-01-14 15:42:36 +0300
committerPavel Samolysov <samolisov@gmail.com>2019-01-14 16:20:56 +0300
commitc868da198834e61cce051775b7e0f9bafd594d89 (patch)
treea0a0d4bbf127a45cacf633f3e346a7aee03d2c21 /appveyor.yml
parent0599a7b8410dc5cfdb477900b280475ae775d7f9 (diff)
downloadgoogletest-c868da198834e61cce051775b7e0f9bafd594d89.tar.gz
googletest-c868da198834e61cce051775b7e0f9bafd594d89.tar.bz2
googletest-c868da198834e61cce051775b7e0f9bafd594d89.zip
Enable building as a shared library (dll) on Windows with Bazel
While the google test library is being built as a shared library using Bazel, so that there is a rule like cc_test( name = "iterator_traits_test", linkstatic = 0, deps = ["@gtest//:gtest_main"], ... ) in a BUILD file, the following error appears on Windows: INFO: Found 1 test target... ERROR: C:/../external/gtest/BUILD.bazel:55:1: output 'external/gtest/gtest.if.lib' was not created ERROR: C:/../external/gtest/BUILD.bazel:55:1: not all outputs were created or valid Target //test:iterator_traits_test failed to build The reason is a missing "win_def_file" attribute of the "gtest" and "gtest_main" rules in the BUILD.bazel inside the google test library package. The "windows_export_all_symbols" feature is added to the rules, this feature forces Bazel to export all symbols from the google test library to linker. I believe exporting all symbols from a testing library makes no problem for the application from a point of view on encapsulation. Signed-off-by: Pavel Samolysov <samolisov@gmail.com>
Diffstat (limited to 'appveyor.yml')
0 files changed, 0 insertions, 0 deletions