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.
 
 
 
 
 
 

85 lines
2.9 KiB

##
## jam.spec -- OpenPKG RPM Package Specification
## Copyright (c) 2000-2006 OpenPKG Foundation e.V. <http://openpkg.net/>
## Copyright (c) 2000-2006 Ralf S. Engelschall <http://engelschall.com/>
##
## 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: jam
Summary: Perforce Jam
URL: http://www.perforce.com/jam/jam.html
Vendor: Perforce Software, Inc.
Packager: OpenPKG Foundation e.V.
Distribution: OpenPKG Community
Class: PLUS
Group: Building
License: Freely distributable
Version: 2.5
Release: 20061013
# list of sources
Source0: ftp://ftp.perforce.com/pub/jam/jam-%{version}.tar
# build information
Prefix: %{l_prefix}
BuildRoot: %{l_buildroot}
BuildPreReq: OpenPKG, openpkg >= 20040130, bison
PreReq: OpenPKG, openpkg >= 20040130
AutoReq: no
AutoReqProv: no
%description
Jam is a software build tool that makes building simple things
simple and building complicated things manageable. Jam is a very
good solution for conventional C/C++ compile-and-link builds.
Because Jam understands C/C++ dependencies, there is no need to
declare header or object files. The built-in Jam rule "Main" handles
header file dependencies and object files both automatically and
on-the-fly.
%track
prog jam = {
version = %{version}
url = ftp://ftp.perforce.com/pub/jam/
regex = jam-(__VER__)\.tar
}
%prep
%setup -q
%{l_shtool} subst \
-e 's;^\(CC[ ]*=\).*$;\1 %{l_cc};' \
-e 's;^\(CFLAGS[ ]*=\).*$;\1 %{l_cflags -O};' \
Makefile
%build
%{l_make} %{l_mflags -O}
%install
rm -rf $RPM_BUILD_ROOT
BINDIR="$RPM_BUILD_ROOT%{l_prefix}/bin" ./jam0 install
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
rm -rf $RPM_BUILD_ROOT