Chiebot-Mirror/grpc - grpc - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
Jan Tattermusch	f098606c4a	Revert "Revert "Reintroduce #21527 (boringssl submodule unification)"" This reverts commit `cca892022b`.	5 years ago
hcaseyal	cca892022b	Revert "Reintroduce #21527 (boringssl submodule unification)"	5 years ago
Jan Tattermusch	e7e5d0198f	Revert "Revert "Unify boringssl submodules and use non-developer boringssl cmake build"" This reverts commit `fe2242e603`.	5 years ago
Jan Tattermusch	fe2242e603	Revert "Unify boringssl submodules and use non-developer boringssl cmake build"	5 years ago
Jan Tattermusch	e37e9aca2b	set ssl.cmake to use CMakeLists.txt from boringssl-with-bazel	5 years ago
Zack Galbreath	5f073edc8f	Conditionally set OPENSSL_NO_ASM for Visual Studio This configuration variable was originally set due to a bug in CMake. We now build BoringSSL with assembly optimizations on Visual Studio provided that the version of CMake we're using is "new enough" (3.13+) and the NASM assembler is installed.	5 years ago
Zack Galbreath	cad4c32d43	Allow gRPC_INSTALL with module providers	5 years ago
Esun Kim	8de389b940	Update by review	5 years ago
Kyle Edwards	6f881ab292	Fix various CMake style issues Remove some spaces at the end of lines. Change how variables are referenced inside if() statements. Remove the space between if/endif and the first parenthesis. Remove the duplicated condition from endif() blocks. Make indentation more consistent. Remove unneeded duplicate PRIVATE keywords from target_include_directories(). Remove redundant set_source_files_properties() call, as the file is already GENERATED.	5 years ago
Jan Tattermusch	7132cd7164	cmake: disable assembly optimizations only when necessary	6 years ago
Jan Tattermusch	6750d42ef1	fine tune cmake find_package usage	7 years ago
Stefan Hacker	471a5dc18b	Fix cmake export for grpc This patch fixes two issues with the targets exported by the grpc cmake build: - Install directories are now given relative instead of absolute. Previously the exported targets would contain absolute paths to their created targets when they should be relative. The actual installation location stays the same as cmake automatically interprets the paths relative to CMAKE_INSTALL_PREFIX - ZLIB and OpenSSL are now linked using targets instead of the legacy library variables if possible. Using the legacy paths produces absolute paths to those dependencies in the export. With this change cmake inserts the target names instead. With these changes no more absolute paths are inserted into the export allowing the install location to be used as an artifact that can be moved or transfered to another machine and used there.	7 years ago
Jan Tattermusch	f38b1526f8	simplify top level CMakeLists.txt	7 years ago

14 Commits (5d9f743a40fa1ca239b810cc8e7c0955776dcf34)