Differences

This shows you the differences between two versions of the page.

--- kicad:footprint_management [2013/06/26 02:59] – [Footprints, modules, libraries] mithat
+++ kicad:footprint_management [2013/06/26 03:21] – [Adding individual third-party footprints to system and third-party libraries] mithat
@@ Line 38: / Line 38: @@
 In addition to distributing collections of footprints in libraries (stored in ''.mod'' files), it is also possible to distribute individual footprints using ''.emp'' files.((Many/most/all of the footprints downloadable from  http://www.kicadlib.org/ are packaged as .emp files.)) However, to use a footprint stored in an ''.emp'' file, it must first be //imported// into a library.
-//**Even though you can import footprints into system and third-party libraries, you are strongly advised against making any changes to system and third-party libraries.**// When you update KiCad, there is a good chance that the system libraries will be overwritten, and you will lose any changes you have made to them. Similarly, if you download an update to a third-party library, you will lose the changes you have made to that library.
+You should add new footprints only to user footprint libraries. See [[#User footprint libraries]] and [[#Adding existing footprints to an existing user library]] below.
-Instead, you should add new footprints to user footprint libraries. See "User footprint libraries" and "Adding existing footprints to an existing user library" below.
+<WRAP center round important 60%>
+//**Even though you can import footprints into system and third-party libraries, you are strongly advised against making any changes to system and third-party libraries.**//
+This is because when you update KiCad, there is a good chance that the system libraries will be overwritten, and you will lose any changes you have made to them. Similarly, if you download an update to a third-party library, you will lose the changes you have made to that library.
+</WRAP>
 ===== User footprint libraries =====