Нет описания

Chris Galvan 2f6d92b1ab Merge pull request #17 from aws-lumberyard-dev/cgalvan/gitflow_211130_netsoaktest_main 3 лет назад
Config 48f6a3e2d8 Add default atom assets 4 лет назад
Gem a0d9180d7a Update NetSoakTest against recent AzNetworking changes 3 лет назад
Levels ebdc969732 Initial commit 4 лет назад
Scripts 256c1deb6b Add Jenkins configuration file for the netsoaktest project (#13) 3 лет назад
ShaderLib 3358acb4a3 Shorten copyright headers by splitting into 2 lines 4 лет назад
Shaders 3358acb4a3 Shorten copyright headers by splitting into 2 lines 4 лет назад
.gitattributes ebdc969732 Initial commit 4 лет назад
.gitignore ebdc969732 Initial commit 4 лет назад
.lfsconfig 32e141221c Updating .lfsconfig comments only 4 лет назад
CMakeLists.txt 3358acb4a3 Shorten copyright headers by splitting into 2 lines 4 лет назад
EngineFinder.cmake 3358acb4a3 Shorten copyright headers by splitting into 2 lines 4 лет назад
LICENSE.txt 7c0c2a38a7 o3de-netsoaktest main - License Change 4 лет назад
LICENSE_APACHE2.TXT 7c0c2a38a7 o3de-netsoaktest main - License Change 4 лет назад
LICENSE_MIT.TXT 7c0c2a38a7 o3de-netsoaktest main - License Change 4 лет назад
README.md 7c0c2a38a7 o3de-netsoaktest main - License Change 4 лет назад
autoexec.cfg ebdc969732 Initial commit 4 лет назад
game.cfg ebdc969732 Initial commit 4 лет назад
preview.png ebdc969732 Initial commit 4 лет назад
project.json ebdc969732 Initial commit 4 лет назад

README.md

NetSoakTest Project

Download and Install

This repository uses Git LFS for storing large binary files. You will need to create a Github personal access token to authenticate with the LFS service.

Create a Git Personal Access Token

You will need your personal access token credentials to authenticate when you clone the repository.

Create a personal access token with the 'repo' scope.

(Recommended) Verify you have a credential manager installed to store your credentials

Recent versions of Git install a credential manager to store your credentials so you don't have to put in the credentials for every request.
It is highly recommended you check that you have a credential manager installed and configured

Clone the repository

There are two options when installing a project

Option #1 (Recommended) - Project-centric approach to building a project

This option lets you keep engine and project files in separate locations.

# clone the project into a folder outside your engine repository folder
> git clone https://github.com/o3de/o3de-netsoaktest.git
Cloning into 'o3de-netsoaktest'...

# register the engine
> C:/Path/To/o3de/scripts/o3de.bat register --this-engine

# register the project 
> C:/Path/To/o3de/scripts/o3de.bat register -p C:/Path/To/o3de-netsoaktest

# example configure command
> cmake -S C:/Path/To/o3de-netsoaktest -b C:/Path/To/o3de-netsoaktest/build -G "Visual Studio 16 2019" -DLY_3RDPARTY_PATH="C:/3rdparty"

# example build command
> cmake --build C:/Path/To/o3de-netsoaktest/build --target Editor NetSoakTest.GameLauncher --configure profile -- /m /nologo 

Option #2 - Engine-centric approach to building a project

This option models the legacy folder layout where all projects were in the same folder as the engine. If you use this approach you must also modify your engine's local git exclude file to ignore the project folder.

# clone the project in a folder named 'NetSoakTest' in your existing engine repository folder
> git clone https://github.com/o3de/o3de-netsoaktest.git C:/path/to/engine/NetSoakTest
Cloning into 'NetSoakTest'...

# modify the local engine git exclude file to ignore the project folder
> echo NetSoakTest > C:/Path/To/o3de/.git/info/exclude

# the project now exists inside the engine folder but your engine repository will ignore all files in the project folder

# example configure command
> cmake -S C:/Path/To/o3de -b C:/Path/To/o3de/build -G "Visual Studio 16 2019" -DLY_3RDPARTY_PATH="C:/3rdparty" -DLY_PROJECTS=NetSoakTest 

# example build command
> cmake --build C:/Path/To/o3de/build --target Editor NetSoakTest.GameLauncher --configure profile -- /m /nologo 

If you have a Git credential helper configured, you should not be prompted for your credentials anymore.

License

For terms please see the LICENSE*.TXT file at the root of this distribution.