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: README.md
+20-20Lines changed: 20 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,12 @@
1
1
# Docker GBA Complier
2
2
Windows people have had a particularly rough time getting up and running with GBA development.
3
3
Since installing cygwin + devkitPro, updating system paths, and updating the Makefile to match
4
-
has proven difficult time and time again, this Dockerfile + Makefile represents an attempt to
5
-
unify things cross-platform in a less brittle way.
4
+
has proven difficult time and time again, this Dockerfile (+ default Makefile) represents an
5
+
attempt to unify things cross-platform in a less brittle way.
6
+
7
+
If you're using the latest version, note that the `gcc` version included in the 1.3+ container
8
+
is significantly stricter than the older version. `-fpermissive` and similar options may need
9
+
to be added to the `CFLAGS` definition in your fork of the example Makefile.
6
10
7
11
## Requirements
8
12
Docker for Desktop: https://www.docker.com/products/docker-desktop/
@@ -11,65 +15,61 @@ Note: Even if you can't get Docker running locally, I now have instructions for
11
15
12
16
13
17
## Building your own Docker Container (not required)
14
-
Ths following `docker build` command is only required if you plan to create your own version of this docker container. The one in this repo is available on Docker Hub as aaaronic/gba-compiler:1.2.
18
+
Ths following `docker build` command is only required if you plan to create your own version of this docker container. The one in this repo is available on Docker Hub as `aaaronic/gba-compiler:1.3`.
15
19
16
20
Once docker is installed, you could choose to do a one-time build of the Dockerfile on your machine (*from the folder containing the `Dockerfile`*):
17
21
18
22
```
19
23
docker build . -t gba-compiler
20
24
```
21
25
A few minutes later, you should have a docker image named gba-compiler that you should not
22
-
need to rebuild (hopefully ever again). It might spend a long time on the "Generating pacman
23
-
keyring master key..." step).
26
+
need to rebuild (hopefully ever again).
24
27
25
28
## Running a GBA project build (aka, compiling your GBA project)
26
-
1. The provided Makefile needs to be in your GBA project's directory (next to all your `.h` and
27
-
`.c` files).
28
-
- You should (hopefully) not need to change much about the Makefile aside from the
29
-
`PRODUCT_NAME` line. It defaults to "Project", which leads to your resulting `.gba` file
30
-
being named `Project.gba`. Feel free to change it to anything _without spaces or special characters_ (ex: "BouncingBox"). You can always rename the resulting file after the compilation instead.
31
-
29
+
1. Run from your GBA project's directory (with all your `.h` and `.c` files).i
30
+
- You can optionally provide your own Makefile (ideally based on the one in this repo)
32
31
2. Run the docker image we built above with the following special sauce:
33
32
34
33
```
35
-
docker run --rm -it -v ${PWD}:/gba aaaronic/gba-compiler:1.2
34
+
docker run --rm -it -v ${PWD}:/gba aaaronic/gba-compiler:1.3
36
35
```
37
36
or, alternatively (if you chose to do your own `docker build` locally):
38
37
```
39
38
docker run --rm -it -v ${PWD}:/gba gba-compiler
40
39
```
41
40
42
-
If the compilation succeeded, you should now see a `Project.gba` (or whatever you renamed it
43
-
to) in your project's folder.
41
+
If the compilation succeeded, you should now see a `my_project.gba` (or whatever you renamed it
42
+
to) in your non-default Makefile.
44
43
45
44
## Setting it and forgetting it for a project in Visual Studio Code
46
45
Copy the included `.vscode` folder (containing `tasks.json`) into your project folder.
47
-
Update `tasks.json`'s "build" command to point to your visualboyadvance-m installation:
46
+
Update `tasks.json`'s "build" command to point to your mGBA installation:
0 commit comments