It's for Windows, and assumes qemu is in your path. It's not a .sh or a makefile.
You can use actual build systems (makefile-based or not) in Windows as well. Even if your project is small enough that you don't care about rebuilding modules that haven't changed since the last build, why does your batch script do both building and emulation? I won't even get into implementation issues like the path hack.
Why do you upload files via GitHub's web interface instead of uploading them by syncing your git repo?
beacuse my git doesn't show you how to connect to your repo after the first time. and now i have to use the web interface.
's a good (free) introduction to version control. It covers several tools, including git, for some of the more common tasks. More advanced topics like submodules, resetting, rebasing, etc. are not covered but it's still a good starting point.
I'm working on a new version (i realized the loading IDT thing is not even valid, sorry, also adding more features, obviously.).
My point wasn't that you did a bad job and should try harder. My point was that you would do a better job effortlessly if just you took the time to find out the things you don't know: a few things about upstream prerequisites, design patterns, and the tools you're using and you'd be ready to actually
work on your projects.
As iansjack suggests, being self-reliant is one of the more important things about being an engineer. A little literacy and willingness is the difference between a script kiddie and a software engineer.