Codeblocks For Mac Os Catalina

Posted on by

Apple appears to have done a Microsoft. The new macOS Catalina is causing problems for a lot of users. Battery drain appears to be at the forefront of these problems but there’s also the fact that Catalina doesn’t support 32-bit apps and there’s still a lot of them out there.

These are instructions on how to build Code::Blocks under Apple Mac OS X.They have been tested under Mac OS X version 10.4 (PowerPC and Intel),and should work similarly on the newer Mac OS X 10.5 and 10.6 as well.

We will be building everything from scratch using the source code, andnot use any available package managers likeMacPorts,Fink,Gentoo orRPM.Packaging can be done later, once it has reached a more stable release.

Update: building for MacPorts can be found at the end of the document.

  • 2Check Autotools versions
  • 7Build wxWidgets
  • 8Bundle library for Mac
  • 10Build CodeBlocks from SVN
  • 11Bundle application for Mac
    • 11.1Way One: Mac OS (resource)
    • 11.2Way Two: NeXT (bundle)
  • 13Install with MacPorts

Install Developer Tools

If they didn't come bundled with Mac OS X, get the Xcode Tools (or Developer Tools for older Mac OS X) from http://developer.apple.com/tools/ or from your install disk.

This will install Apple versions of:

  • http://www.gnu.org/software/gcc/ (GNU Compilers)
  • http://www.gnu.org/software/gdb/ (GNU Debugger)
  • http://www.gnu.org/software/make/ (GNU Make)

Apple regularly pulls all older links in order to promote newer Mac OS X, but all theold developer tools can be downloaded from ADC at http://connect.apple.com/

You need a (free) developer registration with Apple first, in order to log in there.For Mac OS X 10.4, you want (at least) Xcode 2.2, since earlier versions were buggy.

Check Autotools versions

Depending on your OS version, you might need to download and compile new versions of these:

  • http://www.gnu.org/software/autoconf/ (GNU Autoconf)
  • http://www.gnu.org/software/automake/ (GNU Automake)
  • http://www.gnu.org/software/libtool/ (GNU Libtool)

Check what you have, with --version (note that GNU libtool is called 'glibtool' on Mac OS X)

Currently Code::Blocks requires versions:

  • autoconf 2.50+
  • automake 1.7+ (1.9+ needed in order to build the dist tarball)
  • libtool 1.4+ (1.5.8+ highly recommended to get some bug fixes)

Automake example

For Mac OS X 10.4, you will only need an upgraded (local) installation of automake 1.9.x.

You can download 'automake-1.9.6.tar.gz' and configure and install it with something like:

Since it's now known as 'automake-1.9', it won't interfere with the regular 'automake'

If you would rather have the new version to be called when calling 'automake', let it install into /usr/local and put /usr/local/bin before /usr/bin in your PATH.

Libtool example

Download libtool source. The following instructions will overwrite your current version of libtool with the one you just downloaded.

Note that this will replace the system version of glibtool, which might have some compatibility issues with building other software.

FYI: Universal Binaries

If you are building for Mac OS X 10.4 or later, you might want to build 'Universal Binaries 'These are binaries that contain code for both PowerPC ('ppc' arch) and Intel ('i386' arch)

The basic flags that needs to be added are:

(You only need the sysroot parameter on PowerPC Macintosh, not on a Intel Macintosh)The '-arch i386 -arch ppc' is what tells the compiler to build a 'universal' (or 'fat') binary.

Usually it's easiest to build one version for 'powerpc-apple-darwin8',and one version for 'i686-apple-darwin8', and then merge them with 'lipo'

For

Some caveats:

  • pre-compiled headers might fail with a 'no main' error. If they do, add a -c to only compile them
  • when cross-compiling, tools like auto_revision might fail to build. copy these from a native build
  • the Tiger compilers might crash from time to time, but that is only to be expected (it seems)...

See Technical Note TN2137: Building Universal Binaries from 'configure'-based Open Source Projects

FYI: Compilers

When building for older versions of the SDK, you want to make sure to use the same compiler.

Mac OS X 10.6 has GCC 4.2 as the default compiler, which won't work for the Mac OS X 10.4 SDK.

FYI: ANSI or UNICODE

