aboutsummaryrefslogtreecommitdiff
path: root/protoc-artifacts
Commit message (Collapse)AuthorAgeFilesLines
* Replace repo links.Feng Xiao2018-08-223-4/+4
|
* Added support for building the aarch64 and ppcle64 protoc binaries with KokoroAdam Cozzette2018-08-011-2/+3
| | | | | | | | This was fairly straightforward using the existing build-protoc.sh script. The only problem I ran into was that the x86 Docker builds create output directories owned by root, which caused some permission issues. Fortunately it was easy to get around that just by doing those Docker builds last.
* Merge branch '3.6.x' into merge-3-6-xAdam Cozzette2018-08-013-7/+18
|\
| * Updated version numbers to 3.6.1Adam Cozzette2018-07-271-1/+1
| |
| * protoc-artifacts: Update centos base from 6.6 to 6.9Eric Anderson2018-07-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This avoids the need to use "yum update && yum upgrade" in the container to be able to contact GitHub, which requires TLS 1.2[1]. I have verified that binaries built with this container still run in the previous container; no errors like "/lib64/libc.so.6: version `GLIBC_2.14' not found", which occur if using too new of a glibc when compiling. CentOS 6.6 has glibc version 2.12 release 1.209.el6. CentOS 6.9 has glibc version 2.12 release 1.149.el6. Both would upgrade to release 1.212.el6 via "yum update && yum upgrade". 1. https://githubengineering.com/crypto-deprecation-notice/
| * Updated Docker setup to use GCC 4.8Adam Cozzette2018-07-173-10/+9
| | | | | | | | | | | | | | | | | | Now that we depend on C++11, we need at least GCC 4.8 instead of 4.7. This change updates the Docker setup to continue using CentOS 6.6 but with GCC 4.8. I also added libm to the whitelist for dynamically linked libraries for the ARM64 protoc binary.
| * Add protoc release script for Linux build.Feng Xiao2018-07-151-2/+2
| |
| * Update protoc build scripts.Feng Xiao2018-07-153-173/+167
| | | | | | | | | | | | | | | | | | | | 1. Changed maven script to only do artifact uploading and removed build script invocation from it. We didn't use maven to invoke the build script before (we built protoc manually and editted pom.xml to only do uploading for previous releases), and will not use it in the future (we will use kokoro to build artifacts). 2. Cleaned up build-protoc.sh and README.md: removed the part about using maven to build and listed supported platforms explicitly.
| * Additional support for building and deploying ppcle_64 artifactsnashimus2018-07-062-11/+29
| |
* | Updated release documentation (#4973)Adam Cozzette2018-07-301-2/+4
| | | | | | | | | | | | | | | | | | I made a few small fixes to the documentation related to publishing protoc artifacts: - The target directory for Mac should be called osx instead of macos. - There needs to be a directory for aarch_64. - We need to avoid calling "mvn clean" inside the protoc-artifacts directory, since that will delete the contents of the target/ subdirectory.
* | Add protoc release script for Linux build.Feng Xiao2018-07-151-2/+2
| |
* | Update protoc build scripts.Feng Xiao2018-07-133-166/+167
| | | | | | | | | | | | | | | | | | | | 1. Changed maven script to only do artifact uploading and removed build script invocation from it. We didn't use maven to invoke the build script before (we built protoc manually and editted pom.xml to only do uploading for previous releases), and will not use it in the future (we will use kokoro to build artifacts). 2. Cleaned up build-protoc.sh and README.md: removed the part about using maven to build and listed supported platforms explicitly.
* | protoc-artifacts: Update centos base from 6.6 to 6.9Eric Anderson2018-07-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This avoids the need to use "yum update && yum upgrade" in the container to be able to contact GitHub, which requires TLS 1.2[1]. I have verified that binaries built with this container still run in the previous container; no errors like "/lib64/libc.so.6: version `GLIBC_2.14' not found", which occur if using too new of a glibc when compiling. CentOS 6.6 has glibc version 2.12 release 1.209.el6. CentOS 6.9 has glibc version 2.12 release 1.149.el6. Both would upgrade to release 1.212.el6 via "yum update && yum upgrade". 1. https://githubengineering.com/crypto-deprecation-notice/
* | Updated Docker setup to use GCC 4.8Adam Cozzette2018-07-063-10/+9
|/ | | | | | | | | Now that we depend on C++11, we need at least GCC 4.8 instead of 4.7. This change updates the Docker setup to continue using CentOS 6.6 but with GCC 4.8. I also added libm to the whitelist for dynamically linked libraries for the ARM64 protoc binary.
* Update version number to 3.6.0Jisi Liu2018-05-141-1/+1
|
* Merge branch (#4466)Paul Yang2018-04-021-1/+1
| | | | | | | | * Fix setup.py for windows build. * Bump version number to 3.5.2 * Cat the test-suite.log on errors for presubits
* Merge pull request #4411 from pravin-dsilva/protobuf-ppc64leFeng Xiao2018-04-023-2/+10
|\ | | | | Add support for Power (ppc64le) arch
| * Add support for power ppc64lepravin-dsilva2018-03-223-2/+10
| |
* | protoc-artifacts: Use ENTRYPOINT to enable devtoolset-1.1Eric Anderson2018-03-283-2/+17
| | | | | | | | | | | | | | ENTRYPOINT is used even when other commands are specified on the "docker run" command line. This allows running one-off commands in the docker image (especially combined with volume binding with the host) with the correct environment variables.
* | protoc-artifacts: Avoid storing temporary files and use fewer layersEric Anderson2018-03-281-7/+11
| | | | | | | | | | This is just better Dockerfile hygene as it produces smaller resulting images with fewer useless files.
* | protoc-artifacts: Avoid checking out protobuf codeEric Anderson2018-03-282-3/+5
|/ | | | | | | | | | It is a bad idea to check out code into the docker image, as it will be out-of-date. It is better to have the image just be the environment, and let any scripts that need source check them out themselves. This fixes #4419 in that it allows the image to build again, albeit users would need to use wget to grab the source of the version of protobuf they wish.
* Merge pull request #4291 from google/3.5.xJisi Liu2018-02-261-1/+1
|\ | | | | Merge 3.5.x to master
| * Bump protoc-artifact version for a patch rebuildJisi Liu2018-01-051-1/+1
| |
* | Merge remote-tracking branch 'origin/3.5.x' into masterJisi Liu2018-01-031-1/+1
|\|
| * Update version number to 3.5.1Jisi Liu2017-12-191-1/+1
| |
* | Merge branch '3.5.x' into 3.5.x-mergeAdam Cozzette2017-11-304-7/+23
|\|
| * Update protoc-artfactsJisi Liu2017-11-131-5/+6
| |
| * Fix arm64 nameJisi Liu2017-11-091-2/+2
| |
| * Supports Arm64 (aarch64) protoc artifactsJisi Liu2017-11-092-1/+16
| |
| * Update version number to 3.5.0Jisi Liu2017-11-021-1/+1
| |
* | Update README.mdJisi Liu2017-11-131-4/+7
|/
* Merge remote-tracking branch 'origin/3.4.x' into masterJisi Liu2017-10-111-1/+1
|\
| * Bump version for minor releaseJisi Liu2017-09-141-1/+1
| |
* | Merge remote-tracking branch 'origin/3.4.x' into mergemasterJisi Liu2017-08-183-5/+12
|\|
| * Update readmeJisi Liu2017-08-151-0/+6
| |
| * static link for 32 bit build as well.Jisi Liu2017-08-151-1/+1
| |
| * Update comments that cross compile is feasible nowJisi Liu2017-08-151-2/+0
| | | | | | | | Need to install mingw-w64 on linux to cross compile
| * First try static linking pthreadJisi Liu2017-08-151-2/+5
| |
| * Update version number for 3.4.0Jisi Liu2017-07-241-1/+1
| |
* | Merge pull request #3317 from ejona86/protoc-artifacts-jdk8Jisi Liu2017-08-181-2/+3
|\ \ | | | | | | protoc-artifacts: Bump JDK to 8u131
| * | protoc-artifacts: Bump JDK to 8u131Eric Anderson2017-07-051-2/+3
| | | | | | | | | | | | | | | The update 45 download process no longer works, as it requires a login to access the old build.
* | | Merge pull request #3375 from TeBoring/3.3.xPaul Yang2017-07-191-1/+1
|\ \ \ | |_|/ |/| | Merge 3.3.x into master
| * | Merge 3.3.x into masterBo Yang2017-07-181-1/+1
| |\ \ | | |/ | |/|
| | * Update version number to 3.3.2Bo Yang2017-06-211-1/+1
| | |
| | * Update version number to 3.3.1Feng Xiao2017-05-081-1/+1
| | |
* | | Add note about includes to READMEDaniel Taylor2017-07-181-0/+4
|/ / | | | | Ran into an issue today where a machine had the `protoc` compiler but not the include files. Took a while to sort out, and this added note to the README included in every zip should help.
* / Workaround the docker bug when compiling artifactsŁukasz Strzałkowski2017-05-111-1/+1
|/ | | | | | | | | This is a workaround (https://github.com/moby/moby/issues/10180#issuecomment-190429512) the docker issue (https://github.com/moby/moby/issues/10180) which breaks protoc-artifacts build process with following error ```Rpmdb checksum is invalid: dCDPT(pkg checksums): devtoolset-1.1-elfutils.x86_64 0:0.154-6.el6 - u The command '/bin/sh -c yum clean all && yum install -y devtoolset-1.1 devtoolset-1.1-libstdc++-devel devtoolset-1.1-libstdc++-devel.i686' returned a non-zero code: 1``` https://github.com/moby/moby/issues/10180#issuecomment-190429512
* Update version number and changelog for 3.3.0Feng Xiao2017-04-051-1/+1
|
* Prefer the term "3-Clause BSD License" over "New BSD License"Sebastian Schuberth2017-02-281-1/+1
| | | | The first is the newer name, which is also more telling.
* Fix links to the New BSD License in meta-dataSebastian Schuberth2017-02-281-1/+1
| | | | | The "New BSD License" is the "3-Clause BSD License", but the links were pointing to the "2-Clause BSD License".
generated by cgit v1.2.3 (git 2.39.1) at 2024-04-29 04:04:42 +0000