For a proper linux install, the files need to go in a variety of places, and we need to compile with the FOR_DEB flag (so it looks in the right place for the program assets and language files). The easiest way of doing this is probably to replicate the makefile changes in commit https://github.com/bridgecommand/bc/commit/4ed5a3867d10e7fd3c96dc788fc2152fbb9335f7
Then, after building, the files go in the following locations:
Binaries in /usr/bin/
All of the following in /usr/share/bridgecommand:
bc5.ini languageRepeater-en.txt repeater.ini
Icon.ico LICENSE.txt Scenarios
languageController-en.txt map.ini shaders
language-en.txt media Sounds
languageIniEditor-en.txt Models tidalData.m
languageLauncher-en.txt mph.ini World
languageMultiplayer-en.txt README
The contents of the doc folder in /usr/share/doc/bridgecommand
(You can also create a launcher in /usr/share/applications, and icons in /usr/share/icons, but this is optional)
This is how the installation is structured for the .deb, and it will use "~/.Bridge Command" to store users' settings, as well as their own scenarions, ship or world models.