For the moment we are using 'ANSI' (--disable-unicode, default) for Mac OS X 10.3 and earlier,and 'UNICODE' (--enable-unicode, optional) for Mac OS X 10.4 and later.

See http://www.wxwidgets.org/manuals/stable/wx_unicode.html#unicodeandansi

FYI: 32-bit or 64-bit

Code::Blocks currently uses wxMac (wxOSX/Carbon), which is 32-bit only. So it's not possible to build for 'x86_64'.

When Code::Blocks (and requirements) has been updated to use wxOSX/Cocoa, then a 64-bit version might be built too.

Build wxWidgets

Download the source code

Download the tarball for the wxMac release:

Apply necessary patches

Don't forget to apply any released patches!

Configure and (GNU) Make

note: the easiest way to build a Universal Binary with wxWidgets isthe new flag: --enable-universal_binary (you need wxWidgets 2.6.4+)

Install into Destination

Bundle library for Mac

To avoid having the Code::Blocks user having to compile or install wxWidgets themselves,we can bundle it with our application so that it is contained in the application bundle.This could also be done by statically linking wxWidgets, but with dynamic linking we canshare the wxWidgets library between all applications using wxWidgets (not just Code::Blocks)


Way One: Library (dynamic)

To bundle our shared library with the application, we include it in 'MacOS' and change the path:

@executable_path will be replaced with e.g. /Developer/Applications/CodeBlocks.app/Contents/MacOS

Way Two: Framework (bundle)

To bundle our framework with the application, we include it in 'Frameworks' and change the path:

This way it will first look in the framework path (-F), and then in for the shared library path (-L) as usual.

Install Subversion client

On Mac OS X 10.4, you need to install the Subversion (svn) program:

Note: you need SVN for the Code::Blocks revision scripts to work!

Build CodeBlocks from SVN

Download the source code

Apply necessary patches

For a list of all available patches, see:

You might need to convert line endings from DOS to Unix first.

Bootstrap with Autotools

You need to use the newer version of automake (see above), for the 'bootstrap'. (OS X 10.5 users may have recent enough autotools so they may not need to install them)

Mono Fix

If you have the Mono.framework installed, then it probably set up a symlink like:

Unless you have a 'proper' pkg-config installation the Code::Blocks configure will fail, so move this symbolic link aside.

Configure

Note: the easiest way to build a Universal Binary for Code::Blocks is to build once for PowerPC (-arch ppc) and once for Intel (-arch i386), and then merge them (with lipo) afterwards.

Note: You need to patch the location of the pre-compiled headers, or it will generate them in the same place for both arch.

Tiger Fix

There is a bug in the glibtool of Mac OS X 10.4, that fails to link C++ libs:

To work around this, you need to edit the generated 'libtool' script manually:

This bug has been fixed in GNU libtool 1.5.8 and later.

(GNU) Make

'nice' isn't strictly needed, it just makes the compile run at a lower process priority

For the Universal Binary build:

Install into Destination

'sudo' asks you for an admin password, in order to get install permissions

For the Universal Binary build:

Where 'lipomerge' is a custom shell script:

Bundle application for Mac

After building codeblocks in the regular Unix way, you need to bundle it with the iconsand various other info that it needs to make a regular stand-alone Macintosh application.

There are two ways of accomplishing this, old Mac OS-style resource or NeXT-style bundle.The old resources are handy while developing, while bundles are more suitable for release.

Note: You need to use either of these methods, or your application will launchin the background behind all other windows and will be unable to receive any events!

Way One: Mac OS (resource)

Handy while developing, as you don't need to create a whole bundle.

First we install the program to the PREFIX directory of your choice:

Note: on the Intel Macintoshes, the icon comes up as 'broken'(apparently it assumes that all apps with resforks are Classic)

Start the application with a small prefix shell wrapper like this:

You don't need the 'DYLD_LIBRARY_PATH' stuff,if you are installing to a system directory.

Code Blocks For Mac Os Catalina Installer

Common PREFIX Settings

Local: PREFIX=/usr/local

System: PREFIX=/usr

MacPorts: PREFIX=/opt/local

Fink: PREFIX=/sw

Way Two: NeXT (bundle)

This does not involve resources, and is more relocatable.

