gnupic: Re: [gnupic] gplink and .lst files
Subject:
Re: [gnupic] gplink and .lst files
From:
Craig Franklin ####@####.####
Date:
28 Mar 2006 03:52:48 +0100
Message-Id: <4428A631.9010406@users.sourceforge.net>
George M. Gallant, Jr. wrote:
>Craig,
>
>I find 2 problems with the current scheme:
>
> 1. gpasm and gplink both produce xxx.lst files.
>
>
They also both generate .hex and .cod files.
> 2. gplink deletes the xxx.lst file even if it is not writing one
>itself.
>
>
gpasm deletes xxx.lst files even if it is not writing one too.
Here is the problem with your scheme: I compile my project with the
list file enabled. Then later suppress the list file output and keep
building the project. The list file won't match any of the current
outputs. This is confusing at a minimum.
If you want to keep a file, whether it is a hex, cod, list,... rename it
or move it. Why do you want to keep a list file that doesn't match any
of the other outputs?
>George
>
>On Mon, 2006-03-27 at 19:52 -0600, Craig Franklin wrote:
>
>
>
>>The current behavior is to prevent old stale list files from being
>>confused with current hex files. All the gputils tools behave this way
>>for all file types.
>>
>>Best thing to do is to rename your file. This will also help prevent
>>gputils from over writing your special list file.
>>
>>George M. Gallant, Jr. wrote:
>>
>>
>>
>>>I typically use the -l option to gplink to inhibit the creation of the
>>>composite .lst file.
>>>A side effect is gplink deletes the existing .lst file. Moving the the
>>>code at approx
>>>lines 267-268 264 makes seems to correct this behavior.
>>>
>>>New code:
>>>
>>>void write_lst(void) {
>>> gp_symbol_type *symbol = state.object->symbols;
>>> gp_aux_type *aux;
>>> gp_boolean first_time = true;
>>>
>>> if(!state.lst.enabled)
>>> return;
>>>
>>> lst_init();
>>>
>>> list_enabled = true;
>>>
>>>Thanks,
>>> George
>>>
>>>
>>>
>>>
>>>
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: ####@####.####
>>For additional commands, e-mail: ####@####.####
>>
>>
>>
>
>
>
