PiperOrigin-RevId: 257589675

PiperOrigin-RevId: 257474675

PiperOrigin-RevId: 255917787

PiperOrigin-RevId: 255588927

PiperOrigin-RevId: 255586012

PiperOrigin-RevId: 255137607

The previous syntax for GTEST_ADD_TESTS only works with later versions of cmake, see e.g. https://cmake.org/cmake/help/v3.7/module/FindGTest.html?highlight=gtest_add_tests

Since we use cmake 3.7.1 in kokoro we cannot run these tests like this. Furthermore, the function gtest_add_tests is problematic for parametrized tests. Hence, we remove it and replace it with the simpler add_tests.

PiperOrigin-RevId: 253555478

https://github.com/google/tink/issues/217 and
https://github.com/google/tink/issues/218, thanks DazWilkin!)

PiperOrigin-RevId: 253220034

There were a couple of places where `AeadKeyTemplates.AES_128_GCM` was mentioned. Replaced it with `AeadKeyTemplates.AES128_GCM` as it's the correct name of the constant.

https://github.com/google/tink/commit/4c2769c05e9c9dcdcc11f952c7e6ae9ca1d32ece

PiperOrigin-RevId: 251443876

Thanks!

PiperOrigin-RevId: 248717508

PiperOrigin-RevId: 248501728

PiperOrigin-RevId: 247178623

The issue was with grpc: https://github.com/bazelbuild/bazel/issues/4341

PiperOrigin-RevId: 245104328

PiperOrigin-RevId: 247178623

Fixes #197

PiperOrigin-RevId: 244947463
GitOrigin-RevId: 681b99a8a003561a713671b8c6175ccf50463c2c

PiperOrigin-RevId: 244947053
GitOrigin-RevId: 411f1a314678e2feae932d57b2ecc90408b6c4cb

PiperOrigin-RevId: 244946416
GitOrigin-RevId: d5aa347e97b5364faba3040d57daf7a4503ea802

PiperOrigin-RevId: 240532943
GitOrigin-RevId: d2af6ef633ccb66804e66c34a3c0f20a2db393e3

PiperOrigin-RevId: 239454204
GitOrigin-RevId: 08c50f85852a6fa296699ae570351006f0b7362f

PiperOrigin-RevId: 238114107
GitOrigin-RevId: b423179a4f58498a02224ab84fc45a5fb16292fb

Update HOWTO so that the variables are correctly named in the example code on reading and writing keysets.

PiperOrigin-RevId: 237245144
GitOrigin-RevId: 5c38e8efbf5424b8f21ac236ba65677a42ceeb6e

PiperOrigin-RevId: 235621033
GitOrigin-RevId: 4ee8278722a160fba83a2f480b5431af066e84cc

PiperOrigin-RevId: 232313891
GitOrigin-RevId: 43c4ae8550fea1040b2d8a4aa671a7697cd05995

PiperOrigin-RevId: 230785575
GitOrigin-RevId: b9a858a2c74ef3d7a5e9d6adca72d4b02b6ff621

PiperOrigin-RevId: 229521919
GitOrigin-RevId: 4574e5bc99c61ac531c9ef27ca9bd408391bc6fa

PiperOrigin-RevId: 229172174
GitOrigin-RevId: c9b09dd03626dd099076917a69d0d756b52eb35a

1. Why is this change neccesary?
Bazel sometimes removes the previous build targets if you follow the order of
the C++ How-To.

2. How does it address the issue?
The instructions order was modified to prevent Bazel from deleting previous
builds while retaining functionality.

3. What side effects does this change have?
Closes #134

PiperOrigin-RevId: 228697763
GitOrigin-RevId: 54808712d432100ab4efc079a40a185c4116fd4a

PiperOrigin-RevId: 221436661
GitOrigin-RevId: 7e3e6a1c69adac8c6e66d40ebfce00e5e4831ec4

PiperOrigin-RevId: 221077415
GitOrigin-RevId: 23841c3ed1685ef2b507ccdb50fe5740d28887a7

PiperOrigin-RevId: 217928606
GitOrigin-RevId: bb19ba027b28f89324532d95f51e2e361c269488

PiperOrigin-RevId: 217724309
GitOrigin-RevId: c842766df8eb0e72acc442803ee922c8e0cb6617

PiperOrigin-RevId: 217271413
GitOrigin-RevId: 36644d2df76eae91f8333d3a61843071501344a1

PiperOrigin-RevId: 215902831
GitOrigin-RevId: 9a3ed3eceea6d70f8f6ebaf4c5be2f93cd159d1c

Kokoro hasn't failed because its macOS and Ubuntu machines are using old Bazel versions.

Related issues:
https://github.com/google/tink/issues/131
https://github.com/google/tink/issues/136
https://github.com/bazelbuild/bazel/issues/5997
https://github.com/bazelbuild/bazel/issues/5594

PiperOrigin-RevId: 215787620
GitOrigin-RevId: 7b978f1374938e4b839f8357fc50d36b7ab96be5