TrueOS: I cant install Study Bible program


I was a recent windows 10 pro and Linux user, but very newly switch to TrueOS BSD, and really loving this OS, but I am a minister of God, and depend on my Study bible programs e.g esword, the word and BibleTime. But I cant seem to find any of these programs in the appcafe. And I when I check things out online BibleTime is a supported application for BSD OS. So can someone assist me in solving this problem.

#2 would be a place to start

wine/PlayOnBSD would be the 2nd place to start

worst case scenario. get a copy of windows, and install in VirtualBox


I just went to and I did see where FreeBSD is supported. I searched AppCafe in TrueOS and there is no “bibletime.” However I searched for it on a FreeBSD system, and the package does exist there. It’s probably something that hasn’t been ported over yet by the devs. I’m wondering if you can build it from TrueOS Ports.

Just looked and there is a program called Sword in appcafe that links to this website… I’m sure it will be very similar to esword.


bibletime is comlining right now, out of ports.

failed the build process - program not going to work

/usr/local/include/sword/swconfig.h:125:2: note: ‘Sections’ has been explicitly marked deprecated here
SWDEPRECATED SectionMap Sections;
/usr/local/include/sword/defs.h:143:40: note: expanded from macro ‘SWDEPRECATED’

define SWDEPRECATED attribute((deprecated))


8 warnings and 1 error generated.
ninja: build stopped: subcommand failed.
*** Error code 1



Thanks for your help, I will look into all of these suggestions


Okay if anyone would like the Bibletime software here are the steps I followed. They are a bit messy for modern Desktop users so there is some command line work to perform. It’s not too bad and I didn’t have to mess with the code at all.

  1. goto
  2. click on the download link for bibletime-2.11.1.tar.xz
  3. Once downloaded to a working directory of your choice extract the file ( I used Lumina Archiver)
  4. Open a terminal to the working directory where you extracted the bibletime-2.11.1.tar.xz you should be in a directory called bibletime-2.11.1
  5. Locate and execute this line sudo ./
  6. the program will compile and if successful you should see the following lines
    BibleTime has been installed to /usr/local.
    You can run it by typing /usr/local/bin/bibletime.
  7. Just do what the screen says and run /usr/local/bin/bibletime.

At this point you should have the BibleTime program compiled and installed. I did install sword as mentioned above however I didn’t have much fortune in getting that to run. I also noticed that on that bibletime doesn’t have a maintainer for it’s port. I really need to learn how to make ports and packages so maybe I will take the time to do this since this build of bibletime compiled and I was able to run it and add works to it without issue. Also I do use this application. Anyway I hope this helps.


Hi, I’m willing to support you on this but I don’t have the time to do the work myself. I’ve created three new chapters for the porters handbook that you could try to start with. I’ve posted the html on my ‘website’, though it’s pretty rough:

Once you hit Chapter 6 (the original chapter 3), you’re back into the real handbook and should probably just read it from the FreeBSD website.

Ping me if you want to get my email address for direct questions. (I don’t know if you can do private messages on this forum or not).


Yeah I have been looking at the FreeBSD porters hand book It seems a bit complex. I would appreciate any help you can offer. First I need to read through the hand book.


Sometimes it’s easier to start with an example:

Cowsay is about as simple as it gets. The cowsay port uses a custom install step that you may not need if the bibletime makefile has an install target. You’ll probably have to chew up the file and stick parts of it in your ports makefile.


This is exactly what I needed thank you. Also looking through the BibleTime code they are using CMake is there any thing special I need to know? The shell script sets a couple of cmake variables to tell it to build a release build or a debug build and the install path then it does a make clean and a make -j4 install and does that from the build directory. I have to assume that the cmake places the artifacts in the build directory. Anyway again appreciate your help.


Actually looking at the bibletime port in head there is a maintainer the name there is “tabthorpe”. So maybe I will just wait and see if/when tabthorpe upgrades the port to the new build.
With that said I still would like to figure out the port system. I still don’t understand where the ported source code is kept. None of the files in the port directory has a URL that I can discern. Now there is the MASTER_SITES= SF/${PORTNAME}/BibleTime%202/BibleTime%202%20source%20code in the make file but I’m not sure what SF is. Anyway I know I need to read more of the hand book. So now maybe I will pick a different port that doesn’t have a maintainer. I didn’t think about checking head and was just going off of what said for the maintainer information.


I would suggest pinging the maintainer and see if a) he is still actively maintaining and b) if he wants some help. Sometimes people are maintaining these ports because they feel obliged, not because they want to. I took on port maintainer-ship of the Lua 5.3 port after pinging the previous maintainer. He was thrilled to be relieved of the burden. Sometimes the best way to learn to ‘swim’ is to just jump in and start flailing around! :crazy_face:

See - Using MASTER_SITE_* Variables. Also an example here:


You are being too kind. I do appreciate your help and I hope I am not too much of a distraction. I agree I should contact the current maintainer and thank you for pointing out that section from the handbook. So I see that the SF is the sourceforge website. Anyway I hope you have a good one. I may start a different thread for future questions.

At this point I hope I was helpful to deacondivine. Not sure but at least we can enjoy the BibleTime software under TrueOS for now just by downloading the source and running the shell script to make and make install it.

closed #14