-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.txt
77 lines (49 loc) · 2.09 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
GNAT Community
--------------
This contains the GNAT Community edition.
The packages for the native platforms (for Linux, Mac and Windows) contain
- the GNAT compiler toolchain
- the SPARK Ada verification and prover toolset
- the GNAT Programming Studio IDE
The packages for the embedded platforms (ARM and RISC-V) only contain the
GNAT compiler toolchain for that target, so we recommend installing the
native package as well.
Installing
----------
On Windows:
Simply run the .exe and follow the instructions.
On Linux:
You will need to make the package executable before running it. In a command
prompt, do
chmod +x path_to_the_package-bin
then execute the package.
On Mac:
Open the .dmg, and click on the .app contained therein.
On recent versions of Mac OS, you will need to first click on this .app,
then go to the "Security & Privacy" section of the System Preferences,
and allow the run to continue there.
Automated installation
----------------------
If you need to automate the install of these packages, you can use the scripts
provided at:
https://github.com/AdaCore/gnat_community_install_script
Using
-----
To start using the tools in command-line mode, you will need to add
<install_prefix>/bin
to your PATH environment variable. Alternatively, you can simply launch
<install_prefix>/bin/gps
and GPS will automatically add itself to the PATH - it will also find the
cross compiler, if you have installed everything in the default locations.
Note that GPS will add this at the *end* of the PATH, meaning that it will
find first any other GNAT installations that you have in your PATH.
Platform-specific notes
-----------------------
To flash boards (such as the BBC micro:bit board) using the pyocd integration
in GPS under Linux, you might need privileges to access the USB ports, without
which the flash program will say "No connected boards".
To do this on Ubuntu, you can do it by creating (as administrator) the file
/etc/udev/rules.d/mbed.rules and add the line:
SUBSYSTEM=="usb",MODE:="666"
then restarting the service by doing
sudo udevadm trigger