You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

88 lines
3.2 KiB

##
## grpc.spec -- OpenPKG RPM Package Specification
## Copyright (c) 2000-2022 OpenPKG Project <http://openpkg.org/>
##
## Permission to use, copy, modify, and distribute this software for
## any purpose with or without fee is hereby granted, provided that
## the above copyright notice and this permission notice appear in all
## copies.
##
## THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
## WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
## MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
## IN NO EVENT SHALL THE AUTHORS AND COPYRIGHT HOLDERS AND THEIR
## CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
## SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
## LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
## USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
## ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
## OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
## OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
## SUCH DAMAGE.
##
# package information
Name: grpc
Summary: Google Remote Procedure Call (RPC)
URL: http://grpc.io/
Vendor: Google Inc.
Packager: OpenPKG Project
Distribution: OpenPKG Community
Class: EVAL
Group: Networking
License: Apache
Version: 1.22.0
Release: 20190705
# list of sources
Source0: https://github.com/grpc/grpc/archive/v%{version}.tar.gz
Patch0: grpc.patch
# build information
BuildPreReq: OpenPKG, openpkg >= 20160101, gcc, gcc::with_cxx = yes
PreReq: OpenPKG, openpkg >= 20160101
BuildPreReq: protobuf
PreReq: protobuf
%description
Google Remote Procedure Call (gRPC) is a Google Protocol Buffer
based Remote Procedure Call (RPC) mechanism. In gRPC a client
application can directly call methods on a server application on
a different machine as if it was a local object, making it easier
for you to create distributed applications and services. As in
many RPC systems, gRPC is based around the idea of defining a
service, specifying the methods that can be called remotely with
their parameters and return types. On the server side, the server
implements this interface and runs a gRPC server to handle client
calls. On the client side, the client has a stub (referred to as
just a client in some languages) that provides the same methods as
the server.
%track
prog grpc = {
version = %{version}
url = https://github.com/grpc/grpc/releases
regex = v(\d+\.\d+\.\d+)\.tar\.gz
}
%prep
%setup -q
%patch -p0
%build
%{l_make} %{l_mflags} \
CC="%{l_cc} %{l_cflags -O} %{l_cppflags} %{l_ldflags}" \
CXX="%{l_cc} %{l_cxxflags -O} %{l_cppflags} %{l_ldflags}" \
PROTOC="protoc %{l_cppflags}"
%install
%{l_make} %{l_mflags} install prefix=$RPM_BUILD_ROOT%{l_prefix}
rm -f $RPM_BUILD_ROOT%{l_prefix}/lib/*.so*
rm -rf $RPM_BUILD_ROOT%{l_prefix}/src
strip $RPM_BUILD_ROOT%{l_prefix}/bin/* >/dev/null 2>&1 || true
%{l_rpmtool} files -v -ofiles -r$RPM_BUILD_ROOT %{l_files_std}
%files -f files
%clean