aboutsummaryrefslogtreecommitdiff
path: root/tool
diff options
context:
space:
mode:
authorDavid Benjamin <davidben@google.com>2023-02-04 20:06:30 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>2023-02-14 20:26:56 +0000
commit0e68520eb27b1f37038e9d0772cfee1d015b50c3 (patch)
tree7cf105f0a92c22c3d2ea4a4c29cac46b2d7f504a /tool
parentde12e3cabcb466cdf96c90d9bff0d919af71d561 (diff)
downloadboringssl-0e68520eb27b1f37038e9d0772cfee1d015b50c3.zip
boringssl-0e68520eb27b1f37038e9d0772cfee1d015b50c3.tar.gz
boringssl-0e68520eb27b1f37038e9d0772cfee1d015b50c3.tar.bz2
Specify -Iinclude with the crypto target.
It's unclear to me whether doing it target-by-target is an improvement in crypto/fipsmodule, but this otherwise does seem a bit tidier. This aligns with CMake's documentation and "modern CMake" which prefers this pattern. Change-Id: I36c81842bff8b36eeaaf5dd3e0695fb45f3376c9 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/56585 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Bob Beck <bbe@google.com>
Diffstat (limited to 'tool')
-rw-r--r--tool/CMakeLists.txt2
1 files changed, 0 insertions, 2 deletions
diff --git a/tool/CMakeLists.txt b/tool/CMakeLists.txt
index e84d229..9cc7d28 100644
--- a/tool/CMakeLists.txt
+++ b/tool/CMakeLists.txt
@@ -1,5 +1,3 @@
-include_directories(../include)
-
add_executable(
bssl