Chapter 37.2. GitHub

Just to make sure that we are on the same page, let's synchronize our environments.

You can download full current Project repository from

  • Windows solution, x86: _wg37-main\a997modeler\p_windows\p_windows.sln
  • Android solution, ARM64: _wg37-main\a997modeler\p_android\p_android.sln

Important changes here:

  • In order to untie the project from C:\CPP, all paths in projects properties were converted to relative form. Like ..\..\engine instead of C:\CPP\engine.
  • To make repository lighter I deleted unnecessary libraries from GLFW folder.

How to download repository from GitHub

1. Go to

2. Click green button "Code".

3. I usually pick "Download ZIP".

4. When downloaded, go to your Downloads folder and unpack file to your hard drive (usually C:).

5. Since all project's paths are relative, it is safe to rename created _wg37-main folder up to your taste (like "CPP" in my case).

Windows solution

6. Start Visual Studio,

7. Proceed to "Open a project or solution".

8. Open _wg37-main\a997modeler\p_windows\p_windows.sln

9. IMPORTANT: Make sure that configuration (in the top VS menu) is set to x86.

10. Rebuild and run the project (green arrow). Make sure it works.

Android solution

11. Restart Visual Studio,

12. Proceed to "Open a project or solution".

13. Open _wg37-main\a997modeler\p_android\p_android.sln

14. IMPORTANT: Make sure that configuration (in the top VS menu) is set to ARM64.

15. Switch on your Android, unlock, plug in to the comp, allow debugging.

16. Rebuild and run the project (green arrow). Make sure it works.

That's it.

Now our environments are not just compatible, but identical.

Just in case you ever need:

How to UPLOAD your project on GitHub

Let's say (as in my case) you have a folder/project on your computer that you want to publish on GitHub.

First, you will need a GitHub account. Go to and sign up.

Second, you will need a repository. Click on "+" in the upper right corner and add New repository.

  • To keep repository completely empty at this point, don't pick readmi or gitignore options. I created them locally and then uploaded to GitHub along with everything else.

Just in case, my file looks like this:

# _wg37
<a href=""></a> Chapter 37
<br />
<b>GameDev, 3D, cross-platform, C++, Visual Studio 2022, Android, Windows, OpenGL ES 3.2</b>
<br />
<a href="">Demo</a>
<br />
Windows solution, <b>x86</b>: <br />
<br />
Android solution, <b>ARM64</b>: <br />
<br />

My .gitignore file is just a copy of GitHub's template for Visual Studio:

## Ignore Visual Studio temporary files, build results, and
## files generated by popular Visual Studio add-ons.
## Get latest from

# User-specific files

# User-specific files (MonoDevelop/Xamarin Studio)

# Mono auto generated files

# Build results

# Visual Studio 2015/2017 cache/options directory
# Uncomment if you have tasks that create the project's static files in wwwroot

# Visual Studio 2017 auto generated files
Generated\ Files/

# MSTest test Results

# NUnit

# Build Results of an ATL Project

# Benchmark Results

# .NET Core

# ASP.NET Scaffolding

# StyleCop

# Files built by Visual Studio

# Chutzpah Test files

# Visual C++ cache files

# Visual Studio profiler

# Visual Studio Trace Files

# TFS 2012 Local Workspace

# Guidance Automation Toolkit

# ReSharper is a .NET coding add-in

# TeamCity is a build add-in

# DotCover is a Code Coverage Tool

# AxoCover is a Code Coverage Tool

# Coverlet is a free, cross platform Code Coverage Tool

# Visual Studio code coverage results

# NCrunch

# MightyMoose

# Web workbench (sass)

# Installshield output folder

# DocProject is a documentation generator add-in

# Click-Once directory

# Publish Web Output
# Note: Comment the next line if you want to checkin your web deploy settings,
# but database connection strings (with potential passwords) will be unencrypted

# Microsoft Azure Web App publish settings. Comment the next line if you want to
# checkin your Azure Web App publish settings, but sensitive information contained
# in these scripts will be unencrypted

# NuGet Packages
# NuGet Symbol Packages
# The packages folder can be ignored because of Package Restore
# except build/, which is used as an MSBuild target.
# Uncomment if necessary however generally it will be regenerated when needed
# NuGet v3's project.json files produces more ignorable files

# Microsoft Azure Build Output

# Microsoft Azure Emulator

# Windows Store app package directories and files

# Visual Studio cache files
# files ending in .cache can be ignored
# but keep track of directories ending in .cache

# Others

# Including strong name files can present a security risk
# (

# Since there are multiple workflows, uncomment next line to ignore bower_components
# (

# RIA/Silverlight projects

# Backup & report files from converting an old project file
# to a newer Visual Studio version. Backup files are not needed,
# because we have git ;-)

# SQL Server files

# Business Intelligence projects
*- [Bb]ackup.rdl
*- [Bb]ackup ([0-9]).rdl
*- [Bb]ackup ([0-9][0-9]).rdl

# Microsoft Fakes

# GhostDoc plugin setting file

# Node.js Tools for Visual Studio

# Visual Studio 6 build log

# Visual Studio 6 workspace options file

# Visual Studio 6 auto-generated workspace file (contains which files were open etc.)

# Visual Studio 6 auto-generated project file (contains which files were open etc.)

# Visual Studio 6 workspace and project file (working project files containing files to include in project)

# Visual Studio 6 technical files 

# Visual Studio LightSwitch build output

# Paket dependency manager

# FAKE - F# Make

# CodeRush personal settings

# Python Tools for Visual Studio (PTVS)

# Cake - Uncomment if you are using it
# tools/**
# !tools/packages.config

# Tabs Studio

# Telerik's JustMock configuration file

# BizTalk build output

# OpenCover UI analysis results

# Azure Stream Analytics local run output

# MSBuild Binary and Structured Log

# NVidia Nsight GPU debugger configuration file

# MFractors (Xamarin productivity tool) working folder

# Local History for Visual Studio

# Visual Studio History (VSHistory) files

# BeatPulse healthcheck temp database

# Backup folder for Package Reference Convert tool in Visual Studio 2017

# Ionide (cross platform F# VS Code tools) working folder

# Fody - auto-generated XML schema

# VS Code files for those working on multiple tools

# Local History for Visual Studio Code

# Windows Installer files from build outputs

# JetBrains Rider

Third, you will need git itself on your computer.

Go to -> Downloads -> Windows, and so on.

When installed, go to Windows File Explorer, right-click on your folder (which you want to share on Git) and pick Git Bash Here.
It will open a black prompt window.
You are already inside of your folder. Type

git init

It will create .git sub-folder.

Default branch is called master, when GitHub's default branch is called main.

In order to avoid merging branches in the future, I created main branch locally, taking the history from master. Command:

git branch -m master main

Next command will add your folder's content to your local git (skipping whatever mentioned in .gitignore):

git add .
  • Don't miss a dot at the end.

Then we need to make the first commit:

git commit -m "initial commit"

Now we need to bind our remote GitHub repository to our local folder:

git remote add origin
  • This is ONE single string
  • Don't forget to replace "your_git_account/your_repository_name" by your actual names

And to push local folder to remote GitHub repository:

git push -u origin main

That's it! It's online now.

Leave a Reply

Your email address will not be published. Required fields are marked *