| Port details |
- biblesync Multicast shared co-navigation library for Bible programs
- 2.1.0_1 misc
 =2      2.1.0_1Version of this port present on the latest quarterly branch. - There is no maintainer for this port.
- Any concerns regarding this port should be directed to the FreeBSD Ports mailing list via ports@FreeBSD.org
- Port Added: 2020-02-23 07:21:57
- Last Update: 2024-01-09 13:27:13
- Commit Hash: cb347ec
- People watching this port, also watch:: jdictionary, py311-Automat, py311-python-gdsii, py39-PyOpenGL, p5-Sane
- License: PD
- WWW:
- https://github.com/karlkleinpaste/biblesync
- Description:
- This is a C++ single class library encapsulating a protocol conduit. The
premise is that there is a local network over which to multicast Bible
navigation, and someone, possibly several someones, will transmit, and others
will receive. The choices for when you decide to xmit and what to do when you
recv are up to you as the application designer.
Access to the conduit is by creating the object, setting the mode, calling
Transmit() to xmit nav events, and arranging the frequent polling of Receive()
to recv nav events. There is more than just navigation to be handled; there
are live/dead events for potential Speakers as well as mismatches, presence
announcements, and errors. There is a programming reference biblesync.7 which
explains the details, both from a high level view of the essentials of the
protocol's behavior and at a low level of how you create, access, and use the
conduit class. The (single) BibleSync object should persist throughout the
life of your application, but at any time you can set the mode to "disable,"
and preferably stop the receive polling, and then re-enable it later as the
user needs.
Much work has been done in integrating this library into its first application,
Xiphos. It is useful to examine Xiphos' code to see where and how integration
has been done. Get a Xiphos source tree using:
git clone https://github.com/crosswire/xiphos
  ¦  ¦  ¦  ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - Dependency lines:
-
- biblesync>0:misc/biblesync
- To install the port:
- cd /usr/ports/misc/biblesync/ && make install clean
- To add the package, run one of these commands:
- pkg install misc/biblesync
- pkg install biblesync
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.- PKGNAME: biblesync
- Flavors: there is no flavor information for this port.
- distinfo:
- TIMESTAMP = 1590347775
SHA256 (karlkleinpaste-biblesync-2.1.0_GH0.tar.gz) = 9083fcacc4d85f2b8c3a3254112129c02d940d20db8c0c5bcb6239b115e8d0e8
SIZE (karlkleinpaste-biblesync-2.1.0_GH0.tar.gz) = 87868
Packages (timestamps in pop-ups are UTC):
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- cmake : devel/cmake-core
- ninja : devel/ninja
- gettext-runtime>=0.22_1 : devel/gettext-runtime
- Library dependencies:
-
- libuuid.so : misc/e2fsprogs-libuuid
- libintl.so : devel/gettext-runtime
- This port is required by:
- for Libraries
-
- misc/xiphos
Configuration Options:- No options to configure
- Options name:
- misc_biblesync
- USES:
- cmake compiler:c++11-lang gettext-runtime
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
Number of commits found: 9
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
2.1.0_1
09 Jan 2024 13:27:13
 |
Baptiste Daroussin (bapt) |
MAN[4-8]PREFIX: eleminate its usage and move man to share/man |
07 Sep 2022 21:58:51
|
Stefan Eßer (se) |
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner) |
2.1.0
07 Sep 2022 21:10:59
|
Stefan Eßer (se) |
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above  ) |
2.1.0
07 Apr 2021 08:09:01
|
Mathieu Arnold (mat) |
One more small cleanup, forgotten yesterday.
Reported by: lwhsu |
2.1.0
06 Apr 2021 14:31:07
|
Mathieu Arnold (mat) |
Remove # $FreeBSD$ from Makefiles. |
2.1.0
13 Aug 2020 09:07:25
 |
pkubaj |
misc/xiphos: fix build on GCC architectures
Use C11 compiler:
/usr/local/include/unicode/localpointer.h:224: error: expected ';' before
'noexcept'
Also required is bumping GCC for misc/biblesync because of libstdc++ ABI error.
MFH: 2020Q3 (fix build blanket) |
2.1.0
21 Jun 2020 15:36:35
|
salvadore |
Drop ports maintainership
Approved by: gerald (mentor) |
2.1.0
27 May 2020 21:09:28
|
salvadore |
misc/biblesync: Update to 2.1.0
Also add a patch to remove the need of USE_GCC=yes.
As a side effect USE_GCC is now unnecessary for misc/xiphos as well and
thus it is removed.
Approved by: gerald (mentor)
Differential Revision: https://reviews.freebsd.org/D24990 |
2.0.1
23 Feb 2020 07:21:50
|
tcberner |
New port: misc/biblesync: Multicast shared co-navigation library for Bible
programs
This is a C++ single class library encapsulating a protocol conduit. The
premise is that there is a local network over which to multicast Bible
navigation, and someone, possibly several someones, will transmit, and others
will receive. The choices for when you decide to xmit and what to do when you
recv are up to you as the application designer.
Access to the conduit is by creating the object, setting the mode, calling
Transmit() to xmit nav events, and arranging the frequent polling of Receive()
to recv nav events. There is more than just navigation to be handled; there
are live/dead events for potential Speakers as well as mismatches, presence
announcements, and errors. There is a programming reference biblesync.7 which
explains the details, both from a high level view of the essentials of the
protocol's behavior and at a low level of how you create, access, and use the (Only the first 15 lines of the commit message are shown above ) |
Number of commits found: 9
|
As an Amazon Associate I earn from qualifying purchases.