On Sat, Nov 22, 2014 at 06:49:39AM +0200, Miika Turkia wrote:
> Some instructions how building libdivecomputer differs from Subsurface
> build. And mention to copy libigt2 over to other repository if needed.
I have started to play with this and would like go a slightly different
path (but I'd like your feedback).
I would like to "cheat" when creating our packages. I'd like to AT LEAST
include our private libdivecomputer and link statically against that.
(I'd like our private marble as well, but that's a lot more work and most
likely not worth it).
So I was thinking of having a completely clean git directory layout like
this:
src/subsurface
src/subsurface/libdivecomputer
Both of these directories are whatever git version I want (let's say tip
of master and tip of my private branch).
Then cp that src/subsurface directory into src/subsurface-$VERSION
then start building libdivecomputer first
then build subsurface and make sure you link it against libdivecomputer.a
Does that make sense?
/D
PS: here's the start of my script:
#!/bin/bash
# start from the directory above the combined subsurface &
# subsurface/libdivecomputer directory
VERSION=$(cd subsurface ; git describe | sed -e 's/-g.*$// ; s/^v//')
echo "building Subsurface" $VERSION
if [[ -d subsurface-$VERSION ]]; then
rm -rf subsurface-$VERSION.bak.prev
mv subsurface-$VERSION.bak subsurface-$VERSION.bak.prev
mv subsurface-$VERSION subsurface-$VERSION.bak
fi
mkdir subsurface-$VERSION
(cd subsurface ; tar cf - . ) | (cd subsurface-$VERSION tar xf - )
cd subsurface-$VERSION/libdivecomputer
# now make libdivecomputer
cd ..
# now create the Subsurface package with the libdivecomputer.a that we
# just built
_______________________________________________
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
