gnupic: Re: [gnupic] pikdev & gpsim interoperability


Previous by date: 28 Dec 2005 21:16:37 +0000 Re: [gnupic] pikdev & gpsim interoperability, Scott Dattalo
Next by date: 28 Dec 2005 21:16:37 +0000 gpsim weirdness, John De Villiers
Previous in thread: 28 Dec 2005 21:16:37 +0000 Re: [gnupic] pikdev & gpsim interoperability, Scott Dattalo
Next in thread: 28 Dec 2005 21:16:37 +0000 Re: [gnupic] pikdev & gpsim interoperability, John De Villiers

Subject: Re: [gnupic] pikdev & gpsim interoperability
From: John De Villiers ####@####.####
Date: 28 Dec 2005 21:16:37 +0000
Message-Id: <1135804577.4886.114.camel@bbj.inet>

Im with you on this. The file that gpsim was looing for was
.//home/devillj/rctank/lcd.asm

the extra ./ infront of the file is what bothered me.

If i do a strings of the cod file, it actually contains the full-path of
the asm file instead of just the filename.

On Wed, 2005-12-28 at 18:53, Scott Dattalo wrote:
> > hmmh, ok gpsim has an include search path it tries to use, but it looks
> > like it tries to find the full-pathname inside the search path, which
> > obviously wont work.
> 
> Hi John,
> 
> I just recently fixed a gpsim bug in this area. The problem was that if
> there was more than one absolute path in a .cod file and gpsim was started
> from within a directory different than where the .cod file was originally
> assembled, gpsim would fail to load the .cod file.
> 
> I agree that absolute paths in .cod files can cause problems. There are
> (at least) two ways around this. A) Don't move files around once they're
> assembled (inconvenient for the user). B) Invent a .cod file path scheme
> that uses OS environment variables to keep track of where .cod files may
> legally reside.
> 
> gpsim attempts the latter with the -L command line option:
> 
>   -L, --sourcepath=STRING      colon separated list of directories to
>                                search.
> 
> Now, I haven't used this feature in quite a while so there's a chance bit
> rot has crept in. But the intent is to provide a set of directories that
> gpsim can search to look for files. The logic goes something like this:
> for the first .cod file loaded, gpsim will search in the current directory
> (i.e. the one from which it was invoked). If it's not found then the colon
> delimited list of directories specified at the command line is searched.
> The first .cod file that matches is loaded. The .cod file contains
> absolute paths to other files. gpsim will first attempt to load these
> files at their absolute path. If this fails, then the file name is
> separated from its absolute path and searched for in the directories list.
> 
> Scott
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 
> 


Previous by date: 28 Dec 2005 21:16:37 +0000 Re: [gnupic] pikdev & gpsim interoperability, Scott Dattalo
Next by date: 28 Dec 2005 21:16:37 +0000 gpsim weirdness, John De Villiers
Previous in thread: 28 Dec 2005 21:16:37 +0000 Re: [gnupic] pikdev & gpsim interoperability, Scott Dattalo
Next in thread: 28 Dec 2005 21:16:37 +0000 Re: [gnupic] pikdev & gpsim interoperability, John De Villiers


Powered by ezmlm-browse 0.20.