From 3dff4e16d00b3ff43cc616bffa22b38d8fe08da9 Mon Sep 17 00:00:00 2001 From: hachem Date: Fri, 18 Sep 2026 19:41:12 +0200 Subject: chore: update README --- README.md | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index 5473379..b064a36 100644 --- a/README.md +++ b/README.md @@ -1,28 +1,28 @@ # aoc -My [AoC](https://adventofcode.com) solutions, written in x64 assembly. There is absolutely no good reason to pick assembly for this. I could have gone with C, C++, Rust, or pretty much anything else, but where's the fun in that? I'm doing this because I was bored, needed a reason to procrastinate, and, in any case, I don't have that many excuses to write assembly these days anymore, so these let me stay up to spec. Since assembly is beyond annoying to deal with between machines, I provide a Dockerfile with all the tools you might need to build and run the solutions. +my [aoc](https://adventofcode.com) solutions, written in x64 assembly. there is absolutely no good reason to pick assembly for this. i could have gone with c, c++, rust, or pretty much anything else, but where's the fun in that? i'm doing this because i was bored, needed a reason to procrastinate, and, in any case, i don't have that many excuses to write assembly these days anymore, so these let me stay up to spec. since assembly is beyond annoying to deal with between machines, i provide a dockerfile with all the tools you might need to build and run the solutions. -I don't particularly care about the AoC leaderboard. December is usually a pretty busy time for me, so I often don't have the time (or energy) to sit down and solve every puzzle on the day it comes out. As a result, some solutions may be uploaded days, weeks, or potentially much later than the actual puzzle release. That's intentional. I'm doing these primarily because I enjoy solving the problems and because they're a fun excuse to write increasingly questionable amounts of assembly. Getting a good leaderboard position isn't really the point for me. If a solution appears suspiciously late, that's probably why. +i don't particularly care about the aoc leaderboard. december is usually a pretty busy time for me, so i often don't have the time (or energy) to sit down and solve every puzzle on the day it comes out. as a result, some solutions may be uploaded days, weeks, or potentially much later than the actual puzzle release. that's intentional. i'm doing these primarily because i enjoy solving the problems and because they're a fun excuse to write increasingly questionable amounts of assembly. getting a good leaderboard position isn't really the point for me. if a solution appears suspiciously late, that's probably why. -AoC gives each user their own puzzle input. I keep my inputs locally and do not commit them to this repository. If you're running these solutions yourself, you'll need to provide your own inputs in whatever format the corresponding solution expects. +aoc gives each user their own puzzle input. i keep my inputs locally and do not commit them to this repository. if you're running these solutions yourself, you'll need to provide your own inputs in whatever format the corresponding solution expects. -## Docker -The solutions are Linux x64 ELF binaries, so they don't run natively on macOS or Windows. The image bundles `nasm`, `ld`, and `make`. +## docker +the solutions are linux x64 elf binaries, so they don't run natively on macos or windows. the image bundles `nasm`, `ld`, and `make`. -Since the solutions target x86-64, the container should be run as `linux/amd64`. On Apple Silicon, Docker will run it under emulation. +since the solutions target x86-64, the container should be run as `linux/amd64`. on apple silicon, docker will run it under emulation. -Build the image from the repository root: +build the image from the repository root: ```sh docker build --platform=linux/amd64 -t aoc . ``` -List the available days: +list the available days: ```sh docker run --platform=linux/amd64 --rm aoc list ``` -AoC inputs are per-user and are not committed to this repo. Put your input for a given day at `input/dayN.txt` in the repository root, then mount that directory when running so the solution can read it: +aoc inputs are per-user and are not committed to this repo. put your input for a given day at `input/dayN.txt` in the repository root, then mount that directory when running so the solution can read it: ```sh docker run --platform=linux/amd64 --rm \ @@ -30,18 +30,18 @@ docker run --platform=linux/amd64 --rm \ aoc run DAY=5 ``` -Assemble and link every day without running it — a quick build check that needs no input: +assemble and link every day without running it — a quick build check that needs no input: ```sh docker run --platform=linux/amd64 --rm aoc all ``` -When you're done, remove the image with: +when you're done, remove the image with: ```sh docker rmi aoc ``` -## License -[MIT](LICENSE), because if you actually want to use this code, you clearly need more help than permission. +## license +[mit](LICENSE), because if you actually want to use this code, you clearly need more help than permission. -- cgit v1.3