gnupic: Re: [gnupic] Path problems....
Subject:
Re: [gnupic] Path problems....
From:
Julen Gutierrez ####@####.####
Date:
3 Jul 2009 08:19:34 -0000
Message-Id: <9b88da5f0907030119oe02547dwec004053c01082c0@mail.gmail.com>
I didnt know that... interesting but anyway why does it working now?
It could be very interesting for next version that the generation of cod
file would be optional.
Thanks all!!!!!!
2009/7/3 Tamas Rudnai ####@####.####
> On a Windows machine you can substitute a path to a drive letter so the end
> you will have a shorter path:
>
> C:\> SUBST X: "C:\Documents and Settings\myUserName\My
> Documents\Projects\PIC\myCurrentProject"
>
> ...now you can access to your directory with X: drive ....
>
> Tamas
>
>
> On Fri, Jul 3, 2009 at 8:50 AM, Peter Restall ####@####.#### wrote:
>
> >
> > On Fri, 3 Jul 2009 08:11:02 +0100, Tamas Rudnai wrote:
> >
> > > That would brake the .COD fileformat so you would be incompatible with
> > > everything.
> > > BTW: Windows has no problem with long paths up till 4096 chars if I
> > remember
> > > well.
> > >
> > > Tamas
> >
> > There is also what they call a 'junction' in Windows; it's basically
> their
> > version of a symlink. If the OP is using a Windows machine then he may
> > wish
> > to continue with his code in the original directory and possibly create a
> > junction to it with a shorter name, and do the compilations, etc. from
> > there
> > as was suggested in relation to Linux a few messages ago.
> >
> > The downside is that you need a program from MS to create junctions (it's
> > part
> > of the Win32 API but a program to utilise it is not included by default
> > IIRC),
> > and I forget what it's called; it's part of the server tools package I
> > think.
> > Just do a google and it'll pop up.
> >
> > Regards,
> >
> > Pete Restall
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ####@####.####
> > For additional commands, e-mail: ####@####.####
> >
> >
>
>
> --
> http://www.mcuhobby.com
>
