doc: mv png position

Nuclei-Software · Aug 16, 2024 · d1508f0 · d1508f0
1 parent 2131f3d
commit d1508f0
Show file tree

Hide file tree

Showing 44 changed files with 22 additions and 22 deletions.
diff --git a/1-cannot-setup-guestmemory.md b/1-cannot-setup-guestmemory.md
@@ -6,6 +6,6 @@
 qemu-system-riscv64.exe: cannot set up quest memory 'riscv.evalsoc.flashxip' Invalid argument
 ```
 
-![](asserts/images/cannotsetupguestmemiry.png)
+![](asserts/images/1/cannotsetupguestmemiry.png)
 
 一般可以通过关闭某些应用，释放一部分内存以供qemu使用，即可解决些问题。
diff --git a/10-compiling_projects_with_headless_in_nuclei_studio.md b/10-compiling_projects_with_headless_in_nuclei_studio.md
@@ -31,7 +31,7 @@ set PATH=%NSIDE%\toolchain\gcc\bin;%NSIDE%\toolchain\build-tools\bin;%PATH%
 
 > 这个**2023.10**版本的举例的命令 会 弹出一个额外的命令行窗口进行输出。
 
-![Nuclei Studio Command Line Build](asserts/images/wx_20231208153525.png)
+![Nuclei Studio Command Line Build](asserts/images/10/wx_20231208153525.png)
 
 - `NucleiStudio.exe`：该参数是Nuclei Studio的启动应用，在Nuclei Studio的安装目录下。
 - `--launcher.suppressErrors`：该参数是用于抑制Nuclei Studio启动时的错误信息。

diff --git a/12-nucleisdk-0.5.0-dhrystone-score-lower-than-expected-in-IDE.md b/12-nucleisdk-0.5.0-dhrystone-score-lower-than-expected-in-IDE.md
@@ -18,9 +18,9 @@
 
 4. 但实际需要跑分时，要先取消选中`-msave-restore`选项，该跑分结果为**1.664**。
 
-![](asserts/images/12-1.png)
-![](asserts/images/12-2.png)
-![](asserts/images/12-3.png)
-![](asserts/images/12-4.png)
-![](asserts/images/12-5.png)
-![](asserts/images/12-6.png)
+![](asserts/images/12/12-1.png)
+![](asserts/images/12/12-2.png)
+![](asserts/images/12/12-3.png)
+![](asserts/images/12/12-4.png)
+![](asserts/images/12/12-5.png)
+![](asserts/images/12/12-6.png)
diff --git a/13-error_could_not_find_an_available_hardware_trigger.md b/13-error_could_not_find_an_available_hardware_trigger.md
@@ -8,9 +8,9 @@ Error: Couldn't find an available hardware trigger.
 Error: can't add breakpoint: resource not available
 ```
 
-![](asserts/images/13-1.png)
+![](asserts/images/13/13-1.png)
 
-![](asserts/images/13-2.png)
+![](asserts/images/13/13-2.png)
 
 是因为所运行的CPU不支持硬件断点，导致程序运行在Flash上的时候，IDE调试功能无法正常工作，这个是IDE会需要打一个临时断点的缘故导致的。如果需要下载并运行程序，切换到Run运行模式可以正常运行程序。
 