Files needed:

  • codeblocks.plist (generated, rename to 'Info.plist')
  • codeblocks.sh (shell wrapper, rename to 'CodeBlocks')
  • app.icns (icons are available in src/src/resources/icons)

The MacOS program will just be a shell wrapper that calls 'bin/codeblocks', like above.Traditionally the bundle would include Frameworks and Resources, but we'll just avoid thosehere and use the regular 'lib' and 'share/codeblocks' instead (just as with a regular install). These temporary directories are listed in italic below, they're not really used in bundles...

Setup a hierarchy like this, and copy the files from the regular build/install and the above file list to it:

The CodeBlocks application can now be moved with the Finder, and started up like a regular Mac application. (the nightly build includes a more advanced Info.plist and more icons - for also mapping all the files that the application can open, like source code and header files and such)

Proper Application Bundling

To avoid the shell wrapper, the binary can now be moved from 'bin/codeblocks' to 'MacOS/CodeBlocks'. Helper files are moved from 'share/codeblocks' to 'Resources'. The dynamic libraries are moved from 'lib' to 'MacOS':

To avoid having to use a DYLD_LIBRARY_PATH, we rename the shared libraries (with the install_name_tool program) from e.g. /usr/local/lib/ to @executable_path/:

The libraries can have their names changed using the -id parameter:

You also need to change all of the loadable bundles for the plugins:

You can check the result, what libraries/frameworks it links to, with:

Optionally you can then repeat the process, for the wx library too...

Here is a full script to do the job... It assumes to be executed at the same directory level as the CodeBlockSVN.app directory that will receive all the stuff... maybe enhanced but it is a first try that do work when packaging an OS X SVN build.

FYI: Darwin vs. Mac OS X

'Darwin is the UNIX technology-based foundation of Mac OS X.'

'Pure Darwin' here refers to the Open Source version of the OS:

  • http://puredarwin.org/ or http://gnu-darwin.sourceforge.net/

(that is: Darwin using X11 instead of Aqua for the user interface)

Install with MacPorts

Install wxWidgets

You will need the wxWidgets library, install as port with:

If you want the X11/GTK version on Mac OS X, instead use:

Install Code::Blocks

After that is installed, you can install Code::Blocks with:

If you want the X11/GTK version on Mac OS X, instead use:

This will download the SVN trunk, and any dependencies:

Note: to upgrade from SVN, you need to uninstall first:

This is both because all SVN versions are numbered '0',but also due to a bug in the Code::Blocks build scripts.

Running +aqua (wxMac) version

After the build completes, you can start the program by:

Note that the wxMac application bundle in 'MacPorts'is just a wrapper, with symbolic links to /opt/local...

Running +x11 (wxGTK) version

The non-bundled wxGTK version is instead started with:

When running X11/wxGTK programs in Mac OS X, you can use'open-x11' to first start up X11.app and set up $DISPLAY:

Retrieved from 'http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Mac_OS_X&oldid=6415'

September 18

All Wordsearch users now have access to Logos Bible Software free of charge. To access your Wordsearch Library using Logos, follow these steps:
  1. Set up your account at Faithlife using the same email address associated with your Wordsearch account.

Your books should already be available in your library when you begin using Logos. However, some titles will take longer to make available. Some titles may not be available until the end of the year. Your existing notes, highlights, and other user generated content will be available in Logos by early 2021.

August 7 - -

Thank you to everyone who has tried the beta and provided us with feedback. We are continuing to investigate various issues.

We have determined a workaround that helps with the error: OLE 80004001

  1. Click on Options from the upper-left menu
  2. Click on Settings Helper
  3. On step 6 of 6, set it to 'Use the normal font specified by each book'

July 28 - -

Code Blocks For Mac Os Catalina 10.15

Since we launched the beta on Friday afternoon, we have been getting tremendous feedback from our customers. Thank you for your continued support and help during this time. We wanted to provide you with an update on what we’re hearing and seeing now that it’s been out for a few days.

NOTE: If this is your first time hearing a beta program is available, please scroll down to the July 24th update to see the instructions and some other key notes about the current version that is available to test.

We’re noticing that roughly half of the customers who are installing the beta program are able to install everything fine and get books to properly open. In the other cases, we’re noticing that the program will install, but when attempting to open a book, it can trigger an “OLE error 80004001” as seen below, which will cause the program or the book to close and ask to restart the program.

