FreeDOS support
Re: FreeDOS support
If you can polish that into clean patches, we'd be glad to merge them into mainline.
Awesome MicroPython list
Pycopy - A better MicroPython https://github.com/pfalcon/micropython
MicroPython standard library for all ports and forks - https://github.com/pfalcon/micropython-lib
More up to date docs - http://pycopy.readthedocs.io/
Pycopy - A better MicroPython https://github.com/pfalcon/micropython
MicroPython standard library for all ports and forks - https://github.com/pfalcon/micropython-lib
More up to date docs - http://pycopy.readthedocs.io/
Re: FreeDOS support
Great! You made it. Will test asap.
Re: FreeDOS support
Do you mean pull request? How to be with binaries? Also, makefile copied from unix build, but, I think, it's dirty for FreeDos with unused parts and can be stripped. But I have no experience with makefiles at all And some *.c files (maybe another ones too) are not used, I think.pfalcon wrote:If you can polish that into clean patches, we'd be glad to merge them into mainline.
Awesome, feedback is what we need here, since it tested only with one board and dosbox.josie87 wrote:Will test asap
Re: FreeDOS support
Yes.pohmelie wrote:Do you mean pull request?pfalcon wrote:If you can polish that into clean patches, we'd be glad to merge them into mainline.
The simplest answer - in no way. Users who need it, can build it themselves. There's also ticket to provide binaries in "official" way: https://github.com/micropython/micropython/issues/1295 , but it likely will take a lot of time to get that done. You of course can provide binaries yourself, at your, and your users risk.How to be with binaries?
So, ideal solution would be to just use existing unix makefile and port directory (and just apply as few as possible #ifdef's to support DJGPP). If that's not possible, then having a top-level directory with minimal set of files, like for Windows, would work too.Also, makefile copied from unix build, but, I think, it's dirty for FreeDos with unused parts and can be stripped. But I have no experience with makefiles at all And some *.c files (maybe another ones too) are not used, I think.
Awesome MicroPython list
Pycopy - A better MicroPython https://github.com/pfalcon/micropython
MicroPython standard library for all ports and forks - https://github.com/pfalcon/micropython-lib
More up to date docs - http://pycopy.readthedocs.io/
Pycopy - A better MicroPython https://github.com/pfalcon/micropython
MicroPython standard library for all ports and forks - https://github.com/pfalcon/micropython-lib
More up to date docs - http://pycopy.readthedocs.io/
Re: FreeDOS support
I'd be more than happy to help you with any makefile stuff that's needed.
Re: FreeDOS support
Are you sure this is the best solution? Cause I think, that FreeDos have very little with unix build, not about Makefile difference, but… this is very different operating systems. I think more, than win and unix are. Also, FreeDos build requires proper environment variables, so there should be readme/guide, something like in my repo right now. So it's not just easy as "make freedos".pfalcon wrote:ideal solution would be to just use existing unix makefile and port directory
Awesome, I will try to minimize port and will post progress here, so you can review it.dhylands wrote:I'd be more than happy to help you with any makefile stuff that's needed.
Re: FreeDOS support
In terms of reviewing things, the best (for me) would be to put the changes on a github branch and post a link to your branch.pohmelie wrote:Awesome, I will try to minimize port and will post progress here, so you can review it.dhylands wrote:I'd be more than happy to help you with any makefile stuff that's needed.
Re: FreeDOS support
dhylands
Of course, I need time to try minimize repo.
Of course, I need time to try minimize repo.
Re: FreeDOS support
dhylands
I'm done with minimizing as I can. I think you can review it now https://github.com/pohmelie/micropython ... er/freedos
There is some «trick» to avoid alloca.h, for example. I use -D__FreeBSD__=5 cause -DMICROPY_NO_ALLOCA=1 does not work. Hm, but probably we can just remove those #if #else #end and just #include <stdlib.h> at the end of mpconfigport.h.
I'm done with minimizing as I can. I think you can review it now https://github.com/pohmelie/micropython ... er/freedos
There is some «trick» to avoid alloca.h, for example. I use -D__FreeBSD__=5 cause -DMICROPY_NO_ALLOCA=1 does not work. Hm, but probably we can just remove those #if #else #end and just #include <stdlib.h> at the end of mpconfigport.h.
Re: FreeDOS support
Followed the instructions so far. DJGPP builds without errors.
Getting an error while building the Freedos port:
screenshot:
Getting an error while building the Freedos port:
Used this env setting:/home/johannes/djgpp/lib/gcc/i586-pc-msdosdjgpp/4.9.3/include/stddef.h:56:24: fatal error: sys/_types.h: No such file or directory
#include <sys/_types.h>
^
compilation terminated.
Code: Select all
export CROSS_COMPILE=/home/johannes/djgpp/i586-pc-msdosdjgpp/bin/
export DJGPP_GCC=/home/johannes/djgpp/bin/i586-pc-msdosdjgpp-gcc
make