![]() You need to replace the tasmbox.bat and tlinkbox.bat files with direct calls to these tools (the batch files are only creating a dosbox-config on the fly, run the dos executable with the give parameter - thats it ![]() I am trying to do the whole thing inside a single DOSBox, like I would do it in pure DOS, since outside, I have a GNU/Linux OS. Try to add a DEBUG flag or something to have a DEBUG or RELEASE build - same like the /DTARGET=original need to stop calling it "Bits", ASAP - its "Bytes" - there is no need to go the Bit-Level (1 Byte = 8 Bits) for explain Daniël, I managed to compile all OBJ files out of the ASM files in the asmorig directory however, I'm not certain on the best way to link this. Quotecall tlinkbox /s /P- /v /js:\tools\lib\ /v parameter of tlink.exe is the counter-part to TASMs /zi - both are needed to get debug infoĪnd please ALL: try Turbo Debugger - its way more easy then Dosbox Debugger etc.ĭon't throw that stuff away - its needed for easier development So: there is much to see/understand in this repo - and its easy to not see what helps alotĬode Select Expand ASM = tasmbox /m2 /s /zi That cycle is dead not using IDA - its ok, but not the best Port stuff to C or check behavior in Debugger to understand der Asm-Code better Replace with something else - is just a huge recurrung process and also the making diassemblery build out of the box with TASM is done using IDA scripts - orĮlse these 2MB of asm would just spit out hundreds of errorsĤ. Impractiable reachable without having such a toolįor example: the porting overview html and the functions replace with Ported C code in the asm code is completely done on the fly using a IDA script - hard to The asm code is still not 100% analysed, it assembles but its not fully described - adding notes to the IDA database will automaticlyĮxtend other parts of the code if IDA is able to detect dependencies - that is totaly missing when not using IDA, a C port on this level is nearly Unclear for non-IDA users why it is that good codeįor users that own an IDA License analysing in IDA and using the scripts and functions lurking around are of big help - but its completely so just believe this all had its reasons, and makefiles are your daily business if working as a software developer with C/C++. To build all the variants), there are even pure C or SDL based builds possible - to manage that all with some batch-files or manually is not a good idea ![]() ![]() To check if the C port behaves identical and using makefiles makes it not super easy for starters but makes it a fully automatic process The complexity of the build system is a tribute to the 16Bit/dosbox/win/linux base and testability (you will always inter-test different version builds ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |