Re: [sdcc-devel] object file extensions

[Maarten B. <sou...@ds...>]

Hi Sebastien,

It's not really SDCC that generates the object files, but the underlying
assembler. SDCC comes with a modified ASxxxx assembler and linker for most
targets, but the PIC ports use gpasm/gplink. ASxxxx uses the .rel
extension and gpasm uses .o. The rationale is that we did not write the
assemblers.

Maarten

> Hello,
>
> It seems that the object file extension varies according to the backend.
>
> PIC ports produce .o files, while (some of) the other backends produce
> .rel files.
> But which ones? What's the rationale behind this?
>
> I'd like to understand that to suggest better integration settings to the
> code::blocks IDE team.
>
> I made them change the "sdcc" settings to use ".o" files, but this was a
> mistake
> since some backends still use "rel". I guess per-CPU settings would be
> better.
>
> Regards
> Sebastien
>
> ------------------------------------------------------------------------------
> Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
> much more. Get web development skills now with LearnDevNow -
> 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122812
> _______________________________________________
> sdcc-devel mailing list
> sdc...@li...
> https://lists.sourceforge.net/lists/listinfo/sdcc-devel
>