MacOS/Linux - Building (Part 1)

Gathering and verifying all of the prerequisite tooling, libraries and setting up the Development environment will save time.

1. MacOS|Linux Install X-Code To install Xcode, you can download it from the Mac App Store. Alternatively, you can use the command line tool xcode-install to automate the installation process.
2. MacOS|Linux Homebrew Installer
3. MacOS Packages Download 1.2.11 If you already have packages installed, you should read this article for instructions on updating your existing installation.
4. MacOS|Linux Python
   1. MacOS MacOS Installer
   2. Linux Linux users will use the Homebrew installer
5. MacOS|Linux Read about the installation options for wxWidgets.
   1. MacOS|Linux Study Build Configurations
   2. DO NOT use the pre-built binaries.
   3. MacOS|Linux Download the Latest Stable Release²⁾
6. MacOS|Linux Download SDL Release 2.32.4
7. MacOS|Linux README (Libsndfile)
   • MacOS|Linux Download Libsndfile Release 1.22

This tutorial article relies on the the Hobbyist's prior understanding of the tools noted above. Before proceeding, understading the Development repository's structure is also a critical element in generating a successful build.

To install Xcode, you can download it from the Mac App Store . Alternatively, you can use the command line tool xcode-install to automate the installation process.

To install build tools, paste at a terminal prompt:

Debian or Ubuntu

  sudo apt-get install build-essential procps curl file git

Fedora, CentOS, or Red Hat/Rocky

  sudo yum groupinstall 'Development Tools'
  sudo yum install procps-ng curl file git

(NOTE: you may use the 'dnf' command instead of 'yum' on modern installations.)

Arch Linux

  sudo pacman -S base-devel procps-ng curl file git

Homebrew installs packages to their own directory and then symlinks their files into /opt/homebrew (on Apple Silicon) and in /home/linuxbrew on Linux distributions. Homebrew won’t install files outside its prefix and you can place a Homebrew installation wherever you like. It’s all Git and Ruby underneath, so hack away with the knowledge that you can easily revert your modifications and merge upstream updates.

(ALL Platforms)

Bootstrapping Homebrew on Linux or Mac is done by issuing the following command:

 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

(MacOS)

On MacOS - you may use the Homebrew installation package .

(Linux)

Install Python Minimum version 3.12 or greater, using the Homebrew installer.

 brew install python@3.13

(MacOS)

From the Python Download page, install Python using the Universal Installer .

(ALL Platforms)

Ensure that you have the proper version by issuing the following command:

 python3 --version

Python will respond with the following information

 Python 3.x.y

Where: x (minor version) is 12 or greater and y is the patch level for that minor version Set the environment variable PYTHONUTF8 to '1':

 export PYTHONUTF8=1

You are encouraged to simply add this statement to your .bashrc or equivalent environment-setting resource.

Once installation is complete, you must test the integrated build tool (a Python module called PTDevUtils) by issuing the following command:

 python3 -m PTDevUtils version

That command should produce the following response if Python was correctly installed:

 Package PTDevUtils
 Command PTDevUtils
 Version 1.0.1.0

On MacOS, the packaging process is arcane. This tool makes the process (virtually) painless.

MacOS

Homebrew's formula for wxWidgets builds the dynamically linked libraries. For packaging, distribution and general reliability, we want the statically-linked libraries. This requires us to modify the brew formula.

Launch the terminal application and perform the following procedure:

1. Set the variable HOMEBREW_NO_INSTALL_FROM_API to 1

export HOMEBREW_NO_INSTALL_FROM_API=1
   
   
2. Clone the homebrew core repository to the local installation
   
   brew tap –force homebrew/core
   
   
3. Edit the formula for wxwidgets ³⁾
   
   brew edit wxwidgets
   
   
   1. Search for the configuration option “–disable-monolithic”,.
   2. Insert the configuration option “–disable-shared”, immediately beneath it.
   3. :wq (Write/Quit)
      
      
4. Perform the build
   
   brew install –build-from-source –verbose –debug wxwidgets
   
   

Linux ANY LINUX SYSTEMS

On Linux systems it is generally preferable (and easier) to manually build the wxWidgets libraries “by hand”.

1. Ensure that the dependencies are satisfied:
   1. RHEL/Rocky Linux:
      
      sudo dnf -y install gtk3-devel
      
      
   2. Debian / Ubuntu:
      
      sudo apt-get install libgtk-3-dev
      
      
2. Download the sources for wxWidgets-3.2.7
3. Unzip/untar the tar.bz2 file into the Projects directory (along-side of the Pterm7 repository directory) as wxWidgets-3.2.7
4. Issue the following commands:
   
   

    cd <PathTo>/wxWidgets-3.2.7
    md gtk-build
    cd gtk-build
    ../configure --disable-shared --with-gtk

   Verify the configuration results:

   Configured wxWidgets 3.2.7 for `x86_64-pc-linux-gnu' Which GUI toolkit should wxWidgets use? GTK+ 3 with support for GTK+ printing Should wxWidgets be compiled into single library? no Should wxWidgets be linked as a shared library? no Should wxWidgets support Unicode? yes (using wchar_t) What level of wxWidgets compatibility should be enabled? wxWidgets 2.8 no wxWidgets 3.0 yes Which libraries should wxWidgets use? STL no jpeg builtin png sys regex sys tiff sys lzma no zlib sys expat builtin libmspack no sdl no

5. Perform the make with 6 parallel processes so the build doesn't take forever:
   
   make -j6
   
   
6. (Optionally) build the samples and demos
   
   cd samples; make -j6; cd ..
cd demos; make -j6; cd ..
   
   

Linux

It is frequently the case that the installed libraries are not in the available load path. The loader path may need to be added prior to execution of pterm. This command may need to be used to update the standard load library path:

  export LD_LIBRARY_PATH=/home/linuxbrew/.linuxbrew/lib:$LD_LIBRARY_PATH

The other option is to examine the libraries required using the 'ldd' command ⁴⁾ to determine which libraries are needed, and simply copy them into the same directory as the executable.

MacOS|Linux

 brew install libsndfile

Linux

On Linux systems, use of the distribution-specific libraries is recommended.

• Debian / Ubuntu
  sudo apt-get install libsdl2-dev
  
  
• RHEL / Rocky
  sudo dnf install SDL2-devel
  or
  sudo yum install SDL2-devel
  
  

MacOS|Linux(Preferred)

 brew install sdl2

MacOS/Linux - Building (Part 2)