|
|
@@ -1,8 +1,8 @@
|
|
|
-# Build details
|
|
|
+# Build details
|
|
|
This is a technical description what happens in our build and how it is organized. This covers mostly the build architecture of Stride itself.
|
|
|
|
|
|
* [Targets](../Targets) contains the MSBuild target files used by Games
|
|
|
-* [sources/common/targets](../sources/common/targets) (generic) and [sources/targets](../sources/targets) (Stride-specific) contains the MSBuild target files used to build Stride itself.
|
|
|
+* [sources/common/targets](../sources/common/targets) (generic) and [sources/targets](https://github.com/stride3d/stride/tree/master/sources/targets) (Stride-specific) contains the MSBuild target files used to build Stride itself.
|
|
|
|
|
|
Since 3.1, we switched from our custom build system to the new csproj system with one nuget package per assembly.
|
|
|
|
|
|
@@ -18,7 +18,7 @@ Also, we use `RuntimeIdentifiers` to select graphics platform. [MSBuild.Sdk.Extr
|
|
|
|
|
|
Since we want to package tools (i.e. GameStudio, ConnectionRouter, CompilerApp) with a package that contains only the executable with proper dependencies to other NuGet runtime packages, we use NuGet API to resolve assemblies at runtime.
|
|
|
|
|
|
-The code responsible for this is located in [Stride.NuGetResolver](../../../sources/shared/Stride.NuGetResolver).
|
|
|
+The code responsible for this is located in [Stride.NuGetResolver](https://github.com/stride3d/stride/tree/master/sources/shared/Stride.NuGetResolver).
|
|
|
|
|
|
Later, we might want to take advantage of .NET Core dependency resolving to do that natively. Also, we might want to use actual project information/dependencies to resolve to different runtime assemblies and better support plugins.
|
|
|
|
Vaclav Elias