Setting up "right" for g/as assembler and .s assembly files
Posted: Sun Feb 17, 2013 9:16 am
I mucked with the file types dialog box, hardcoding "as" and the "-gstabs" switch to turn on debug information. I got the project to build and link.
In the debuger, I could add watches for $eax and $ecx or go to the "output" tab and type in "info registers", although the output from "info registers" was kind of mucked up.
So my question/suggestion has multiple parts:
(1) How do I setup CodeLite "the right way" to elegantly handle the "as" (gas) assembler? How do I set the equivalents of $(CC), the include and switches and so on? I'm a newbie to this command chain and to CodeLite.
(2) Debugging works pretty well in terms of setting code breaks in assembler code, stepping and so on. But a purpose-driven "registers/memory" dialog during the debugging process would be a HUGE win for debugging assembly language code.
(3) My "ontology" of CodeLite things is not clear. Would "as" be another compiler? Or another "tool" under a given compiler? Or both? It's not clear how to distinguish these two concepts (can you have multiple "Compilers" per project or not?) And again, where/how does one configure all the environment variables, paths and switches and so on for these tools? A thorough tutorial on setting up a new tool and clearly laying out the internal "ontology" of CodeLite would be awesome.
(4) Um, "as" is a built in part of the gcc tool chain. I was pretty surprised that these files were not recognized and handled appropriately "out of the box" by CodeLite.
Thanks for any and all assistance!
- Scott
In the debuger, I could add watches for $eax and $ecx or go to the "output" tab and type in "info registers", although the output from "info registers" was kind of mucked up.
So my question/suggestion has multiple parts:
(1) How do I setup CodeLite "the right way" to elegantly handle the "as" (gas) assembler? How do I set the equivalents of $(CC), the include and switches and so on? I'm a newbie to this command chain and to CodeLite.
(2) Debugging works pretty well in terms of setting code breaks in assembler code, stepping and so on. But a purpose-driven "registers/memory" dialog during the debugging process would be a HUGE win for debugging assembly language code.
(3) My "ontology" of CodeLite things is not clear. Would "as" be another compiler? Or another "tool" under a given compiler? Or both? It's not clear how to distinguish these two concepts (can you have multiple "Compilers" per project or not?) And again, where/how does one configure all the environment variables, paths and switches and so on for these tools? A thorough tutorial on setting up a new tool and clearly laying out the internal "ontology" of CodeLite would be awesome.
(4) Um, "as" is a built in part of the gcc tool chain. I was pretty surprised that these files were not recognized and handled appropriately "out of the box" by CodeLite.
Thanks for any and all assistance!
- Scott