- C 66.1%
- Assembly 29.7%
- RenderScript 1.8%
- Makefile 1.2%
- HTML 0.4%
- Other 0.5%
26645ce909
Some modules weren't built / copied over. This partially addresses the bullet point in #351: it's not that copy_ct60_usb_modules() uses ${TARGET} is wrong but it is the other way around: functions like copy_tt_modules() shouldn't hardcode their paths but sometimes we not always take the ${TARGET} CPU but a custom one (e.g. 030 for riebltt, 060 for ethernat etc). And on top of that, XIF modules do not have any debug targets at all. Currently different CPUs are used for: riebltt.xif (in copy_tt_modules; 030 instead of 02060) ethernat.xif+svethlan.xif (in copy_ct60_modules; 060 instead of 02060) blitz_st.ucd (in copy_blitz_usb_modules; mst instead of $TARGET) blitz030.ucd (in copy_blitz_usb_modules; 030 instead of $TARGET) copy_ct60_usb_modules & copy_aranym_usb_modules explicitly specify "060" and "040" respectively. Maybe we should build all modules for the same CPU. Or at least use .compile_${TARGET} instead of hardcoded .compile_<CPU> paths. Partially resolves #351. |
||
|---|---|---|
| .github/workflows | ||
| .scripts | ||
| doc | ||
| fonts | ||
| shared | ||
| sys | ||
| tools | ||
| xaaes | ||
| .gitignore | ||
| .travis.yml | ||
| BINFILES | ||
| BUGS | ||
| CONFIGVARS | ||
| COPYING | ||
| COPYING.GPL | ||
| COPYING.LGPL | ||
| COPYING.MiNT | ||
| docs | ||
| EXTRAFILES | ||
| HACKING | ||
| Makefile | ||
| MISCFILES | ||
| mkinstalldirs | ||
| PHONY | ||
| README.md | ||
| RULES | ||
| SRCFILES | ||
Bootable builds: Download Per CPU builds: Download TOS USB drivers: Download
This is FreeMiNT. Please see the file COPYING for licensing conditions. Please send electronic mail to freemint-discuss@lists.sourceforge.net for further information as well as concerning the kernel development subjects.
If you have a more generic question or you would like to simply reach as many users as possible, feel free to use FreeMiNT support section on Atari Forum.
All the documentation is located in the doc/ subdir.
FreeMiNT development has been community-driven without a dedicated maintainer since 2016. Contributors for all subsystems are welcome, be it for bugfixing, adding new features, improving documentation or testing.
Please note that if your file system doesn't support long filenames some of the files could have unpacked with truncated names.