How to pull the latest dependancies for building from master?
I decided to take a quick peek at master from github so went and updated my fork, pulled that fork into a new local repo and tried building it like I originally did 4.0 when I first got it.
I updated the dependencies from 4.0 version to 4.1 but looks like some dependencies have changed (the build fails trying to build FBX because the sdk version has changed from 2013 to 2014 and that isn't included in the dependencies zips). So my question is regarding getting up-to-date dependency zips for the current master when that changes.
How do I maintain the bleeding edge source code, if the bleeding edge requires dependencies for anything to build and those aren't updated from the repo?
I'm kind of curious actually. Why aren't third party libraries that are required to build the source actually checked into github anyway? I mean I can understand stuff like content and templates, but third party libraries that sit under the engine source tree to my mind seem like they should be in the repo.
As it is, I don't have the 2014 version of the FBXSDK required to build with. There are also a couple more build failures, I assume from the same issue (incorrect version of the third party stuff not in required dependency zip files).
Whats the recommended way to keep a bleeding edge mirror of the engine build tree?
asked May 23 '14 at 04:53 PM in Bug Reports
Try 4.2 preview zips
answered May 23 '14 at 05:31 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here