Through your help in testing the beta, we’ve also found a few more flaws in the program to take note of:

  • Toggling the “auto-arrange” feature from the “Window” dropdown menu will show the book but will then pop up the “OLE error 80004001” message and close the book or program
  • In certain instances with customers who have exceptionally large libraries, we are seeing the program can be susceptible to crashing during step two of the indexing process
  • We are noticing that sometimes uninstalling and reinstalling the beta can improve some of the issues surrounding loading books as mentioned above

Just to be clear, we do not plan on taking down the beta at this phase. Instead we plan on continuing to evolve the program with your help. From this point forward, we will continue to have our internal development team work on attacking some of the bug fixes that we’re capable of handling in-house, but on some of the larger issues, we will be sending some log files back to our third-party development company to get another enhanced build based on the findings that have been uncovered up to this point. At this time, there is not an ETA on when the next beta test build will be ready from them, but we will keep this page updated with all the news related to this topic as it becomes available.

As a reminder, Wordsearch will continue to allow customers to utilize the AppStream environment indefinitely. There are no plans to phase out the AppStream at this time so that you can continue to receive the full functionality capabilities of Wordsearch if needed or if this is your preferred way of accessing your Wordsearch program and resources. Thank you again for your patience.

July 24 - -

Please note: This is an announcement directed specifically to Mac Catalina users. If you are on Mojave or Sierra, it is not recommended that you upgrade to Catalina at this time.

A beta version of Wordsearch 12 on Mac Catalina is now available. We would like to invite you to test this offline beta version. In our internal testing, we have already experienced some varying results, and would appreciate your help.

While this isn’t the ideal solution, we wanted to get an offline version in your hands as soon as possible. We know how important Wordsearch is for your ministry and are sincerely sorry for the trouble, frustration, and disappointment this has caused.

One of the key things we are noticing in our testing is that after the initial installation is completed, on some computers, it is taking 2-3 minutes for the Wordsearch 12 program to actually appear on the screen. On others, it loads much quicker. We wanted to make you aware of this so that on its first launch, you may need to be patient with it as it attempts to properly load. This is something we’re definitely aiming to improve as we go along. If your download does not open after several minutes, please let us know by emailing wordsearchsupport@lifeway.com.

PLEASE NOTE: This initial build release of this beta Wordsearch 12 for Catalina is missing some functionality that is typically in the full Wordsearch 12 program. We felt it was important to release this first version as soon as it was available, but we do plan on continuing to add back the currently missing functionality as soon as possible.

As of today, here are the main things that are missing from the program:

  1. Word Processor
  2. Lexicon Explorer
  3. Highlighting
  4. Scripture pop-ups
  5. Right-click functionality

Download Instructions:

Please review the following instructions to download and install the Catalina beta Wordsearch 12:

  1. Please note: it may take several minutes for the program to open after it is installed
  2. After your program is downloaded, login, then click on Help from the upper left menu and click on Unlock Purchased Books.
  3. Click here for Installation FAQs. If you need assistance with the installation, please email us at wordsearchsupport@lifeway.com.

What happens with AppStream now?

Wordsearch plans on allowing customers to continue to utilize the AppStream environment indefinitely. There are no plans to phase out the AppStream at this time so that you can continue to utilize the full functionality capabilities of Wordsearch if needed.

July 21 - -
Final development work is looking to be completed by end of day Wednesday, with the release looking to take place on Thursday or Friday.

July 17 - -
Significant progress has been made. We are on track to release an offline version of Wordsearch 12 for Catalina sometime next week. More details will be posted soon.

June 30 - -
A major stride in development was made over the past few days to where of the two major remaining bugs that existed, one was fully resolved and the other is about 90% resolved. The problem that is still being worked on is the way books appear in the library and to have everything scale correctly. This has been taken care of with every book category except for the “Bibles” category. We’re very hopeful that this will be a quick fix and that the launch can finally be prepared here in the very near future. In full disclosure, if it was another lesser used category, we would have made the decision to launch the program as is, but with it being so key, we’re going to try to quickly resolve this issue and then get the links ready for all customers to be able to download it as absolutely soon as possible.

