Skip to content

Commit 3e61912

Browse files
authored
Merge branch 'ArmDeveloperEcosystem:main' into main
2 parents cae073f + f0cafd0 commit 3e61912

30 files changed

+874
-29
lines changed

.wordlist.txt

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -577,7 +577,6 @@ Pmod
577577
PostgerSQL
578578
PostgrSQL
579579
Postgres
580-
Powershell
581580
Prefetching
582581
Prereqs
583582
ProjectExplorer

assets/contributors.csv

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Rin Dobrescu,Arm,,,,
4343
Przemyslaw Wirkus,Arm,PrzemekWirkus,przemyslaw-wirkus-78b73352,,
4444
Nader Zouaoui,Day Devs,nader-zouaoui,nader-zouaoui,@zouaoui_nader,https://daydevs.com/
4545
Alaaeddine Chakroun,Day Devs,Alaaeddine-Chakroun,alaaeddine-chakroun,,https://daydevs.com/
46-
Koki Mitsunami,Arm,,,,
46+
Koki Mitsunami,Arm,,kmitsunami,,
4747
Chen Zhang,Zilliz,,,,
4848
Tianyu Li,Arm,,,,
4949
Georgios Mermigkis,VectorCamp,gMerm,georgios-mermigkis,,https://vectorcamp.gr/
19.1 KB
Loading
74.2 KB
Loading
17.9 KB
Loading
36.2 KB
Loading
20.6 KB
Loading

content/install-guides/git-woa.md

