Compile on Linux please!

[audiocommander]

But that means i can not compile MB applications whith gpasm right at the moment. (either v.0.13.3 nor v.0.13.4) or is it possible to write a sed file which does the same as it does with MIOS files?

To be honest, I don't know what that means ;)

...because when I compile my C-based programs with SDCC this happens:

-> C -> SDCC -> ASM -> GPASM -> HEX -> SYX

everything works fine.

But when I try this:

-> ASM -> GPASM -> HEX

the resulting hex file is wrong.

I haven't had time to interspect this further, but AFAIR there were other reports where ASM-sources weren't compiled correctly.

I can only assume that I simply forgot to send some parameters to GPASM or something has to be tweaked somewhere... you're welcome to test it!

I recommend, that you load an ASM-based source (like the seq-app) and backup the pregenerated included hex file. Then try to compile the project unchanged. When you compare your fresh compiled .hex file against the backuped original .hex-file, there should be no differences.

If there's a difference you might take a look at a C-based MIOS-App Makefile (eg. the 128 I/O test application) how GPASM is called when the process is started automatically.

I hope this points you towards the right direction.

If you have success, I'd be happy for a report :)

Best regards,

Michael

sorry, admin ;D

(maybe someone could split up this topic to a new one "Compile on OSX please!" )?

[chriss]

hi michael

I recommend, that you load an ASM-based source (like the seq-app) and backup the pregenerated included hex file. Then try to compile the project unchanged. When you compare your fresh compiled .hex file against the backuped original .hex-file, there should be no differences.

thats exactly what i did on the last weekend, not only that the the hex file was different it was gone... and i got two files called "main.lst" and "main.cod". And i had this errors in the terminal described at the beginning of this thread.

aout.inc:61:Error [103] syntax error

aout.inc:72:Error [103] syntax error

aout.inc:155:Error [103] syntax error

aout.inc:157:Error [103] syntax error

aout.inc:183:Error [103] syntax error

aout.inc:228:Error [103] syntax error

aout.inc:239:Error [103] syntax error

aout.inc:249:Error [103] syntax error

cs_menu_timer.inc:27:Error [103] syntax error

cs_menu.inc:57:Error [103] syntax error

cs_menu.inc:65:Error [103] syntax error

cs_menu.inc:75:Error [103] syntax error

cs_menu.inc:106:Error [103] syntax error

cs_menu.inc:147:Error [103] syntax error

cs_menu.inc:178:Error [103] syntax error

cs_menu.inc:193:Error [103] syntax error

cs_menu.inc:309:Error [103] syntax error

cs_menu.inc:357:Error [103] syntax error

cs_menu.inc:415:Error [103] syntax error

cs_menu.inc:443:Error [103] syntax error

cs_menu.inc:641:Error [103] syntax error

cs_menu.inc:660:Error [103] syntax error

cs_menu.inc:669:Error [103] syntax error

cs_menu.inc:672:Error [103] syntax error

cs_menu.inc:717:Error [103] syntax error and so on ....

the problem i have is that i don´t have a C file nor a C application, instead i want to compile a plain MB asm file with gpasm.

otherwise i have to wait till i get a macbook to use mplab again  :'(

so the new thread should better call "compile MB application assembler files on OSX please"

again thanks for your help

chriss

[audiocommander]

Hi Chris,

this is a MACRO-problem indeed solveable with the mentioned MIOS-fix.

http://www.midibox.org/dokuwiki/doku.php?id=compiling_the_midibox_source_on_linux

because the first error message is:

macros.h:91:Error [151] Operand contains unresolvable labels or is too complex.

sorry, wasn't aware of that  :-[

I'm not sure if macros.h is interchangeable with macros.sed... I'm totally overasked when it comes to ASM...

but I'm not sure if it works even if you fix the macros.

You should definitely check the generated .hex against the original one, if you succeed in fixing the Macro's.

Anyway, it's worth to give it a try  :)

btw. it's totally normal that the hex file is removed before compiling a new one.

the other files you noticed are temporary generated output files.

best regards,

Michael

[chriss]

hi michael

thanks a lot for your input,

I'm not sure if macros.h is interchangeable with macros.sed... I'm totally overasked when it comes to ASM..

and i am when it comes to programing language.

when there is actually no such makros.sed file than it´s ok. i just wanted to be sure that i am not doing something wrong in the teminal or with my directions.

thanks again

chriss