Overall, within the development team at Wordsearch, there is legitimate excitement and anxiousness as the ability to get the fix out for offline use is extremely close. We just need to clear one final hurdle. As soon as this fix is in, we will let everyone know about the exact release date. We will put this release date in all of our emails, on our social media, on our blog, on this site, etc. We promise to do everything we can to communicate it well and to make the process of getting access to your Wordsearch download link as easy as possible. More to come hopefully very soon.

June 26 - -
We are currently in the middle of another round of testing. We are continuing to work towards providing an offline fix for Catalina users as soon as possible.

We are aware that Apple made an announcement this week about their next Operating System, called Big Sur, to be released sometime this Fall. Our Development Team has already been reviewing the details of Big Sur to make sure the solution being developed for Catalina will quickly be available for Big Sur users.

June 12 - -
Development continues.

June 1 - -
We continue to work towards resolving bug issues. At this time we are not yet ready to release an ETA for a possible launch date for the offline version. If you're not already aware, please scroll down to our post from April 6th to view instructions on how to access our our online AppStream option.

May 21 - -
Troubleshooting continues.

May 14 - -
Some positive news. Several weeks ago we had a list of seven key problems that needed to be addressed to finalize the fix for the offline version and we’re now down to just two bugs. Our Development Team has a lot of optimism that those two bugs have been correctly identified and a solid resolution plan is now in place.

May 8 - -
Troubleshooting continues.

May 1 - -
In our meetings with our third-party developer this week, great progress was made regarding troubleshooting issues. Another update will be posted next week.

April 23 - -
Troubleshooting bug issues continues. Another update will be posted next week.

April 15 - -
Now that the temporary AppStream is up and running we are back to focusing on completing the development for our permanent fix: an offline Catalina-compatible Wordsearch 12. We are currently in a new round of testing with our third-party developer as we continue to sort out various bug issues. At this time we do not have a potential ETA on when this option will be available. Another update will be posted next week.

April 6 - -

Follow these Instructions to Access the Wordsearch 12 AppStream

Important Note: We kindly ask that if you are a PC user that you do not submit a request for this AppStream access. There is no additional functionality in this that you wouldn’t already have using your Wordsearch 12 program. Due to the significant costs that we are taking on in order to run the servers to operate this AppStream while we work on our permanent fix for Mac users, we are asking that only users who have lost access to their Wordsearch program due to being on Catalina OS request this access.

If you are a Mac Catalina user, please email us at wsdirector@lifeway.com telling us you need access. Please include the email address associated with your Wordsearch Bible account. Due to the high volume of requests we are expecting, we ask that you email your request rather than calling in. We should be able to handle your request within 24 hours of receiving it.

Once your request has been received, we will grant you access to AppStream in your account through our customer database. At that time, you will receive a confirmation email with instructions to access the AppStream.

Click here to find a list of FAQs.April 3 - -

As you are aware, the Wordsearch desktop application has not been available on the Mac Catalina OS. We have been working tirelessly to provide a solution, but we know that this situation has caused tremendous inconvenience and frustration. We wanted to apologize once again for the trouble this has caused.

To keep you updated where we are in the process, we wanted to let you know that we have some good news. We have come up with a web-based solution that will launch early next week.

To start with, this is not our permanent solution for Catalina, but we wanted you to have access to your program and library as soon as possible.

The Wordsearch 12 AppStream gives you access to the full Wordsearch 12 program as well as your library. As long as you have the Internet, you can connect to the Wordsearch desktop experience. (Please note this is the full program and different from our app.wordsearchbible.com site.)

Code Blocks For Mac Os Catalina Patcher

Other Notes:

- This is only for Mac users.

- If on Mojave OS or prior, you can upgrade to Catalina once this is available, but please note that there is no offline capabilities within the AppStream. If you prefer to stay on Mojave OS or prior to maintain your offline access, we understand and will continue to work towards providing the offline solution soon.

- With that said, there are no offline capabilities with the Wordsearch 12 Appstream. As a reminder, this is not our final solution for Mac users.

- The Chrome browser and Firefox browser are recommended for best use. Safari will work, but you will have a better experience with Chrome or Firefox.

- We will send an email again to everyone with the exact instructions on how to connect. This is completely free for current Wordsearch users, even if you currently have an older version of Wordsearch.

