EAGLEDIR

Klaus,

   Well kind-of.  What I think I understand is the following.

   For some reason the "Library Use" list included all the libraries in

the 4.16 structure.

   When I look at the libraries in the Library list in the Control Panel

I see the libraries in 5.1.  If I open a schematic that was created in

5.1 and click "add" the libraries are in the 4.16 structure (as shown by

the path displayed and their contents).  Dropping them and then adding

the 5.1 libraries seems to have solve the problem.

   It still seems strange to me that it pointed to the 4.16 but a

solution is at hand.

   Danke,

Phil

Klaus Schmidinger wrote:

On 07/22/08 05:06, Phil wrote:

 

I have just upgraded to Eagle 5.0 and then upgraded to 5.1.  I have a

Non-profit Standard License.  When I start the 5.x program the library

is pointed to by the variable $EAGLEDIR that is currently set to my

4.16 libraries.  I am not ready to remove 4.16 as some of the designs

are still there and I have not yet made the transition fully to 5.

 

  Where is the value of EAGLEDIR set and how can I change it to point

to the 5.0 structure?

 

EAGLEDIR ist the directory that contains the version of EAGLE

you are currently running.

It is determined at runtime, by taking the full path name to

the eagle.exe file and stripping the "\bin\eagle.exe" part.

 

So if you have installed EAGLE into

 

  C:\Program files\EAGLE-5.1.0

 

the EAGLEDIR variable will contain the value "C:\Program

files\EAGLE-5.1.0".

when you run "C:\Program files\EAGLE-5.1.0\bin\eagle.exe".

 

Klaus Schmidinger

Klaus,

   Well kind-of.  What I think I understand is the following.

   For some reason the "Library Use" list included all the libraries in

the 4.16 structure.

   When I look at the libraries in the Library list in the Control Panel

I see the libraries in 5.1.  If I open a schematic that was created in

5.1 and click "add" the libraries are in the 4.16 structure (as shown by

the path displayed and their contents).  Dropping them and then adding

the 5.1 libraries seems to have solve the problem.

   It still seems strange to me that it pointed to the 4.16 but a

solution is at hand.

   Danke,

Phil

Klaus Schmidinger wrote:

On 07/22/08 05:06, Phil wrote:

 

I have just upgraded to Eagle 5.0 and then upgraded to 5.1.  I have a

Non-profit Standard License.  When I start the 5.x program the library

is pointed to by the variable $EAGLEDIR that is currently set to my

4.16 libraries.  I am not ready to remove 4.16 as some of the designs

are still there and I have not yet made the transition fully to 5.

 

  Where is the value of EAGLEDIR set and how can I change it to point

to the 5.0 structure?

 

EAGLEDIR ist the directory that contains the version of EAGLE

you are currently running.

It is determined at runtime, by taking the full path name to

the eagle.exe file and stripping the "\bin\eagle.exe" part.

 

So if you have installed EAGLE into

 

  C:\Program files\EAGLE-5.1.0

 

the EAGLEDIR variable will contain the value "C:\Program

files\EAGLE-5.1.0".

when you run "C:\Program files\EAGLE-5.1.0\bin\eagle.exe".

 

Klaus Schmidinger