Rock Storm <rockst...@gmx.com> wrote:
> On Fri, 2016-11-04 at 17:23 -0700, Walter Landry wrote:
>> I replaced the build system with waf. I have a waf package already.
>> Waf is a bit controversial in Debian, so I need to make an ITP and see
>> what the Debian consensus is.
>
> I completely ignore waf and how it works, but I'll take a look at it,
> it seems promising.
FYI, I filed my waf ITP.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843325
For reasons I do not understand, it has yet to show up on
debian-devel.
> Even though it is a pain and feels outdated I was sticking to
> upstream's build system, I'd rather modify the source as little as
> possible.
In case it helps, I am attaching a Makefile that builds using the
upstream build system. It is for a specialized setup we have here,
but should work with minor tweaks. It does not build shared
libraries.
> As soon as the licensing issue is cleared up I'll upload my progress in
> case you'd like to review it and/or collaborate.
Are you in contact with upstream?
Cheers,
Walter Landry
INSTALL = install
INSTALL_PROGRAM = $(INSTALL) -m 755 -p
INSTALL_DATA = $(INSTALL) -m 644 -p
INSTALL_DIR = $(INSTALL) -m 755 -d
prefix=$(shell cd ../..; pwd)
exec_prefix=$(prefix)
bindir=$(exec_prefix)/bin
libdir=$(exec_prefix)/lib
includedir=$(prefix)/include/cspice
datadir=$(prefix)/data
all: installdirs
if [ ! -d cspice/ ] ; then \
tar -xf dist/cspice.tar.Z ; \
else true ; \
fi
cd cspice; ./makeall.csh
$(INSTALL_PROGRAM) cspice/exe/* $(bindir)
rm -rf $(datadir)/*
$(INSTALL_DATA) cspice/data/* $(datadir)
rm -rf $(includedir)/*
$(INSTALL_DATA) cspice/include/* $(includedir)
$(INSTALL_DATA) cspice/lib/* $(libdir)
# symlink cspice.a to libcspice.a, the usual name for a library
ln -f -s cspice.a $(libdir)/libcspice.a
installdirs :
$(INSTALL_DIR) $(bindir) $(libdir) $(includedir) $(datadir)
install:
true
clean:
rm -rf cspice/
