dart-sdk/third_party/boringssl
2016-04-29 13:04:27 -07:00
..
linux-aarch64/crypto Revert BoringSSL Roll 2016-04-29 10:14:33 -07:00
linux-arm/crypto Revert BoringSSL Roll 2016-04-29 10:14:33 -07:00
linux-x86/crypto Adds back files lost during BoringSSL roll revert 2016-04-29 13:04:27 -07:00
linux-x86_64/crypto Adds back files lost during BoringSSL roll revert 2016-04-29 13:04:27 -07:00
mac-x86/crypto Adds back files lost during BoringSSL roll revert 2016-04-29 13:04:27 -07:00
mac-x86_64/crypto Adds back files lost during BoringSSL roll revert 2016-04-29 13:04:27 -07:00
win-x86/crypto Adds back files lost during BoringSSL roll revert 2016-04-29 13:04:27 -07:00
win-x86_64/crypto Adds back files lost during BoringSSL roll revert 2016-04-29 13:04:27 -07:00
.gitignore Adds back files lost during BoringSSL roll revert 2016-04-29 13:04:27 -07:00
boringssl.gypi Revert BoringSSL Roll 2016-04-29 10:14:33 -07:00
boringssl_configurations.gypi Revert BoringSSL Roll 2016-04-29 10:14:33 -07:00
boringssl_dart.gyp Revert BoringSSL Roll 2016-04-29 10:14:33 -07:00
boringssl_tests.gypi Revert BoringSSL Roll 2016-04-29 10:14:33 -07:00
BUILD.gn Revert BoringSSL Roll 2016-04-29 10:14:33 -07:00
err_data.c Revert BoringSSL Roll 2016-04-29 10:14:33 -07:00
README Breaking Change: merge BoringSSL branch into master 2015-08-26 14:42:12 +02:00

The files in this directory, except for src/, boringssl_dart.gyp, and
boringssl_configurations.gypi, are generated from the checkout of
boringssl in src/, by running the script
src/util/generate_build_files.py chromium.

That script is maintained by the chromium team, to make a gyp build
of boringssl that does not require go or perl.  We modify the main
gyp file of this build, boringssl.gyp, to add configurations for
the target architectures, creating boringssl_dart.gyp.

When updating boringssl in Dart, delete this directory,
and check out the new boringssl to src.  Then run the script, check out
our two files boringssl_dart.gyp and boringssl_configurations.gypi and commit
the changes and any added or deleted files, as well as a change to the
boringssl revision in DEPS.  If there are changes in boringssl.gyp,
consider making  similar changes to boringssl_dart.gyp
Test the changes on all platforms before committing, of course.