View | Details | Raw Unified | Return to bug 243916 | Differences between
and this patch

Collapse All | Expand All

(-)misc/biblesync/Makefile (+30 lines)
Line 0 Link Here
1
# $FreeBSD$
2
3
PORTNAME=	biblesync
4
DISTVERSION=	2.0.1
5
CATEGORIES=	misc
6
7
MAINTAINER=	salvadore@FreeBSD.org
8
COMMENT=	Multicast shared co-navigation library for Bible programs
9
10
LICENSE=	PD
11
LICENSE_FILE=	${WRKSRC}/COPYING
12
13
LIB_DEPENDS=	libuuid.so:misc/e2fsprogs-libuuid
14
15
USES=		cmake gettext-runtime
16
17
USE_GCC=	yes
18
19
USE_GITHUB=	yes
20
GH_ACCOUNT=	karlkleinpaste
21
22
USE_LDCONFIG=	yes
23
24
CMAKE_ON=	BUILD_SHARED_LIBS
25
26
post-install:
27
	${INSTALL_MAN} ${STAGEDIR}${PREFIX}/share/man/man7/biblesync.7 ${STAGEDIR}${MAN7PREFIX}/man/man7
28
	${RM} -R ${STAGEDIR}${PREFIX}/share/man
29
30
.include <bsd.port.mk>
(-)misc/biblesync/distinfo (+3 lines)
Line 0 Link Here
1
TIMESTAMP = 1580898650
2
SHA256 (karlkleinpaste-biblesync-2.0.1_GH0.tar.gz) = 953eed0b0ee7e4f8c6c34f7871babed26f03049e4dad5fc222fe3a65811a4d16
3
SIZE (karlkleinpaste-biblesync-2.0.1_GH0.tar.gz) = 89139
(-)misc/biblesync/pkg-descr (+24 lines)
Line 0 Link Here
1
This is a C++ single class library encapsulating a protocol conduit.  The
2
premise is that there is a local network over which to multicast Bible
3
navigation, and someone, possibly several someones, will transmit, and others
4
will receive.  The choices for when you decide to xmit and what to do when you
5
recv are up to you as the application designer.
6
7
Access to the conduit is by creating the object, setting the mode, calling
8
Transmit() to xmit nav events, and arranging the frequent polling of Receive()
9
to recv nav events.  There is more than just navigation to be handled; there
10
are live/dead events for potential Speakers as well as mismatches, presence
11
announcements, and errors.  There is a programming reference biblesync.7 which
12
explains the details, both from a high level view of the essentials of the
13
protocol's behavior and at a low level of how you create, access, and use the
14
conduit class.  The (single) BibleSync object should persist throughout the
15
life of your application, but at any time you can set the mode to "disable,"
16
and preferably stop the receive polling, and then re-enable it later as the
17
user needs.
18
19
Much work has been done in integrating this library into its first application,
20
Xiphos.  It is useful to examine Xiphos' code to see where and how integration
21
has been done.  Get a Xiphos source tree using:
22
git clone https://github.com/crosswire/xiphos
23
24
WWW: https://github.com/karlkleinpaste/biblesync
(-)misc/biblesync/pkg-plist (+6 lines)
Line 0 Link Here
1
include/biblesync/biblesync-version.hh
2
include/biblesync/biblesync.hh
3
lib/libbiblesync.so
4
lib/libbiblesync.so.2.0.1
5
libdata/pkgconfig/biblesync.pc
6
man/man7/biblesync.7.gz

Return to bug 243916