Lines changed: 103 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,103 @@
1+
---
2+
### Title the install tools article with the name of the tool to be installed
3+
### Include vendor name where appropriate
4+
title: Git for Windows on Arm
5+
6+
### Optional additional search terms (one per line) to assist in finding the article
7+
additional_search_terms:
8+
- git
9+
- windows
10+
- woa
11+
- windows on arm
12+
- open source windows on arm
13+
14+
### Estimated completion time in minutes (please use integer multiple of 5)
15+
minutes_to_complete: 10
16+
17+
### Link to official documentation
18+
official_docs: https://git-scm.com/doc
19+
20+
author_primary: Jason Andrews
21+
22+
### PAGE SETUP
23+
weight: 1 # Defines page ordering. Must be 1 for first (or only) page.
24+
tool_install: true # Set to true to be listed in main selection page, else false
25+
multi_install: false # Set to true if first page of multi-page article, else false
26+
multitool_install_part: false # Set to true if a sub-page of a multi-page article, else false
27+
layout: installtoolsall # DO NOT MODIFY. Always true for tool install articles
28+
---
29+
30+
Git has native support for [Windows on Arm](https://learn.microsoft.com/en-us/windows/arm/overview). Starting with version 2.47.1, an official installer is available.
31+
32+
In addition to Windows laptops, Windows on Arm instances are available with Microsoft Azure. For further information, see [Deploy a Windows on Arm virtual machine on Microsoft Azure](/learning-paths/cross-platform/woa_azure/).
33+
34+
## How do I download and install Git for Windows on Arm?
35+
36+
Git releases are available in [GitHub releases](https://github.com/git-for-windows/git/releases/).
37+
38+
Use a browser to download the desired release file. The Git releases for Windows on Arm have `arm64.exe` in the filename.
39+
40+
You can also download from a Windows PowerShell with the following command:
41+
42+
```command
43+
curl https://github.com/git-for-windows/git/releases/download/v2.47.1.windows.1/Git-2.47.1-arm64.exe -o Git-2.47.1-arm64.exe
44+
```
45+
46+
Once you have downloaded Git, run the installer `.exe` file on a Windows on Arm machine.
47+
48+
The installer starts.
49+
50+
Click Next to acknowledge the GNU General Public License.
51+
52+
Set the destination location or accept the default location and click Next.
53+
54+
Continue to click Next for any configuration settings. You can accept all defaults if you are unsure of specific settings.
55+
56+
At the end of the install process you see the screen below indicating setup has finished installing Git:
57+
58+
![Install](/install-guides/_images/git-woa.png)
59+
60+
Click the Finish button to complete installation.
61+
62+
## How do I use Git on Windows?
63+
64+
You can use Git on Windows from a Command Prompt or using Git Bash, a Linux-like terminal experience which includes Git and many other Linux commands.
65+
66+
{{% notice Note %}}
67+
Git is not automatically added to your search path during installation.
68+
{{% /notice %}}
69+
70+
To use Git, click the Windows Start button and then click `All apps`.
71+
72+
You see the Git folder in the G section.
73+
74+
![Start](/install-guides/_images/git2-woa.png)
75+
76+
There are menu items for multiple ways to start Git.
77+
78+
## How can I use Git in a Windows Command Prompt?
79+
80+
Start a Git Command Prompt by selecting `Git CMD` from the start menu.
81+
82+
![CMD](/install-guides/_images/git3-woa.png)
83+
84+
85+
To see the help message enter:
86+
87+
```cmd
88+
git help
89+
```
90+
91+
You can use Git from this Command Prompt.
92+
93+
## How can I use Git with Git Bash?
94+
95+
To use Git in a Linux-like environment, select `Git Bash` from the start menu.
96+
97+
![CMD](/install-guides/_images/git4-woa.png)
98+
99+
Click the colored icon on the top left corner of the Git Bash window and then click `Options` to change the appearance of the window, including colors, fonts, and font sizes.
100+
101+
![Options](/install-guides/_images/git5-woa.png)
102+
103+
You are now ready to use Git on your Windows on Arm device.

content/install-guides/windows-perf-wpa-plugin.md

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -31,17 +31,17 @@ layout: installtoolsall # DO NOT MODIFY. Always true for tool install articles
3131
The Windows Performance Analyzer (WPA) plugin connects [WindowsPerf](/learning-paths/laptops-and-desktops/windowsperf/) to the Windows Performance Analyzer. Windows Perf is a lightweight performance profiling tool inspired by Linux Perf and designed for Windows on Arm.
3232

3333
Windows Performance Analyzer provides developers with diagnostics and performance tuning. It generates data tables and graphs of Event Tracing for Windows (ETW) events, which are recorded in one of three ways:
34-
- Windows Performance Recorder (WPR)
35-
- Xperf
36-
- or through an assessment that's run in the Assessment Platform.
34+
- By using Windows Performance Recorder (WPR).
35+
- By using Xperf.
36+
- Through an assessment that is run in the Assessment Platform.
3737

38-
WPA can open event trace log (ETL) files, which you can use for analysis.
38+
WPA can open Event Trace Log (ETL) files, which you can use for analysis.
3939

40-
The WPA plugin is built using the [Microsoft Performance Toolkit SDK](https://github.com/microsoft/microsoft-performance-toolkit-sdk), a collection of tools to create and extend performance analysis applications. The plugin parses JSON output from Windows Perf so that it can be visualized in WPA.
40+
The WPA plugin is built using the [Microsoft Performance Toolkit SDK](https://github.com/microsoft/microsoft-performance-toolkit-sdk), which is a collection of tools to create and extend performance analysis applications. The plugin parses JSON output from Windows Perf so that it can be visualized in WPA.
4141

42-
## What are some of the features of the WPA plugin?
42+
## What are the features of the WPA plugin?
4343

44-
The WindowsPerf GUI extension includes features, which are designed to streamline the user experience:
44+
The WindowsPerf GUI extension includes features that are designed to streamline the user experience, and these are detailed below.
4545

4646
### Timeline view
4747

@@ -67,25 +67,25 @@ Open the Microsoft Store and search for "windows performance analyzer".
6767

6868
![WPA store](/install-guides/_images/wpa-store.png)
6969

70-
Hover over the card, and the "Free" button will become a "Get" button. Click the "Get" button to start installation.
70+
Hover over the card, and you will see that the **Free** button becomes a **Get** button. Click the **Get** button to start the installation.
7171

72-
Wait for WPA to be installed, and launch it from the Windows menu.
72+
Wait for WPA to be installed, and then launch it from the Windows menu.
7373

7474
![WPA installation #center](/install-guides/_images/wpa-installation.png)
7575

7676
{{% notice Note %}}
77-
The WPA plugin requires WPA version `11.0.7.2` or higher. You can check the version by clicking `Help` -> `About Windows Performance Analyzer`.
77+
The WPA plugin requires WPA version `11.0.7.2` or higher. You can check the version by clicking **Help** > **About Windows Performance Analyzer**.
7878
{{% /notice %}}
7979

8080
Close Windows Performance Analyzer.
8181

8282
### Install the WPA plugin
8383

84-
You are ready to install the WPA plugin, which is a single `.dll` file.
84+
You are now ready to install the WPA plugin, which is a single `.dll` file.
8585

8686
Download the `.zip` file from the [Windows Perf WPA plugin GitHub releases page](https://github.com/arm-developer-tools/windowsperf-wpa-plugin/releases) on GitHub.
8787

88-
Alternatively, you can download the `.zip` file from a Command Prompt:
88+
Alternatively, you can download the `.zip` file from a command prompt:
8989

9090
```console
9191
mkdir wpa-plugin
@@ -101,28 +101,28 @@ tar -xmf wpa-plugin-1.0.2.zip
101101

102102
The file `WPAPlugin.dll` is now in your `wpa-plugin` directory.
103103

104-
There are three ways you can use the `WPAPlugin.dll` file:
104+
There are three ways that you can use the `WPAPlugin.dll` file:
105105

106-
#### 1. Start WPA from the command line and pass the plugin directory location using a flag.
106+
##### Option 1: Start WPA from the command line and pass the plugin directory location using a flag.
107107

108108
Use the `-addsearchdir` flag to tell `wpa` where to find plugins.
109109

110-
For example, if you downloaded the DLL in your `Downloads` directory, you can run `wpa` as shown below:
110+
For example, if you downloaded the `.dll` in your `Downloads` directory, you can run `wpa` as shown below:
111111

112112
```bash
113113
wpa -addsearchdir %USERPROFILE%\Downloads\wpa-plugin-1.0.2
114114
```
115115
116-
#### 2. Set an environment variable.
116+
##### Option 2: Set an environment variable.
117117

118118
Set the `WPA_ADDITIONAL_SEARCH_DIRECTORIES` environment variable to the location of the `.dll` file.
119119

120-
#### 3. Copy the .dll file to the CustomDataSources directory next to the WPA executable.
120+
##### Option 3: Copy the `.dll` file to the `CustomDataSources` directory next to the WPA executable.
121121

122122
The default location is:
123123
`C:\\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\CustomDataSources`
124124

125-
## How can I verify the WPA plugin is installed?
125+
## How can I verify that the WPA plugin is installed?
126126

127127
To verify the plugin is loaded, launch WPA and the plugin should appear on the Installed Plugins list.
128128

@@ -132,12 +132,12 @@ To verify the plugin is loaded, launch WPA and the plugin should appear on the I
132132

133133
To open a JSON file directly from the command line, you can use the `-i` flag to specify the file path to open.
134134

135-
For example: to open `timeline_long.json` in your downloads directory, run the command:
135+
For example, to open `timeline_long.json` in your `downloads` directory, run the command:
136136

137137
```console
138138
wpa -addsearchdir %USERPROFILE%\Downloads\wpa-plugin-1.0.2 -i %USERPROFILE%\Downloads\timeline_long.json
139139
```
140140
## How do I uninstall the WPA plugin?
141141

142-
To uninstall the plugin simply delete the `WPAPlugin.dll` file.
142+
To uninstall the plugin, simply delete the `WPAPlugin.dll` file.
143143

content/learning-paths/laptops-and-desktops/llvm_putty/putty_llvm.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,9 +27,9 @@ You can use Clang to build a CMake application for Windows on Arm. The example a
2727

2828
To compile PuTTY on a Windows on Arm device, follow the steps outlined below:
2929

30-
1. Open `Windows Powershell` on your Windows on Arm computer.
30+
1. Open `Windows PowerShell` on your Windows on Arm computer.
3131

32-
Run the next two steps at the Powershell command prompt.
32+
Run the next two steps at the PowerShell command prompt.
3333

3434
2. Create a directory to use for the build and go to the directory:
3535

0 commit comments

Comments
 (0)