Build from Source in Visual Studio 2015 ; big problems

evelyn4you · November 15, 2016, 4:01pm

hello dear friends of Xenko,

the last days i had much struggle to build the xenko binaries from source code from the following link on github:

Installation of the Xenko - Editor with the precompiled binaries was no problem.
The sampled can be modified an compiled an be run in VS 2015 without problem.

Die Xenko Addon was installed in VS 2015 and the environment variable is set.

Compiling the solution gives hundreds of errors because of the many, many dependencies one dll has from the others an so one. Everyone who has checked the source code knows what i mean.

I desperately tried to find the first core.dll code which should not have any other dependencies but that i could not figure out.

Visual Studio is installed completely with updates from microsoft.

Please can someone really try to compile the given Solution on github ?

The explanation howto compile such a very, very complex solution with such a big amount of dependent dll files should be some more in detail.

Any help possible ?

The reason why i want compile the binaries myself is, that i want to migrate a game project to xenko, but want to be shure that i can solve upcoming problems by modifying the source code.

Kryptos · November 15, 2016, 4:34pm

From which branch did you try to build the sources?

evelyn4you · November 15, 2016, 9:02pm

hello Kryptos4h,

i tried the branch “master”.

The others seem to me the older versions which a provide for compatibility reasons of user which made a game with the old versions.

Did i miss something ?

Kryptos · November 16, 2016, 3:38am

Master actually contains experimental features that very probably will not be compatible with any publicly released version of the editor. While this should not have prevented you from building from master (we will investigate this), it is safer to build from a released tag first. Note that the same remark applies to the branch of the future version of Xenko (currently 1.9) as the released editor will not work with it.

The last released version being 1.8.3, you should checkout the commit corresponding to this tag, and eventually branch from it. There might be commits after the tag that are not released in a version yet but do fix some issues. You can probably checkout master-1.8 as-is, as we try to avoid breaking changes between minor releases, although there is no guarantee that a particular commit might not break.

Hope this can help.