@@ -49,22 +49,6 @@ If you'd like to run unit and end-to-end tests, run the tests like you'd normall
49
49
$ zig build test
50
50
```
51
51
52
- ## Why did you decide to unarchive this repo?
53
-
54
- Excellent question! If you recall, back in March 2021, I've moved the development of the linker directly
55
- to upstream (Zig master), and since then, ` zld ` (or ` zig ld ` in fact) has been able to link a variety
56
- of projects targeting Mach-O file format. Now I am in the process of implementing a traditional ELF linker,
57
- so I've decided to repeat the process which in my humble opinion worked out pretty well for Mach-O. The idea
58
- is to start small by adding basic linking in a standalone repo (separate from Zig master), and when the linker
59
- matures enough, upstream it into Zig. I think this approach makes sense and allows me to focus on the target
60
- file format only rather than try and tackle both a new file format and challenges of incremental linking.
61
-
62
- Having said that, I've also decided to downstream all latest developments to the traditional Mach-O linker
63
- back into this repo, thus making ` zld ` a capable standalone linker when it comes to linking Mach-O. I'll strive
64
- to make it a direct replacement for any system linker, however, note that my priority will always be advancing
65
- of ` zig ld ` (which is not to say that I won't backport fixes from one to another). At the end of the day, the idea
66
- will be to swap in ` zig ld ` in place of any other linker.
67
-
68
52
## Supported backends
69
53
70
54
- [x] Mach-O (x86_64)
@@ -78,5 +62,4 @@ will be to swap in `zig ld` in place of any other linker.
78
62
79
63
## Contributing
80
64
81
- You are welcome to contribute to this repo, but ask you to see if you could also contribute the same fix
82
- to Zig too. This will make my life easier and you will have made many Zig developers happy!
65
+ You are welcome to contribute to this repo.
0 commit comments