April 1 - -
Testing continues.

March 30 - -
Internal testing continues. Another update will be posted in the next 24-48 hours.

March 28 - -
Apologies for the update delay. However, we have good news as a lot of progress has been made with our internal testing for the web-based Wordsearch 12 access point. It's very possible we're in the last round of internal testing. The past few days our Development Team has been busy uploading our 5,000+ book catalog to the online system. This will help make the start-up process quicker for our customers. Another update will be posted Monday.

March 25 - -
Internal testing is still underway for the web-based Wordsearch 12 access point. Another update will be posted in the next 24-48 hours.

March 23 - -
Internal testing is underway for the web-based Wordsearch 12 access point. Another update will be posted in the next 24-48 hours.

March 20 - -
We are still working on the browser-based solution. We'll be working on this throughout the weekend. Update to come Monday.

March 18 - -
The browser-based Wordsearch 12 access point solution is almost ready for internal testing.

Another update will be posted within the next 48 hours.

March 16 - -
Good progress has been made on the browser-based Wordsearch 12 access point solution. Internal testing should start soon.

We'd like to reemphasize that this is a TEMPORARY solution. Once the browser-based option is launched, we will continue working to provide an offline Catalina-compatible version asap.

Another update will be posted within the next 48 hours.

March 13 - -
We are still working on the browser-based solution. Update to come Monday.

March 12 - -
Unfortunately we have encountered another snag. The latest Catalina-based build resolved previous bugs but caused new ones. We are now working on making the browser-based option available for customers ASAP. Once the browser-based option is launched we will continue working towards an offline Catalina-based solution. An update will be provided within the next 24 hours.

March 10 - -
We are currently running a brand new WS12 build for Catalina through internal rounds of testing. This new build attempts to resolve the latest bugs we encountered​. At the same time we’re also just a couple of steps away from having the browser-based cloud option ready for public access. Hypothetically if this latest WS12 build for Catalina passes testing with flying colors, the browser-based option may be unnecessary. Another status update will be provided within the next 48 hours.

March 6 - -
We have some positive news to share with you all in regards to getting access to your program and books again if you're on a Mac OS Catalina device. Through some testing that took place today, we were able to run the WS12 program in a cloud-based streaming environment that we have built out through the Amazon Web Services cloud. Essentially, this will allow you to connect to the server we have structured and you will be able to have access to the full WS12 program. From there, you will just sign in to your account using your email and password and get access to all the books you've owned. To be very clear, this is NOT our long-term and permanent fix. We are still pursuing daily the ability to use the WS12 program in an offline state where the files are all stored on your hard drive. We've had some positive news on that front this week too for that fix, but it's still difficult to predict its final release date. However, for this temporary fix to allow you all to connect to the cloud to get access to your program/books, we're going to make it very easy for you to just be able to click a button from your My Account area which will connect you to the program. While it would be a bit foolish to put a firm guarantee on this, all signs point to us being able to release this access to you all around the middle of next week. We will be sending out an email to our entire customer base once this solution is live and at that time, provide you with the simple instructions on how to gain the appropriate access. Thank you again for your patience and we look forward to releasing this temporary fix very soon and also staying extremely dedicated to fixing the offline solution as well.

March 3 - -
Wordsearch is committed to getting our Mac users a working version of the desktop program as absolutely soon as possible. Within this effort, we are now closing in on a fix that would allow our users to get access to the Wordsearch desktop program by running the program 'in the cloud' through some servers we are setting up. This will give you the ability from your Mac to easily connect to the server with an internet connection and then you will have access to your program and books. The overall fix for full offline use continues on as well of course, but as a temporary solution, we are nearing the release of this technology. More to come on a release date later this week.

February 26 - -
Wordsearch Bible is continuing to pursue any and all avenues to try to resolve the issue to allow our program to run properly on the Mac Catalina OS. Within the past few days, we have been able to get our program running on Catalina, but when attempting to do any major actions in the program, a bug prevents it from then operating properly. This is a bug we are actively working on resolving as quickly as possible. We are very hopeful that once this bug is resolved, that the end of our development process is very near and possibly even complete. In the meantime, we are also pursuing other opportunities for Mac users to be able to connect to a remote environment which will allow users to run the full feature WS12 version. While this would be more of a temporary solution, it would still allow our users full access to their programs and libraries in the meantime until our other coding has been completed. Testing of this remote environment are ongoing as of Wednesday afternoon, February 26, and we hope to have more news on its potential availability to our customers here very shortly.

