Storing custom made lbr files

Am 01.11.2012 08:09, schrieb Stefan Olsson:

Hi

 

I have both EAGLE-6.2.0 and EAGLE-6.3.0 installed on my Windows 7 platform.

Over the time I have made a number of .lbr files with both EAGLE versions.

Nowdays I only use EAGLE-6.3.0.

I create designs with components form libraries I have created with both versions of EAGLE.

The parameter "Libraries" in the "Directory" menu is set to "$EAGLEDIR\lbr"

 

Do a newer EAGLE version search older installed EGALE versions /lbr directory for .lbr files ?

Do EAGLE "move around" custom made .lbr files when it is installed ?

 

If a do a search for one of my files, hartman.lbr, I can not find it, neither in C:\Program Files (x86)\EAGLE-6.2.0 or in C:\Program Files (x86)\EAGLE-6.3.0 but if I do "Open library" in EAGLE-6.3.0 and move to C:\Program Files (x86)\EAGLE-6.2.0\lbr EAGLE it will find the file and I can open it ??

 

>

 

Regards Stefan

 

Eagle-6.3.0 is a newer version and may contain updated libraries and

some other corrections.

If you have created your own devices you should put them into your own

libraries and place them into a different directory.

Otherwise if you update eagle into the same directory the libraries will

be overwritten and your work is lost.

You must add the path to your own libraries in the control panel

/options /directories and separate it from existing entry by a semicolon.

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag

Hi

I do understand that and I try to archive this, but I can not find the files I have created, but EAGLE do.

An example.

I have created a library, hartman.lbr:

This library I can open up within EAGLE by doing doing "Open library" but when I try to find the actual file it is nowhere to be found,

neither in

C:\Program Files (x86)\EAGLE-6.2.0\lbr

or in

C:\Program Files (x86)\EAGLE-6.3.0\lbr

So, my question is/was, is EAGLE moving the library files around on it's own, do it concatenate library files when newer versions of EAGLE is installed etc.

Reagrds

Am 01.11.2012 09:36, schrieb Stefan Olsson:

Hi

 

I do understand that and I try to archive this, but I can not find the files I have created, but EAGLE do.

 

An example.

 

I have created a library, hartman.lbr:

 

This library I can open up within EAGLE by doing doing "Open library" but when I try to find the actual file it is nowhere to be found,

 

neither in

C:\Program Files (x86)\EAGLE-6.2.0\lbr

or in

C:\Program Files (x86)\EAGLE-6.3.0\lbr

 

So, my question is/was, is EAGLE moving the library files around on it's own, do it concatenate library files when newer versions of EAGLE is installed etc.

 

>

Reagrds

 

No, why should eagle?

The variable $EAGLEDIR depends on system. Why don't you set a real path?

If you can open your "hartman.lbr" from an eagle sheet/board you should

be able to move up the path to your actual directory.

If this doesn't work start a file search with your operating systen.

Also check that the library is "in use".

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag

Hi

Platform: Windows 7

The reason I ask is that if

A) I Start EAGLE-6.3.0, do open library,

B) I can see the file hartman.lbr,

C) If I right click on the file it says that the path to this file is "C:\Program Files (x86)\EAGLE-6.2.0\lbr"

This mean that EAGLE concatenate the content in both "C:\Program Files (x86)\EAGLE-6.2.0\lbr" and "C:\Program Files (x86)\EAGLE-6.3.0\lbr"

Either by moving files around or just concate the content in the UI.

However, If

A) I open an ordinary Windows file manager

B) Enter the path "C:\Program Files (x86)\EAGLE-6.2.0\lbr"

C) The file hartman.lbr is not there

So, how come that "Open library" inside EAGLE-6.3.0 can find hartman.lbr when I can not do it manually find it via a file browser ?

Regards

Am 01.11.2012 13:26, schrieb Stefan Olsson:

Hi

 

Platform: Windows 7

 

>

The reason I ask is that if

 

A) I Start EAGLE-6.3.0, do open library,

B) I can see the file hartman.lbr,

C) If I right click on the file it says that the path to this file is "C:\Program Files (x86)\EAGLE-6.2.0\lbr"

 

This mean that EAGLE concatenate the content in both "C:\Program Files (x86)\EAGLE-6.2.0\lbr" and "C:\Program Files (x86)\EAGLE-6.3.0\lbr"

Either by moving files around or just concate the content in the UI.

 

However, If

A) I open an ordinary Windows file manager

B) Enter the path "C:\Program Files (x86)\EAGLE-6.2.0\lbr"

C) The file hartman.lbr is not there

 

So, how come that "Open library" inside EAGLE-6.3.0 can find hartman.lbr when I can not do it manually find it via a file browser ?

 

>

 

Regards

 

I don't use Win7, but could it be

C:\*user*\Program Files (x86)\EAGLE-6.2.0\lbr

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag

Op Thu, 01 Nov 2012 13:26:11 +0100 schreef Stefan Olsson 

<noreply-135139@element14.com>:

 

However, If

A) I open an ordinary Windows file manager

B) Enter the path "C:\Program Files (x86)\EAGLE-6.2.0\lbr"

C) The file hartman.lbr is not there

 

So, how come that "Open library" inside EAGLE-6.3.0 can find hartman.lbr 

when I can not do it manually find it via a file browser ?

 

Hello Stefan,

You are probably experiencing a Windows 7, (64 bit), feature called UAC 

Virtualization (AKA Data Redirection). To cut a very long story short: 

Windows 7 doesn't always store youre data where you think it does.

To avoid this, try not to write to protected area's in the file system. 

