gnupic: Re: [gnupic] Path problems....
Subject:
Re: [gnupic] Path problems....
From:
Julen Gutierrez ####@####.####
Date:
2 Jul 2009 08:06:22 -0000
Message-Id: <9b88da5f0907020106u1c70de7bwd733dc3073c08396@mail.gmail.com>
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: ####@####.####
>
>
