FreeDOS support

[pohmelie]

Code: Select all

#define MICROPY_NLR_SETJMP (1)

Yeah, I have tried this before, but it looks like djgpp can't preprocess(?) *.S files, since errors are same and irrelevant to value of MICROPY_NLR_SETJMP. So I have just comment this file.
After two hours I successfully built micropython for dos, and test it on my board with AMD Geode and last FreeDos. On a way to build this I have found some «errors» in master of micropython (e.g. different types of arguments in header and source). I will summarize they later and post here, maybe some of them is just my bad understanding. Also there is some issue with build-djgpp(?) since there two directories with djgpp binaries: one contain long names, another short. Second one does not include all binaries (e.g. size) so this should be fixed or I missed something again.
Anyway, build is done and it is time to extend it via dos-specific modules, so where can I read about micropython objects and functions for c↔python bridge? Or source files is enough to realize?
By the way, it looks like there is only "sys" module. How to check what I have?
Hm, can't attach file since it is too large (317Kb-zipped)

[dhylands]

You can play games in the makefile too. Like this: https://github.com/dhylands/micropython ... kefile#L14

[pfalcon]

I will summarize they later and post here, maybe some of them is just my bad understanding.

At https://github.com/micropython/micropython/issues please.

Also there is some issue with build-djgpp(?) since there two directories with djgpp binaries: one contain long names, another short. Second one does not include all binaries (e.g. size) so this should be fixed or I missed something again.

It's not clear what you mean. Please mind that any computer system consist of multiple components, for each of which a different party is responsible. We'll be happy to make any reasonable changes to make MicroPython easily buildable with djgpp, but any djgpp issues you would need to report to djgpp project. (FreeDOS issues to FreeDOS, etc.)

Or source files is enough to realize?

Yes, the source is the best reference. You can also search/read this forum, as various aspects were discussed/answered here. But that likely will take you more time than reading source directly, while still
risking that information will be outdated. Reading the source frees from all the issues - you see directly what it is and how it works, it's up to date, etc. And yep, if you read the forum, you'll find people generally praise source quality of uPy, so it of course take you couple of days to figure out it all, but after half an hour of looking you'll know something already.

[pohmelie]

You can play games in the makefile too. Like this: https://github.com/dhylands/micropython ... kefile#L14

This does not work, also I found that MICROPY_NLR_SETJMP in mpconfigport.h does not affect on make of nlrx86.S at all. It looks like nothing from mpconfigport.h is defined when preprocessing nlrx86.S. But __i386__ looks defined. Maybe this is djgpp issue.

At https://github.com/micropython/micropython/issues please.

Done https://github.com/micropython/micropython/issues/1647

It's not clear what you mean.

Of course it's djgpp issue, I've already create https://github.com/andrewwutw/build-djgpp/issues/10 right after posting my previous post.

Little changes to core files, so micropython can be compiled with djgpp:
1. Comment content of nlrx86.S
2. Comment in modmath.c:
131: MATH_FUN_1(gamma, tgamma)
235: { MP_OBJ_NEW_QSTR(MP_QSTR_gamma), (mp_obj_t)&mp_math_gamma_obj },
It looks like there is no tgamma in djgpp std lib.
3. asmx86.c and asmx86.h like here https://github.com/micropython/micropython/issues/1647
Use attached crapy-magic freedos folder

[dhylands]

You can play games in the makefile too. Like this: https://github.com/dhylands/micropython ... kefile#L14

This does not work

OK - it works fine for me. Maybe you've got a typo or you put it in the wrong place in the Makefile?

also I found that MICROPY_NLR_SETJMP in mpconfigport.h does not affect on make of nlrx86.S at all. It looks like nothing from mpconfigport.h is defined when preprocessing nlrx86.S. But __i386__ looks defined. Maybe this is djgpp issue.

Looking at this again, I think that you need to add -DMICROPY_NLR_SETJMP to CFLAGS and not mpconfigport.h

[pohmelie]

Looking at this again, I think that you need to add -DMICROPY_NLR_SETJMP to CFLAGS and not mpconfigport.h

Yeah, adding of "CFLAGS_MOD += -DMICROPY_FREEDOS=1" to the Makefile and "#if !defined(MICROPY_FREEDOS) || !MICROPY_FREEDOS" to nlrx86.S solved the problem.

OK - it works fine for me. Maybe you've got a typo or you put it in the wrong place in the Makefile?

Hm, I've just copy your string "PY_O_BASENAME := $(filter-out nlr%, $(PY_O_BASENAME)) nlrsetjmp.o"

[pohmelie]

Oh, I was too fast and did it wrong, of course I should insert "-DMICROPY_NLR_SETJMP" and no changes to nlrx86.S

added:
Yeah, it works fine, so two left: tgamma and asmx86.c/asmx86.h difference

[dhylands]

Perhaps add

Code: Select all

$(info PY_O_BASENAME = $(PY_O_BASENAME))

before and after the line and see what it did.

What version of make are you using?

Doh - no the problem is that it needs to be after the include of py.mk (which is where PY_O_BASENAME is setup)

[pohmelie]

dhylands
It does not matter, since "-DMICROPY_NLR_SETJMP" do the job.

[pohmelie]

Finally made FreeDos port without changes to micropython core.
https://github.com/pohmelie/micropython-freedos