You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Documentation/Pages/Build.md
+25Lines changed: 25 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,31 @@ Projects are generated by invoking `./SC.sh build` or `SC.bat build`.
33
33
This is for example the `Tools/SC-build.cpp` file for the `SCTest` test suite and the [SCExample](@ref page_examples):
34
34
\include Tools/SC-build.cpp
35
35
36
+
# How to Debug
37
+
38
+
1. Make sure to compile `SC::Build` invoking any of the `Build SCTest Debug | Release` vscode tasks for your architecture
39
+
2. Launch the `Debug SC-build` for your platform from vscode
40
+
41
+
With any other debugger or IDE other than vscode, after 1. just debug `_Build/_Tools/Windows/SC-build.exe` (or the equivalent on other platform) with similar arguments as passed by the vscode task (replace `${workspaceFolder}` with the path where Sane C++ Libraries are located).
42
+
The first argument is the path to SC Libraries, then you have the tools directory and the directory of the build outputs.
43
+
As forth argument you have the name of the tool (`build` for `SC-Build`) and then any custom argument to the tool (`configure`, `SCTest` in the example below)
0 commit comments