**/build/macos

This is a repository of C++ (C++11 and C++2a) examples of using GTK+ v3 to build Graphical User Interfaces for system applications using the `gtkmm` library for C++ bindings.

You can use `gtk`'s C bindings instead of `gtkmm`, but to write more modern code in C++ style we decided to use `gtkmm`.

For more testing purposes, we're also building with GCC 9 using the C++2a standard ("C++20") and testing out the latest language features with the GUI apps shown here.

Once you've followed the build-and-setup section, you should go to the [test_install](test_install/README.md) documentation and follow those instructions to verify that everything is setup correctly.

Follow the setup instructions for your system before trying to build, modify, or run any of the provided example subprojects in this repository.

Note that with macOS Catalina (10.15.x), Apple changed the default shell for the system and user accounts to be `zsh` instead of `bash`. You shouldn't need to change it to run anything here, but I built everything using `bash` instead of `zsh`, so for reference here's how I updated my config:

chsh -s /bin/bash;

touch ~/.bash_profile;

touch ~/.bashrc;

echo "source ~/.bashrc" >> ~/.bash_profile;

And then you can use either `~/.bashrc` or `~/.bash_profile` to put your shell preferences in. As configured, it's preferable to put everything in `~/.bashrc` since that'll be `source`-ed (read: "imported") by the `~/.bash_profile` file. I do this typically just to try and keep things more comparable to Linux systems that I use and work with, since they tend to only use a `~/.bashrc` config file and don't have the `~/.bash_profile` version. Most (if not all) of the configs are compatible between macOS and Linux, so putting everything into `~/.bashrc` this way can make the config more portable and reusable.

Again, the above is optional, but it's what I did, so there may be `bash`-specific commands referenced, and if you're using `zsh` you may get errors that I didn't. So please just be aware of that so that you don't get stuck or post a config-specific issue. If you'd like to request `zsh` support for this repo, please create an Enhancement issue on GitHub.

For the rest of the setup, the steps we'll follow are:

1. Install Homebrew, to make library installations consistent and (relatively) config-proof.

1. Use Homebrew to install the GTK+ v3 library and its dependencies.

1. Download and install a macOS compatible D Language Compiler.

1. Download the `gtkd` source code.

1. Build and install `gtkd`.

This process, all together, should take about 30-60 minutes with downloads and depending on your system specs.

1. [Homebrew](https://brew.sh/) install:

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

1. C++ Compiler installation (we're using GCC 9.3.x from Homebrew):

bre install gcc;

1. Homebrew install GTK+ v3 to macOS system:

brew install gtk+3;

brew install gtkmm3; # Optional, C++ bindings in-case you want to do C++ development.

1. Go to the [test_install README](test_install/README.md) and confirm that the application builds and runs.

Simple example to confirm that the installation of prerequisites was successful.

See the [test_install README](test_install/README.md) for more info.

This is an example app to confirm that GTK+3 and gtkmm are installed, as well as a valid C++ compiler.

You should have been directed here as the first to run after cloning out this repository, to confirm that your system is ready for development with GTK+ v3.x.y (GTK+3).

- GTK+ v3 installed on system.

- C++ Compiler (modern).

- GNU Make v3.82 or higher.

- macOS Catalina (10.15.4)

- Homebrew: [https://brew.sh/](https://brew.sh/)

- GTK+3 install: 3.24.18 (2020-04-14, macOS Homebrew)

- GCC install: 9.3.0_1 (macOS Homebrew)

- GNU Make (`gmake`) install: 4.3 (macOS Homebrew)

Currently this only supports macOS.

To build the application defined in the `src/` directory, use the following `bash` commands:

cd <REPO_PATH>/build/macos/;

make;

The above should build an executable file named `test_install` that can be run (see below).

After following the build instructions:

./test_install;

That above command should pop-open a small Application Window with a few widgets in it.

If that succeeds, then your system is all set to run through the other examples.

If you get an error or some issue with any of the above commands, you'll need to re-review the prerequisites and confirm that your system is configured correctly.

- Name: `test_install` (defined in `Makefile`)

- Size: `20.15 kiB`

.RECIPEPREFIX = +

CC_STD = c++2a

GCC := gcc-9 --std=$(CC_STD)

FLAGS = -Wall -Wextra -Werror -pedantic -g

LIB_GTKMM = gtkmm-3.0

LIB_GLIB = glib-2.0

LIBS := `pkg-config $(LIB_GTKMM) $(LIB_GLIB) --cflags --libs` -lstdc++

BINTAG ?= # `date +D%Y.%m.%d_T%H.%M.%S_Z%z`

EXE_NAME_BASE ?= test_install

SRC_DIR := ../../src

.DELETE_ON_ERROR:

.PHONY: all

all:

+ $(GCC) $(FLAGS) \

-o $(EXE_NAME_BASE)$(BINTAG) \

$(SRC_DIR)/main.cpp \

$(LIBS)

+ chmod +x $(EXE_NAME_BASE)$(BINTAG)

.PHONY: clean

clean:

+ rm ./$(EXE_NAME_BASE)

#include <gtkmm.h>

int main(int argc, char * argv[])

{

auto app = Gtk::Application::create(

argc

, argv

, "leafyrabbet_app"

);

Gtk::Window window;

Gtk::Box box_layout(Gtk::ORIENTATION_VERTICAL);

Gtk::Entry wdgt_textentry;

Gtk::CheckButton wdgt_btn_success;

Gtk::CheckButton wdgt_btn_fail;

window.set_default_size(420, 80);

wdgt_textentry.set_text("Success!");

box_layout.pack_start(wdgt_textentry);

box_layout.pack_start(wdgt_btn_success);

box_layout.pack_start(wdgt_btn_fail);

window.add(box_layout);

window.show_all_children();

auto ret_code = app->run(window);

return (ret_code);

}