CAM Process Create Directories

On 7/22/2011 7:45 AM, James Morrison wrote:

Hello,

 

I would like to suggest that there be a way for the CAM processor to

automatically create any sub-directories it needs based on the file

specified for a given layer.  For instance, I have the following file

specified for my top layer:

 

%P/gerbers/01-top.grb

 

This structure helps keep the design files separate from the manufacturing

file output.

 

But I have to manually create the gerbers folder which is a bit of a pain.

There is more to this folder structure so it's not just one folder, but

actually a whole tree of folders for various outputs and formats.

 

It would be nice if I could set a switch in the CAM processor to simply

create any sub-directories that it needs that don't exist.

 

James.

 

or even not a switch... just do it.

Gary Gofstein wrote on Fri, 22 July 2011 17:16

or even not a switch... just do it.

No!  Don't "just do" something that is incompatible with the current

behavior.

If Eagle had always created subdirectories then I'd probably have my system

set up to work with that now.  But it doesn't, so I've created my workflow

around what Eagle does now.  DON'T CHANGE THE DEFAULT.

I use a separate directory for every version of every board, and just put

all the files in there as one flat pile.  I just checked, and a fairly full

directory has around 40 files.  That's easily managable without

subdirectories.  I do have scripts that know the various file name suffixes

and build the zip files for the board house and for assembly.  These take

care of the details of grabbing appropriate files from the pile so I don't

have to.  When I want a file, I know its name and use it directly, so the

fact that there are 39 other files in the directory is irrelevant.

So for me there is no problem to solve as I've already adapted to how Eagle

does things.  Add new features if you want, but make sure the default is to

do the same thing as before.  It would really piss me off if the next

verion of Eagle did something different out of the box, and I had to waste

time digging around figuring out how to get it back as it was.

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

"Olin Lathrop" <eagle@embedinc.com> wrote in message

news:j0ek49$bhl$1@cheetah.cadsoft.de...

around what Eagle does now.  DON'T CHANGE THE DEFAULT.

With this attitude, over 5 years we will use Eagle10, with the same "default

functionality" as now, and it will be ten thousands "new" features hidden

well in some command-line-only-editable file.

"Olin Lathrop" <eagle@embedinc.com> wrote in message

news:j0ek49$bhl$1@cheetah.cadsoft.de...

around what Eagle does now.  DON'T CHANGE THE DEFAULT.

With this attitude, over 5 years we will use Eagle10, with the same "default

functionality" as now, and it will be ten thousands "new" features hidden

well in some command-line-only-editable file.