so, it can be feasible to store Gerbers in different directory
e.g. $PROJECTDIR\Gerbers\%N.cmp
I think it is very easy to implement !
so, it can be feasible to store Gerbers in different directory
e.g. $PROJECTDIR\Gerbers\%N.cmp
I think it is very easy to implement !
Walter Spermann wrote:
>$PROJECTDIR is not unique. You can have many of them.
>You'd need something like $PROJECTDIR[n] for n-th project dir.
Is the path to the current eagle.epf unique?
Oliver
--
Oliver Betz, Munich
despammed.com is broken, use Reply-To:
Hello,
On 11/05/12 10:14, Vassilis Papanikolaou wrote:
so, it can be feasible to store Gerbers in different directory
e.g. $PROJECTDIR\Gerbers\%N.cmp
I think it is very easy to implement !
There are already a number of aliasses for CAM output (%D, %E %P etc.).
$PROJECTDIR is not unique. You can have many of them.
You'd need something like $PROJECTDIR[n] for n-th project dir.
If you exchange the order in the directory setup this can be quite confusing.
Supplying the $EAGLEDIR as alias could be an alternative.
Walter Spermann
--
-
Walter Spermann
Softwareentwicklung
CadSoft Computer GmbH
Pleidolfweg 15
84568 Pleiskirchen
Tel.: 08635/6989-10
www.cadsoft.de
-
Registergericht: Amtsgericht Traunstein HRB 5573
Geschäftsführer: Thomas Liratsch
-
Vassilis Papanikolaou wrote:
>so, it can be feasible to store Gerbers in different directory
>e.g. $PROJECTDIR\Gerbers\%N.cmp
Over the years, I suggested many times to add an $EPFDIR placeholder
(and $BRDDIR $SCHDIR). No sucess so far...
>I think it is very easy to implement !
Sure. Who know why CadSoft doesn't want to implement it.
BTW: My way to start Eagle is assigning eagle.exe to *.epf files. My
setting for the "projects" folder in Eagle is just ".". There is no
all-embracing Eagle projects root on my storage. Eagle projects are
just subdirectories next to other project data (software,
calculations, mechanical stuff...).
Oliver
--
Oliver Betz, Munich
despammed.com is broken, use Reply-To: