1

I just learned the basics for git bash and GitHub, and I want to start using a repository for a simple console-based text game in C++ that I will be making. I have a MacBook laptop that I use to code on the go in XCode, and when I am home I use my Windows desktop in Visual Studio.

My question is "How do I run a C++ program from GitHub for both of these IDE's after I have cloned it?"

Should I just get the same IDE for both computers, like Eclipse? I've done quite a bit of research, but everything seems super complicated. I am hoping that there's an easier way, as I'm just a hobby coder. I'm definitely willing to learn; I just hate copying and pasting commands without understanding what they do. Any help is appreciated :)

Edited: Clarified that I know how to clone. The running part is what I don't know how to do.

Zeke Willams
  • 170
  • 11
  • 1
    [Here](https://help.github.com/articles/cloning-a-repository/) is the online documentation. There are links for the different operating systems. – wally Apr 16 '18 at 18:21
  • I clarified my question a bit. I know how to clone a repository. I don't know how to run it, if it's a c++ program once I've cloned it. – Zeke Willams Apr 16 '18 at 18:26
  • You can create a project from existing code for [XCode](https://stackoverflow.com/questions/5942059/creating-an-xcode-project-with-existing-code) or [VS](https://stackoverflow.com/questions/4853550/import-existing-c-source-code-into-visual-studio). Or you could use something like CMake to do it for you. – wally Apr 16 '18 at 18:30

1 Answers1

1

There really are several ways to do what you're asking.

  1. Store the project files with your repo, usually in a dedicated folder
    • msvc (with version)
    • xcode
    • makefile
    • qt creator
    • kdevelop
    • etc....
  2. generalize the c++ with another build-system like CMake

The first option will/can get annoying but it is usually where most people starting to learn to program go. It isn't too bad so long as you realize you'll probably have problems sharing your project as no one has 'quite' the same exact setup as you.

The second option is where most projects usually end up. You need to learn the intricacies of something like CMake but once you learn, projects can be made for almost any IDE/environment.

g19fanatic
  • 10,567
  • 6
  • 33
  • 63