casa-mp-base
Public
Commits
Toby Peterson authored aa97f013455
| 1 1 | # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4 |
| 2 2 | |
| 3 3 | PortSystem 1.0 |
| 4 4 | PortGroup github 1.0 |
| 5 5 | PortGroup cxx11 1.1 |
| 6 6 | |
| 7 7 | # see note to remove block below at next update |
| 8 - | github.setup google protobuf 3.9.2 v |
| 8 + | github.setup protocolbuffers protobuf 3.9.2 v |
| 9 9 | revision 0 |
| 10 10 | |
| 11 11 | checksums rmd160 51b60b25ba285d87ae16f01ad2d3b21916c2bae8 \ |
| 12 12 | sha256 1891110cce323fe56b509da3589f03756c7eaf462a60971cb1c4af4efb154f69 \ |
| 13 13 | size 4543063 |
| 14 14 | |
| 15 15 | name protobuf3-cpp |
| 16 16 | categories devel |
| 17 17 | maintainers nomaintainer |
| 18 18 | license BSD |
| 31 31 | a variety of data streams and using a variety of \ |
| 32 32 | languages. You can even update your data structure \ |
| 33 33 | without breaking deployed programs that are compiled \ |
| 34 34 | against the "old" format. You specify how you want \ |
| 35 35 | the information you're serializing to be structured by \ |
| 36 36 | defining protocol buffer message types in .proto \ |
| 37 37 | files. Each protocol buffer message is a small \ |
| 38 38 | logical record of information, containing a series of \ |
| 39 39 | name-value pairs. |
| 40 40 | |
| 41 + | homepage https://developers.google.com/protocol-buffers/ |
| 42 + | |
| 41 43 | github.tarball_from releases |
| 42 44 | distname protobuf-cpp-${version} |
| 43 45 | worksrcdir protobuf-${version} |
| 44 46 | |
| 45 47 | |
| 46 48 | ###### REMOVE AT NEXT UPDATE |
| 47 49 | # no longer needed as all our c++11 compilers support thread_local now |
| 48 50 | if {${os.platform} eq "darwin" && ${os.major} < 11} { |
| 49 51 | if {[string match *clang* ${configure.compiler}] && ${configure.cxx_stdlib} eq "macports-libstdc++"} { |
| 50 52 | # GCC emulates thread-local storage |