gnupic: Re: [gnupic] gplink and .lst files
Subject:
Re: [gnupic] gplink and .lst files
From:
Craig Franklin ####@####.####
Date:
28 Mar 2006 02:50:12 +0100
Message-Id: <442896ED.6020104@users.sourceforge.net>
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
>
>
>
>
