gnupic: Re: [gnupic] Path problems....


Previous by date: 3 Jul 2009 06:19:31 -0000 Re: [gnupic] Path problems...., Noel Henson
Next by date: 3 Jul 2009 06:19:31 -0000 Re: [gnupic] Path problems...., Tamas Rudnai
Previous in thread: 3 Jul 2009 06:19:31 -0000 Re: [gnupic] Path problems...., Noel Henson
Next in thread: 3 Jul 2009 06:19:31 -0000 Re: [gnupic] Path problems...., Tamas Rudnai

Subject: Re: [gnupic] Path problems....
From: Julen Gutierrez ####@####.####
Date: 3 Jul 2009 06:19:31 -0000
Message-Id: <9b88da5f0907022319vcfe3c15m193776151167c871@mail.gmail.com>

I try to use -c option and gpasm doesnt create the HEX file, just .o file.

2009/7/2 Noel Henson ####@####.####

> Julen,
>
> Another option is to change this line in libgputils/gpcod.h
> #define source_len 63
> to something like
> #define source_len 127
> and recompile.
>
> This shouldn't hurt anything on a Linux system. But Windows can have
> problems (or at least used to) with long paths.
>
> Noel
>
> On Thursday 02 July 2009, Julen Gutierrez wrote:
> > Ok i know that the problem is with COD file, but i cant find any way to
> > avoid the creating of this file with gpasm and with gplink neither.
> >
> >
> > 2009/7/1 Noel Henson ####@####.####
> >
> > > That's what it is. There is the same limitation in MPLAB running under
> > > Windows.
> > >
> > > Noel
> > >
> > > On Wednesday 01 July 2009, Tamas Rudnai wrote:
> > > > I think this is related to the .COD file format unfortunately. The
> > > > documentation is not in front of me but if you can switch off the
> > > > generation of .COD files and use COFF instead then you should be
> > > > fine. This is existing on all development environment that uses .COD
> > > > files, including MPASM, so there is no other cure really than
> > > > avoiding the generation of the .COD.
> > > >
> > > > Alternatively you can move or create a link to your work directory
> > > > so the overall length of path become less than this 62 char limit.
> > > >
> > > > Tamas
> > > >
> > > >
> > > > On Wed, Jul 1, 2009 at 11:10 AM, Julen Gutierrez <
> > > >
> > > > ####@####.#### wrote:
> > > > > I have a problem that i dont know if i can avoid with gpasm. The
> > > > > compiler doesnt work if the path is longer than 62 characters and
> > > > > when it contains spaces. Can i make something? Is there any patch
> > > > > to fix it? It i very important for my application. Please help me!
> > > > > Thanks a lot,
> > > > >
> > > > > Julen
> > >
> > > --
> > >
> > > ------------------------------------------------------------------
> > >  Noel Henson
> > >  www.noels-lab.com     Chips, firmware and embedded systems
> > >  www.vimoutliner.org   Work fast. Think well.
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: ####@####.####
> > > For additional commands, e-mail: ####@####.####
>
>
>
> --
>
> ------------------------------------------------------------------
>  Noel Henson
>  www.noels-lab.com     Chips, firmware and embedded systems
>  www.vimoutliner.org   Work fast. Think well.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
>

Previous by date: 3 Jul 2009 06:19:31 -0000 Re: [gnupic] Path problems...., Noel Henson
Next by date: 3 Jul 2009 06:19:31 -0000 Re: [gnupic] Path problems...., Tamas Rudnai
Previous in thread: 3 Jul 2009 06:19:31 -0000 Re: [gnupic] Path problems...., Noel Henson
Next in thread: 3 Jul 2009 06:19:31 -0000 Re: [gnupic] Path problems...., Tamas Rudnai


Powered by ezmlm-browse 0.20.