gnupic: Re: [gnupic] gplink and .lst files
Subject:
Re: [gnupic] gplink and .lst files
From:
"George M. Gallant, Jr." ####@####.####
Date:
28 Mar 2006 03:21:15 +0100
Message-Id: <1143512400.12961.18.camel@scuba.home.net>
Craig,
I find 2 problems with the current scheme:
1. gpasm and gplink both produce xxx.lst files.
2. gplink deletes the xxx.lst file even if it is not writing one
itself.
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: ####@####.####
>
