Import/Export Library Devices

Biff schrieb:

Greetings Folks,

 

I just upgraded to Eagle 5 Pro from the free Eagle 4. I have library

devices, packages and symbols that I created which are stored in the testpad

and other libraries of the old version.

 

I would like to be able to get those devices, packages and symbols out of

the old libraries and put them into the new version's libraries.

 

If  I can't get import/export those devices, i will be forced to make them

again and this will take a lot of time.

 

Can you tell me how to get the devices from eagle 4 libraries to Eagle 5

libraries?

 

Thanks Very Much!

 

 

Just use them. A better way would be to copy the lib's into a separate

directory under version 5.x.x .So you keep the version 4 lib's untouched

in case you still want to do version 4 work.

--

Gruß / regards

Joern

On Wed, 23 Sep 2009 18:08:22 -0500, "Biff" <biff@nobiffboy.com> wrote:

Greetings Folks,

 

I just upgraded to Eagle 5 Pro from the free Eagle 4. I have library

devices, packages and symbols that I created which are stored in the testpad

and other libraries of the old version.

 

I would like to be able to get those devices, packages and symbols out of

the old libraries and put them into the new version's libraries..

This is why you should never modifiy any Eagle-supplied libraries.  If

you want to make a modification in an device from an Eagle-supplied

library, first make a copy of the device in a new custom library.  If

you have many such modifications, then you may want to think about how

you are going to organize them.  That is, make one giant custom

library of all your modified devices, or one custom library for each

project, or one custom library for each Eagle-supplied library that

the devices came from - whichever makes the most sense to you.  Keep

only your modified devices in these custom libraries.  Don't just copy

the entire library they came from.  And to further avoid confusion

with the originals, change the name of the device so it is not exactly

the same as the name it had in the Eagle-supplied library.

If you do things this way, then whenever you upgrade to a new version

of Eagle, all you have to do is copy your custom libraries into the

new Eagle library folder, or a subfolder of it, as Joern suggested.

Robert Scott

Real-Time Specialties

Ypsilanti, Michigan

Thanks very much guys for your input. I guess I had to learn this the hard

way which may not be the best way but it does stick.

Luckily, I don't have a lot of devices to deal with so it won't be too

painful to make the transistion.

A fairly quick fix is to use exp-project-lbr.ulp to create a new library

from a board/schematic. If any modifications are required to board devices,

the devices can be replaced from the newly created library.

I must admit that not modifying the stock EAGLE libs is a great idea,

wish I had started that way years ago...and if it said somewhere in the

tutorial to do this, I would have. But I must have missed that. I guess

I will learn the hard way as well. If it's not strongly suggested in the

tutorial and manual, maybe it CADSOFT should put it in there, it makes a

lot of sense.