admin/ElliotKillick-windows-vs-linux-loader-architecture

mirror of https://github.com/ElliotKillick/windows-vs-linux-loader-architecture synced 2026-06-08 10:57:32 +00:00

Files

T

Elliot Killick 8f9257c1da A release

From June to now, most of my time on this project was spent writing
"The Rise of Microsoft". Researching and writing that thing took an
inordinate amount of time. Also, I took a break to work primarily on
another unreleased project I have before switching back to this one.

I am proud of what I got here though and I feel like it is all coming
together. My plans for the whitepapers are already well drafted and I
know they will make an impact.

I have learned a ton from working on this project and it has definitely
given me something to idly think about and work on in my spare time.

Finishing "The Problem with How Windows Uses Threads" was something I
thought I wanted done before this release, but oh well. The main README
is at about 50K words now, plus all the other smaller documents and you
are looking at about a small novel's worth of technical writing. And
technical writing takes multiple times longer than typical story
writing.

Anyway, this project is exciting for me - people who I show it to also
really like it - and I am even more excited about what is to come!

2025-11-30 23:00:08 -05:00

glibc

A release

2025-11-30 23:00:08 -05:00

windows

A release

2025-11-30 23:00:08 -05:00

README.md

Organize and update

2025-02-11 22:04:18 -05:00

README.md

Code Samples

Compiling & Running

These instructions are for building and running the code samples in this repo:

Compile
- Unix: Run make where there is a Makefile
- Windows: Run build.bat where this script exists
- For cross-platform Rust: cargo build
Pre-execution
- Unix: Run export LD_LIBRARY_PATH="$PWD" (set this varible to where the libraries are) so an application can its find libraries
- Windows: This system searches the program folder and current working directory by default (copy or move files if necessary, e.g. with the copy /y command)
- For cross-platform Rust: Not necessary when using cargo helpers
Run
- Unix: Run ./<PROGRAM> or gdb ./<PROGRAM> to debug
- Windows: Run <PROGRAM_NAME>.exe or pop it into WinDbg to debug
- For cross-platform Rust: cargo run

The steps are intentionally designed to be as simple and easy as possible to remove friction from experimentation, even on Windows, thanks to the succinct build.bat helper files I made to achieve parity with Unix systems.