diff --git a/14-cannot_find_-lncrt_balanced_no_such_file_or_directory.md b/14-cannot_find_-lncrt_balanced_no_such_file_or_directory.md
@@ -10,11 +10,11 @@ G:/NucleiStudio/toolchain/gcc/bin/../lib/gcc/riscv64-unknown-elf/13.1.1/../../..
 G:/NucleiStudio/toolchain/gcc/bin/../lib/gcc/riscv64-unknown-elf/13.1.1/../../../../riscv64-unknown-elf/bin/ld.exe: cannot find -lncrt_balanced: No such file or directory
 ```
 
-![](asserts/images/14-1.png)
+![](asserts/images/14/14-1.png)
 
 是因为在创建工程时，我们创建了一个64位的工程，同时在Standard C Library时，选择了带`-lncrt_balanced`、`-lfileops_uart`的扩展，而此类扩展又不支持64位，导致编译不通过。
 
-![](asserts/images/14-2.png)
+![](asserts/images/14/14-2.png)
 
 ## 解决方案
 

diff --git a/15-unsatisfiedLinkError_of_swt-win32-4965r8_dll_on_windows7.md b/15-unsatisfiedLinkError_of_swt-win32-4965r8_dll_on_windows7.md
@@ -41,11 +41,11 @@ java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
 
 是因为在eclipse 2024.06版本中，有使用到一些特性，而该特性对操作系统有要求，可以参考 https://github.com/eclipse-platform/eclipse.platform.swt/issues/1252
 
-![](asserts/images/15-1.png)
+![](asserts/images/15/15-1.png)
 
 并且在eclipse的官方文档中，针对eclipse测试的操作系统中也做了说明，对某些版本的操作系统不再做兼容。可以参考 https://eclipse.dev/eclipse/development/plans/eclipse_project_plan_4_32.xml#target_environments
 
-![](asserts/images/15-2.png)
+![](asserts/images/15/15-2.png)
 
 而NucleiStudio 2024.06是基于eclipse 2024.06，所以也会有同类型的问题。
 

diff --git a/2-qemu-glib-gio-unexpectedly.md b/2-qemu-glib-gio-unexpectedly.md
@@ -1,10 +1,10 @@
 # windows 11下使用Nuclei Studio进行qemu调试程序时报错
 
-windows 11下使用Nuclei Studio开发时，当使用qemu调试程序时,会有报错如下，是因为在windows 11下缺少相关依赖，但一般不引响qemu的正确使用，可以呼略此错误。
+windows 11下使用Nuclei Studio开发时，当使用qemu调试程序时,会有报错如下，是因为在windows 11下缺少相关依赖，但一般不影响qemu的正确使用，可以忽略此错误。
 ```
 qemu-system-riscv32.exe: warning: GLib-GIO: Unexpectedly, UWP app `Microsoft.ScreenSketch_11.2309.16.0_x64__8wekyb3d8bbwe' (AUMId `Microsoft.ScreenSketch_8wekyb3d8bbwe!App') supports 29 extensions but has no verbs
 qemu-system-riscv32.exe: warning: GLib-GIO: Unexpectedly, UWP app `Clipchamp.Clipchamp_2.8.1.0_neutral__yxz26nhyzhsrt' (AUMId `Clipchamp.Clipchamp_yxz26nhyzhsrt!App') supports 41 extensions but has no verbs
 
 ```
 
-![](asserts/images/vx_16993400095638.png)
+![](asserts/images/2/vx_16993400095638.png)
diff --git a/4-use_pre_build_or_post_build.md b/4-use_pre_build_or_post_build.md
@@ -6,8 +6,8 @@
 
 在Nuclei Studio 2023.10版本中，如果在工程编译中需要使用到Pre-build Command/Post-build Command, 因Nuclei Studio中集成的build-tools为v4.4.0版本，而上游CDT中在处理Pre-build Command/Post-build Command的方法，在build-tools v4.4.0无法正常使用，所以会出现报错问题。
 
-![](asserts/images/20231113181414.png)
-![](asserts/images/20231113181518.png)
+![](asserts/images/4/20231113181414.png)
+![](asserts/images/4/20231113181518.png)
 
 遇到这种情况时，可以下载 https://www.nucleisys.com/upload/files/toochain/build-tools/build-tools_202002.zip ，并替换工具链中的build-tools，问题可以得到解决。
 

diff --git a/5-update_npk_to_support_nucleistudio_202310.md b/5-update_npk_to_support_nucleistudio_202310.md
@@ -155,7 +155,7 @@ buildconfig:
 
 最终显示创建项目的时候显示效果如下
 
-![企业微信截图_16999495827037](https://github.com/Nuclei-Software/nuclei-studio/assets/1538922/dc9aeec3-0887-4a28-8fb7-418c98c9e4de)
+![](asserts/images/5/create_project.png)
 
 
 ## libncrt的升级

diff --git a/7-update_nucleistudio_202310_to_fixed_version.md b/7-update_nucleistudio_202310_to_fixed_version.md
@@ -32,15 +32,15 @@
 在Nuclei Studio菜单中找到**Help->Install New Software**, 然后在Install工具的`Work with`
 选中`NucleiStudio - https://ide.nucleisys.com/NucleiStudio/`,下面会列出所有待更新的插件。
 
-![](asserts/images/195660415249583.png)
+![](asserts/images/7/195660415249583.png)
 
 在弹出的插件列表中选中需要升级的插件，我们选中`RISC-V C/C++ Cross Development Tools`, 然后Next。
 
-![](asserts/images/v_20231116151002.png)
+![](asserts/images/7/v_20231116151002.png)
 
 在升级过程中，Nuclei Studio会询问Trust Artifacts时，操作如下图，选择Trust Selected, 然后升级完成，Nuclei Studio会重启。至此Nuclei Studio Plugins升级完成。
 
-![](asserts/images/v_18001190261409.png)
+![](asserts/images/7/v_18001190261409.png)
 
 **2. 升级build-tools**
 

