Mirrors_UI_SDK/GacUI
1
0
Fork 0
mirror of https://github.com/vczh-libraries/Release.git synced 2026-08-17 09:21:41 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Sync Copilot guidance

Browse Source
This commit is contained in:
vczh
2026-07-12 23:03:57 -07:00
parent 03915cb31d
commit 479459c36d
4 changed files with 8 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/Guidelines/Building.md
+2 -7
View File
@@ -1,8 +1,7 @@
# Building a Solution
- Go to `Windows Specific` section if you are on Windows.
- Go to `Linux Specific` section if you are on Linux.
- Go to `macOS Specific` section if you are on macOS.
- Go to `Linux/macOS Specific` section if you are on Linux/macOS.
## Windows Specific
@@ -44,7 +43,7 @@ It is possible that, before running `copilotBuild.ps1`, the binary to compile is
- "0 Error(s)"
- DO NOT delete the log file by yourself.
## Linux Specific
## Linux/macOS Specific
Building only happens in a folder that has a `vmake` file.
- If the repo has only one project, it is in `REPO-ROOT/Test/Linux`.
@@ -58,7 +57,3 @@ Call `REPO-ROOT/.github/Ubuntu/build.sh -f` for full rebuild.
`build.sh` will also run other script files in that folder; you may need to run `chmod +x` if any script file is blocked.
Only the "debug x64" configuration is supported on Linux. If you are instructed to build and run other configuration, ignore it.
## macOS Specific
(to be editing...)
.github/Guidelines/Debugging.md
+2 -6
View File
@@ -1,7 +1,7 @@
# Debugging a Project
- Go to `Windows Specific` section if you are on Windows.
- Go to `Linux Specific` section if you are on Linux.
- Go to `Linux/macOS Specific` section if you are on Linux/macOS.
- Go to `macOS Specific` section if you are on macOS.
## Windows Specific
@@ -72,7 +72,7 @@ You can also use `dv -rX` to expand "X" levels of fields. The default option is
- DO NOT use **dt**.
- DO NOT use **q**, **qd**, **qq**, **qqd** etc. to stop the debugger.
## Linux Specific
## Linux/macOS Specific
Like building and running, debugging must be performed from the same folder that contains `vmake`:
- If the repo has only one project, it is in `REPO-ROOT/Test/Linux`.
@@ -102,7 +102,3 @@ quit
```
For non-interactive one-shot debugging, wrap `lldb` with `timeout` so it cannot block forever.
## macOS Specific
(to be editing...)
.github/Guidelines/Running-CLI.md
+2 -6
View File
@@ -1,7 +1,7 @@
# Running a CLI Application Project
- Go to `Windows Specific` section if you are on Windows.
- Go to `Linux Specific` section if you are on Linux.
- Go to `Linux/macOS Specific` section if you are on Linux/macOS.
- Go to `macOS Specific` section if you are on macOS.
## Windows Specific
@@ -31,7 +31,7 @@ cd SOLUTION-ROOT
- `-Platform` can be `x64` (default) or `Win32`
- Pick the default option (omit both arguments) when there is no specific requirement.
## Linux Specific
## Linux/macOS Specific
Building only happens in a folder that has a `vmake` file.
- If the repo has only one project, it is in `REPO-ROOT/Test/Linux`.
@@ -48,7 +48,3 @@ Compiled binary might have a bug causing it to trap in a dead loop. DO NOT just
If this seems suspicious, you are recommended to kill the process and run it again with the debugger.
Only the "debug x64" configuration is supported on Linux. If you are instructed to build and run other configuration, ignore it.
## macOS Specific
(to be editing...)
.github/Guidelines/Running-UnitTest.md
+2 -6
View File
@@ -1,7 +1,7 @@
# Running a Unit Test Project
- Go to `Windows Specific` section if you are on Windows.
- Go to `Linux Specific` section if you are on Linux.
- Go to `Linux/macOS Specific` section if you are on Linux/macOS.
- Go to `macOS Specific` section if you are on macOS.
## Windows Specific
@@ -73,7 +73,7 @@ Ignore `LocalDebuggerCommandArgumentsHistory` in `*.vcxproj.user`.
- Treat memory leak fixes as required work, especially after all test cases pass and the remaining failure signal is only the appended leak dump.
- DO NOT delete the log file by yourself.
## Linux Specific
## Linux/macOS Specific
Building only happens in a folder that has a `vmake` file.
- If the repo has only one project, it is in `REPO-ROOT/Test/Linux`.
@@ -98,7 +98,3 @@ If this seems suspicious, you are recommended to kill the process and run it aga
When `/D` or `/C` is specified, the unit test binary stops at the first failure, causing it to be unable to summarize how many test cases pass or fail at the end. This is an obvious signal that it fails.
Only the "debug x64" configuration is supported on Linux. If you are instructed to build and run other configuration, ignore it.
## macOS Specific
(to be editing...)