'Program files' is one such location you should avoid. Try saving you're 

libraries in a folder under your 'Documents' folder.

If you want tom read more about UAC virtualization, search for it. There 

is lot's of info available.

HTH,

Richard

Hi

Yes, you are absolutly right, I checked up this "UAC Virtualization" and after reading about it I found my files at "C:\Users\s20622\AppData\Local\VirtualStore\Program Files (x86)\EAGLE-6.2.0\lbr"

Thanks for the tip.

Man, another reason for wanting Linux even more, another notch on the list that proofs that Microsoft is in no ways have the knowledge of writing operating system but instead messing it up.

"You are not allowed to write to this area, but you can actually, but not here, but it looks like it, you can do it but virtualized, if this manifest file exist or if the launcher is UAC aware or starter program is elevated........"

what a mess, poor these system admins of Windows systems, they can not have easy tasks.

This truly show, again, that anything that Micorsoft promote, recomend or sell shall as far as possible be avoided.

Regards Stefan

I thought you were confused, but you seem to have it figured out "You are

not allowed to write to this area, but you can actually, but not here, but

it looks like it, you can do it but virtualized, if this manifest file

exist or if the launcher is UAC aware or starter program is

elevated........"  man that one is confusing.  I think I want my old CP/M

system back with the floppy drives and a 4mhz Z-80.  Also new to Eagle, I'm

going to have to be careful to avoid that trap door and make sure I have

any of my libraries in my local directory with the preferences pointing to

it.  Thanks for finding that tidbit.

mikey

--

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

I thought you were confused, but you seem to have it figured out "You are

not allowed to write to this area, but you can actually, but not here, but

it looks like it, you can do it but virtualized, if this manifest file

exist or if the launcher is UAC aware or starter program is

elevated........"  man that one is confusing.  I think I want my old CP/M

system back with the floppy drives and a 4mhz Z-80.  Also new to Eagle, I'm

going to have to be careful to avoid that trap door and make sure I have

any of my libraries in my local directory with the preferences pointing to

it.  Thanks for finding that tidbit.

mikey

--

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

Hello,

The UAC Virtualization is of course not an Eagle issue. It's Microsoft 

doing it's best to integrate into W7 a way of working that was (sort of) 

allowed in older Windows versions. It's debatable wether it's the best way 

to do it but let's not start that here....

As a word of advice: use the supplied Eagle lib's as 'read only'. That is, 

as soon as you use a component from one of those lib's, copy it to your 

own lib. NEVER modify the suplied lib's. Those lib's are updated when 

needed and you can bet that by that time you can't remember which library 

you modified and want to keep and which are ok to update. It could even be 

that, for some reason, the part you used isn't in the updated lib.

To avoid a lot of headache in the future, make you own lib's. To make it 

easier, you can use the same name as the Cadsoft lib, prepended by 

something (diode.lbr > own_diode.lbr). It will save you the trouble of 

having to think of a lot of funky names..

Place those lib's somewhere where a normal user has write access and add 

the path to the directory setup in the Eagle control panel (first entry; 

Eagle searches lib's in the order they are written down here). If you use 

the Cadsoft lib's this way, you can leave them where they are.

Richard

Op Sat, 03 Nov 2012 06:22:36 +0100 schreef Mike Fields 

<mr.gadget2@comcast.net>:

I thought you were confused, but you seem to have it figured out "You are

not allowed to write to this area, but you can actually, but not here, 

but

it looks like it, you can do it but virtualized, if this manifest file

exist or if the launcher is UAC aware or starter program is

elevated........"  man that one is confusing.  I think I want my old CP/M

system back with the floppy drives and a 4mhz Z-80.  Also new to Eagle, 

I'm

going to have to be careful to avoid that trap door and make sure I have

any of my libraries in my local directory with the preferences pointing 

to

it.  Thanks for finding that tidbit.

 

mikey

Definitely agree with Richard's comment.  Best solution is to have your own

libraries in your own user space and as he suggests, leave the Eagle

libraries as read-only.  One thing that I think could be helpful is for the

Eagle install process to put a 00_README.txt file in the library directory

briefly describing this issue and the suggested way of storing libraries -

from my searching, I have found many folks that a) don't know the best way

to edit library parts and b) are not sure where to put libraries they have

created.  The UAC thing is certainly not Eagles problem, but it does catch

people un-aware who are used to older versions of windows or other OS's

since the problem comes down to the files not being where you think they

are (like soft links in the Unix world).

mikey

--

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

OK, so along the lines of what Richard says (and others have mentioned),

you user modified/created libs should be somewhere else the user has access

to.  Does anyone have a preferred data structure ?  I notice in W7, when

Eagle 6.3 is installed, it creates a default location for projects under

the users path ( C:\Users\mikey\Documents\eagle\ ).  Two questions come up

in my mind since I am just getting things setup on my machine - is it best

to create a "libs" folder under the C:\Users\mikey\Documents\eagle\ path (

C:\Users\mikey\Documents\eagle\my-libs for example)?  How about 3rd party

libraries like the sparkfun or adafruit libs - put them in the same

"my-libs" folder or put them in a different folder (but still under the

users path)?  What has worked best for folks ?  I realize that in the past

many people just put them in the same library as the Eagle installed libs,

however, as we have seen, that is not a good plan (and Windows is working

to help us figure a better plan) for a number of reasons. It would be nice

to have a consensus on where to put extra libs.

When you add a folder to the search path for libs in eagle, does it just

search that folder or does it search sub-folders within that specified

folder ?

mikey

--

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