diff --git a/asserts/images/cannotsetupguestmemiry.png → asserts/images/1/cannotsetupguestmemiry.png b/asserts/images/cannotsetupguestmemiry.png → asserts/images/1/cannotsetupguestmemiry.png
diff --git a/asserts/images/wx_20231208153525.png → asserts/images/10/wx_20231208153525.png b/asserts/images/wx_20231208153525.png → asserts/images/10/wx_20231208153525.png
diff --git a/asserts/images/12-1.png → asserts/images/12/12-1.png b/asserts/images/12-1.png → asserts/images/12/12-1.png
diff --git a/asserts/images/12-2.png → asserts/images/12/12-2.png b/asserts/images/12-2.png → asserts/images/12/12-2.png
diff --git a/asserts/images/12-3.png → asserts/images/12/12-3.png b/asserts/images/12-3.png → asserts/images/12/12-3.png
diff --git a/asserts/images/12-4.png → asserts/images/12/12-4.png b/asserts/images/12-4.png → asserts/images/12/12-4.png
diff --git a/asserts/images/12-5.png → asserts/images/12/12-5.png b/asserts/images/12-5.png → asserts/images/12/12-5.png
diff --git a/asserts/images/12-6.png → asserts/images/12/12-6.png b/asserts/images/12-6.png → asserts/images/12/12-6.png
diff --git a/asserts/images/13-1.png → asserts/images/13/13-1.png b/asserts/images/13-1.png → asserts/images/13/13-1.png
diff --git a/asserts/images/13-2.png → asserts/images/13/13-2.png b/asserts/images/13-2.png → asserts/images/13/13-2.png
diff --git a/asserts/images/14-1.png → asserts/images/14/14-1.png b/asserts/images/14-1.png → asserts/images/14/14-1.png
diff --git a/asserts/images/14-2.png → asserts/images/14/14-2.png b/asserts/images/14-2.png → asserts/images/14/14-2.png
diff --git a/asserts/images/15-3.png b/asserts/images/15-3.png
diff --git a/asserts/images/15-1.png → asserts/images/15/15-1.png b/asserts/images/15-1.png → asserts/images/15/15-1.png
diff --git a/asserts/images/15-2.png → asserts/images/15/15-2.png b/asserts/images/15-2.png → asserts/images/15/15-2.png
diff --git a/asserts/images/16-2.png b/asserts/images/16-2.png
diff --git a/asserts/images/16-3.png b/asserts/images/16-3.png
diff --git a/asserts/images/16-4.png b/asserts/images/16-4.png
diff --git a/asserts/images/16-5.png b/asserts/images/16-5.png
diff --git a/asserts/images/16/config_console_limit.png b/asserts/images/16/config_console_limit.png
diff --git a/asserts/images/16/config_terminal_limit.png b/asserts/images/16/config_terminal_limit.png
diff --git a/asserts/images/16/generated_fail.png b/asserts/images/16/generated_fail.png
diff --git a/asserts/images/16/overflow.png b/asserts/images/16/overflow.png
diff --git a/asserts/images/16-1.png → asserts/images/16/parse_profiling_fail.png b/asserts/images/16-1.png → asserts/images/16/parse_profiling_fail.png
diff --git a/asserts/images/16/refresh_project.png b/asserts/images/16/refresh_project.png
diff --git a/asserts/images/vx_16993400095638.png → asserts/images/2/vx_16993400095638.png b/asserts/images/vx_16993400095638.png → asserts/images/2/vx_16993400095638.png
diff --git a/asserts/images/20231113181414.png → asserts/images/4/20231113181414.png b/asserts/images/20231113181414.png → asserts/images/4/20231113181414.png
diff --git a/asserts/images/20231113181518.png → asserts/images/4/20231113181518.png b/asserts/images/20231113181518.png → asserts/images/4/20231113181518.png
diff --git a/asserts/images/5/create_project.png b/asserts/images/5/create_project.png
diff --git a/asserts/images/195660415249583.png → asserts/images/7/195660415249583.png b/asserts/images/195660415249583.png → asserts/images/7/195660415249583.png
diff --git a/asserts/images/v_18001190261409.png → asserts/images/7/v_18001190261409.png b/asserts/images/v_18001190261409.png → asserts/images/7/v_18001190261409.png
diff --git a/asserts/images/v_20231116151002.png → asserts/images/7/v_20231116151002.png b/asserts/images/v_20231116151002.png → asserts/images/7/v_20231116151002.png
diff --git a/asserts/images/nside_cmdbuild_20231201.png b/asserts/images/nside_cmdbuild_20231201.png
diff --git a/asserts/images/v_17001190261409.png b/asserts/images/v_17001190261409.png