Skip to content

Commit 966dd85

Browse files
system debug: make documentation clearer that X64 option is required on windows (oneapi-src#139)
Co-authored-by: David Ludwig Wilson <[email protected]>
1 parent 9a90688 commit 966dd85

File tree

2 files changed

+21
-17
lines changed

2 files changed

+21
-17
lines changed

Tools/SystemDebug/docs/EFIApplication.rst

Lines changed: 16 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -163,6 +163,12 @@ We do this with:
163163

164164
``cmake ..``
165165

166+
.. note::
167+
On Windows, when using Visual Studio 2017 or older, you will need to specify the architecture.
168+
Please use the following cmake command:
169+
170+
``cmake .. -AX64``
171+
166172
then - on windows you will see a Visual Studio solution in the ``build``
167173
directory, uxdbgapp.sln, on POSIX systems you will see a MakeFile in the
168174
build folder.
@@ -233,30 +239,30 @@ follows:
233239
``./make_boot_media.sh uxdbgapp.efi <dev/disk>``
234240

235241

236-
NOTE
237-
----
238-
239-
if you have issues with permissions, you might have to make the script
240-
executable.
242+
.. note::
243+
if you have issues with permissions, you might have to make the script
244+
executable.
241245

242-
you can do this by issueing the following command in terminal:
246+
you can do this by issueing the following command in terminal:
243247

244-
``chmod +x make_boot_media.sh``
248+
``chmod +x make_boot_media.sh``
245249

246250
you can find information on the disks by using the following:
247251

248252
mac OS
249-
--------
253+
^^^^^^^^^^^^^^
254+
250255

251256
``diskutil list``
252257

253258
linux
254-
--------
259+
^^^^^^^^^^^^^^
260+
255261

256262
``sudo fdisk -l``
257263

258264
Windows
259-
------------
265+
^^^^^^^^^^^^^^
260266

261267
Start the powershell script, from a powershell prompt.
262268

Tools/SystemDebug/efi_application/README.md

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -55,6 +55,7 @@ To build the efi application, we use the `cmake` build system to generate the bu
5555
We do this with:
5656

5757
```cmake ..```
58+
> :warning: **If you are using Visual Studio 2017**: You will need to specify architecture. This can be done with `cmake .. -AX64`
5859
5960
then - on windows you will see a Visual Studio solution in the `build` directory, uxdbgapp.sln, on POSIX systems you will see a MakeFile in the build folder.
6061

@@ -63,19 +64,17 @@ You can then build this by issuing the following command:
6364

6465
```cmake --build .```
6566

66-
Or,
67-
6867
on Windows, you can open the visual studio solution, and build the uxdbgapp target.
6968

7069
On POSIX, you can run the makefile with `make -j`.
7170

7271

73-
##### windows builders
72+
#### __windows builders__
7473

7574
On windows, the output will be in the `Debug` folder in the build directory.
7675

7776

78-
#### Edk2 basetools
77+
#### __Edk2 basetools__
7978

8079
On windows, you will either need to build edk2 basetools, or get the prebuilt binaries.
8180

@@ -172,7 +171,7 @@ Then, select the .efi file using the file browser.
172171

173172
Next, select the usb device you would like to flash to.
174173

175-
174+
> :warning: **If you recieve Execution Errors** You might have to change your powershell execution policy. This can be done with the following comman in powershell: `Set-ExecutionPolicy Unrestricted `
176175
177176
### Example Steps (Linux)
178177

@@ -185,8 +184,7 @@ chmod +x make_boot_media.sh
185184
../make_boot_media.sh uxdbgapp.efi /dev/sdb
186185
```
187186

188-
##### if you recieve execution errors
189-
You might have to change your powershell execution policy. This can be done with the following comman in powershell: `Set-ExecutionPolicy Unrestricted `
187+
190188

191189
## Disclaimer
192190
IMPORTANT NOTICE: This software is sample software. It is not designed or intended for use in any medical, life-saving or life-sustaining systems, transportation systems, nuclear systems, or for any other mission-critical application in which the failure of the system could lead to critical injury or death. The software may not be fully tested and may contain bugs or errors; it may not be intended or suitable for commercial release. No regulatory approvals for the software have been obtained, and therefore software may not be certified for use in certain countries or environments.

0 commit comments

Comments
 (0)