Not the best start building from sources


I am trying to build cinder from the sources with Visual Studio 2015.
I followed the instructions here and so far, two things went wrong:

First, the git clone --recursive git:// cinder_master command failed:

$ git clone --recursive git:// cinder_master
Cloning into 'cinder_master'...
fatal: unable to connect to[0:]: errno=Invalid argument[1:]: errno=Invalid argument

Second, the git clone --recursive cinder_master command was only partially successful:

$ git clone --recursive cinder_master
Cloning into 'cinder_master'...
remote: Counting objects: 104628, done.
remote: Compressing objects: 100% (26/26), done.
remote: Total 104628 (delta 8), reused 15 (delta 4), pack-reused 104598
Receiving objects: 100% (104628/104628), 405.47 MiB | 2.81 MiB/s, done.
Resolving deltas: 100% (66421/66421), done.
Checking connectivity... done.
Checking out files: 100% (7164/7164), done.
Submodule 'include/boost' (git:// registered for path 'include/boost'
Submodule 'tools/TinderBox-Mac' (git:// registered for path 'tools/TinderBox-Mac'
Submodule 'tools/TinderBox-Win' (git:// registered for path 'tools/TinderBox-Win'
Cloning into 'include/boost'...
fatal: unable to connect to[0:]: errno=Invalid argument[1:]: errno=Invalid argument

Clone of 'git://' into submodule path 'include/boost' failed

Cinder and Tinder-Box were correctly updated but Cinder-boost wasn’t.

I have a few questions:
Do Cinder still need the boost behemoth now that with have C++1x ?
What are the difference between Cinder-Boost and boost? Can I just clone the official boost version into include/boost and get on the way?


Looks like you’re having trouble connecting to Github. Could it be a network or password issue?

Regarding Boost: Cinder is only using a relatively small subset of it and is on its way to phasing out Boost entirely.


Thank you for your time Paul,

Being at work, probably. But here are some puzzling facts:

  • We are using at least a dozen external libraries and I never have had any connection issue with GitHub before,
  • Of the 3 submodules, only Cinder-Boost is problematic,
  • Changing .gitmodule to switch the 3 submodules from git to https doesn’t fix the problem, while
  • Using the git clone --recursive include/boost -b boost_1_60 command ALONE works like a charm.


If no idea comes to your mind over this, please forget the whole thing as we have a workaround.

Btw, do you intend to support VS2017 in the near future? VS2013 compiler is really crappy for modern C++.


It might also be that Github’s server is very busy. Happens a lot lately.

Regarding VS2017: chances are it is already supported. You can try to open your project in VS2017. Personally, I would not upgrade the project when prompted. That way, you can first see if you can use the project (as is) with the new IDE. Then, update to the new toolset manually (in the project’s settings) to see if it compiles under VS2017.