build instruction from base directory

Eddio0141 · Aug 12, 2023 · edbe4e8 · edbe4e8
1 parent a4b81bb
commit edbe4e8
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/.github/workflows/build-on-push.yml b/.github/workflows/build-on-push.yml
@@ -22,9 +22,9 @@ jobs:
         uses: FedericoCarboni/setup-ffmpeg@v2
       - name: Tests
         working-directory: ./UniTAS
-        run: dotnet test --configuration ${{ matrix.configuration }}
+        run: dotnet test UniTAS --configuration ${{ matrix.configuration }}
       - name: Build
-        run: dotnet build --configuration ${{ matrix.configuration }}
+        run: dotnet build UniTAS --configuration ${{ matrix.configuration }}
       - name: Get built artifacts
         uses: actions/upload-artifact@v3.1.1
         with:

diff --git a/README.md b/README.md
@@ -42,8 +42,8 @@ You can use [unitas_setup_tool](https://github.com/Eddio0141/unitas_setup_tool)
 # How to build
 
 - Make sure you have [.NET SDK 7.0](https://dotnet.microsoft.com/en-us/download) installed on your system
-- Switch to the inner `UniTAS` directory
-- Run `dotnet build`
+- Run `dotnet build UniTAS` at the base directory
+  - Remove the `UniTAS` if you are in the inner `UniTAS` directory
   - If you need to choose `Release` or `Debug` config, do so with the `--configuration` flag
 - Output folder would be in `UniTAS/Patcher/bin/{Debug|Release}`
   - The output content can be copied directly inside a `BepInEx` folder to be used