Re: [Sdcc-user] Re: pic port and "#FILE" line in .asm

[Vangelis R. <vr...@ot...>]

----- Original Message ----- 
From: "D Hawkins" <ill...@sl...>
To: <sdc...@li...>
Subject: [Sdcc-user] Re: pic port and "#FILE" line in .asm


> Yes, I'm amazed by what Vangelis is doing (big thanks, again).  I'd like
> to help, but I feel like I'd be a hindrance at the current speed I could
> contribute.

Everyone can contribute, even by sending reports even for minor things.
Currently, the reports come from only two persons, so its easy to keep
up, but if things go tougher it will be better to utilise the SF bug
tracker.

> >>I asked Vangelis to add the code to generate the "#FILE" line in the
> >>assembly and change the "#CSRC" lines to "#LINE" to be compatible with
> >>gplink.  This will generate source level COFF-files, which can be used
> >>in MPLAB's IDE, allowing 'C'-code single-stepping/debugging (for those

One thing to make clear here. Currently SDCC emits in the #FILE directive
the
path to the source (relative to the directory from which SDCC is called).
That is, if I run sdcc from directory  c:\foo and the source is in directory
c:\foo\src

sdcc src\boo.c

the #FILE directive will contain "src\boo.c".

What you ask for is to contain the full "c:\foo\src\boo.c" ?

I don't think this is the right thing to do. Is it definete that MPLAB won't
cooperatate with current behaviour? Even if you move the sources to
another directory (more MPLAB friendly?!)

Regards,
Vangelis