February 24 - -

We were able to get a running program of WS12 on a Catalina OS environment late last week but then upon running some updates, ran into a bug. We are currently exploring all options of how to get a running program out to our customers as quickly as possible that will allow WS to operate on the Catalina OS. At this point, we are even considering if it's feasible to release a version of the program that doesn't have every single ability that WS12 does just to get something out to our customer base to begin working with, then provide the updates as they come available. Of course the main goal is to get the full functionality program out ASAP, and that's still the intention, but are also willing to explore other avenues if it means getting something out to our customer base in the meantime faster.

February 17 - -

A big breakthrough happened today with the development work and there is a chance that we have a testable download installer ready here maybe even tomorrow. It's a bit too early to tell if this was the major puzzle piece that needed to be solved, but if this turns out to be true, then we will quickly do some internal testing on it to determine if it's ready for the full release. More news to hopefully come on this tomorrow. Stay tuned.

February 12 - -

We have been able to move past last week's error in the code that was causing a delay. Our lead programmer is back to making the necessary code changes to try to push the Catalina fix towards its release. We're hoping to be able to provide a more accurate release date by the end of this week. In the meantime, we ask that you use our web app to read your resources on a Mac Catalina OS.

Codeblocks for macos catalina

February 7 - -

This has been a very frustrating week for our development team as we got very close to prepping its release as we had a running version of Wordsearch running on Catalina OS. However, in recent days, we determined there was an error in the code that was delivered to us by our third-party vendor that now has to be resolved before moving forward. We're currently awaiting that fix.

February 3 - -

Code Blocks For Mac Os Catalina Dmg

With work continuing throughout the weekend on this project, there were advancements made and our development team even got a version of Wordsearch 12 running on a Mac with the Catalina OS. At that point, during some testing on trying to run some updates, it triggered an error that the team is now working through. But, this was still significant progress made in getting a version of our software to run on Catalina. Once this issue is resolved, which should be fairly quick, we're hoping that the release will be very near from that point.

January 30 - -

The process has slowed down slightly in the past 48 hours with a couple of minor errors that have popped up. We're still hoping to able to do an internal test on a Catalina running Wordsearch program by the end of this week.

January 28 - -

Our internal development team worked throughout the weekend to process the test build that we received. The typical process here is that we must receive the files then do a large amount of converting of those files to get them to work within our internal processes. The conversion portion of the process can often times be the lengthiest part of the project. Through their diligent work, this was completed successfully on Monday. On Tuesday, some final checks will be run and then if all goes smoothly, we are hoping to send a build to our employees on Wednesday afternoon or first thing Thursday morning to be able to test the Wordsearch 12 program on Mac computers. If the testing of this phase goes well, then we will move to the final phase of the process, which is actually building the installer links to allow our customers to be able to access the download from their accounts.

Thanks again for your patience and we look forward to hopefully releasing this update in the very near future.

Codeblocks For Macos Catalina

January 24 - -

In order to complete the necessary fixes for Wordsearch Bible to run on Mac OS Catalina, we have been working with a third-party company for over a year now to work towards a solution. As soon as Apple announced the intentions to move towards 64-bit requirements, Wordsearch began planning on how to resolve the issue. This third-party company specializes in converting Windows-based programs and retrofitting it to work in a Mac environment. Because of this, we have been waiting since the launch of OS Catalina on a build to arrive that we could implement and release.

Just as of this week, we have finally received a test build from our third-party company and have now been able to turn over that code to our internal programming development team. Initial tests on the test build are very promising and we are hopeful for a near-term release. This being said, there are still a couple of hurdles to clear and work will continue on these hurdles throughout this upcoming weekend to ensure that we get the fix out for everyone as absolutely soon as possible.

Overall, this week has been a tremendously large step in the right direction to resolving this very unfortunate and very long delay. We greatly apologize for the massive inconvenience this has caused, and we will look forward to sharing a more exact release date with you very soon.

Please stay tuned to this page as we will continue to provide updates as they become available.