Announcement: EAN-02 :: Managing EAGLE Directories

James Morrison wrote:

We've added a new http://www.eaglecentral.ca/eagle-appnotes/.

EAN-02 discusses the issues and perils of configuring the

"Directories" in EAGLE.

"Stratford Digital recommends adding a user folder as the base for all

EAGLE related design files and making it the highest priority."

Although this seems to mirror the way Cadsoft intended to use Eagle, I

strongly dislike the idea of one big tree of Eagle projects.

I put Eagle project files (epf, sch, brd and special project libs) in

subfolders of the product projects where I store also other design

files and docs.

I invoke eagle while this directory is "current" and by passing the

epf file name to eagle. A simple association eith "epf" does the job

inWindows if you use one version of Eagle for all projects, but see

below.

In Eagle, I configure "." (only "."!) as the project root, and I add

"." to the other paths.

Then I navigate to the folder where my project resides and invoke

Eagle from there, in Windows by double clicking the epf file.

Besides this, I use a cmd file to select the matching Eagle version,

because I don't want to convert old projects unintentionally:

- snip -

@echo off

find "Version=""03 5" %1 >nul

if NOT errorlevel 1 (

     start X:\Path_to_Eagle3\eagle.exe %1

     exit /b

)

find "Version=""04 1" %1 >nul

if NOT errorlevel 1 (

     start X:\Path_to_Eagle4\eagle.exe %1

     exit /b

)

find "Version=""05 0" %1 >nul

if NOT errorlevel 1 (

        start X:\Path_to_Eagle5\eagle.exe %1

     exit /b

)

echo Unknown epf version

pause

- snip -

It should be trivial to make a similar shell script for the *x world.

If you don't intend to change old projects and you are using Eagle 5,

this batch file is not needed, because Eagle 5 doesn't change the epf

unasked (earlier versions did).

Oliver

James Morrison wrote:

We've added a new http://www.eaglecentral.ca/eagle-appnotes/.

EAN-02 discusses the issues and perils of configuring the

"Directories" in EAGLE.

"Stratford Digital recommends adding a user folder as the base for all

EAGLE related design files and making it the highest priority."

Although this seems to mirror the way Cadsoft intended to use Eagle, I

strongly dislike the idea of one big tree of Eagle projects.

I put Eagle project files (epf, sch, brd and special project libs) in

subfolders of the product projects where I store also other design

files and docs.

I invoke eagle while this directory is "current" and by passing the

epf file name to eagle. A simple association eith "epf" does the job

inWindows if you use one version of Eagle for all projects, but see

below.

In Eagle, I configure "." (only "."!) as the project root, and I add

"." to the other paths.

Then I navigate to the folder where my project resides and invoke

Eagle from there, in Windows by double clicking the epf file.

Besides this, I use a cmd file to select the matching Eagle version,

because I don't want to convert old projects unintentionally:

- snip -

@echo off

find "Version=""03 5" %1 >nul

if NOT errorlevel 1 (

     start X:\Path_to_Eagle3\eagle.exe %1

     exit /b

)

find "Version=""04 1" %1 >nul

if NOT errorlevel 1 (

     start X:\Path_to_Eagle4\eagle.exe %1

     exit /b

)

find "Version=""05 0" %1 >nul

if NOT errorlevel 1 (

        start X:\Path_to_Eagle5\eagle.exe %1

     exit /b

)

echo Unknown epf version

pause

- snip -

It should be trivial to make a similar shell script for the *x world.

If you don't intend to change old projects and you are using Eagle 5,

this batch file is not needed, because Eagle 5 doesn't change the epf

unasked (earlier versions did).

Oliver