Update compiling documentation for Fedora and Mac OS X

Documentation/compiling/linux-fedora.txt

@@ -0,0 +1,29 @@
+Compiling KiCad on Fedora
+=========================
+
+First written: 2011-03-09
+
+Lasted edited by: Jerry Jacobs <xor.gate.engineering@gmail.com>
+
+Fedora 14
+---------
+
+First we need to install all the needed tools and libraries with yum. First
+become root with su.
+
+Then invoke yum:
+yum install gcc gcc-c++ bzr cmake doxygen wxGTK-devel make
+
+Create somewhere on your drive a kicad directory.
+
+Then clone the bzr repository:
+bzr checkout lp:kicad testing
+
+then cd into the build directory
+invoke cmake to generate the makefiles
+
+cmake ../testing
+
+If everything went well you should be able to build kicad with make.
+
+make

Documentation/compiling/mac-osx.txt

@@ -36,11 +36,32 @@ At time of writing (2009-01-16) this is on line 18381
            into this: OSX_UNIV_OPTS="-arch ppc -arch i386 -arch x86_64"
 
 Building a universal monolib wxWidgets 2.9 with the following parameters:
-./configure --enable-unicode=yes --enable-shared=no --enable-monolithic --with-opengl \
+./configure --enable-unicode=yes --enable-shared=no --enable-monolithic --with-opengl --with-expat=builtin  --enable-universal_binary --enable-aui --enable-debug --with-osx_cocoa   --with-macosx-sdk=/Developer/SDKs/MacOSX10.5.sdk/ --prefix=/opt/wxwidgets-svn
-  --enable-universal_binary --enable-aui --enable-debug --with-osx_cocoa \
-  --with-macosx-sdk=/Developer/SDKs/MacOSX10.5.sdk/ --prefix=/opt/wxwidgets-svn
 
-If you dont need the debugging symbols then you can remove the --enable-debug parameter.
+Then you should a message like this:
+
+Configured wxWidgets 2.9.2 for `i686-apple-darwin10.4.0'
+
+  Which GUI toolkit should wxWidgets use?                 osx_cocoa
+  Should wxWidgets be compiled into single library?       yes
+  Should wxWidgets be linked as a shared library?         no
+  Should wxWidgets support Unicode?                       yes (using UTF-8)
+  What level of wxWidgets compatibility should be enabled?
+                                       wxWidgets 2.6      no
+                                       wxWidgets 2.8      yes
+  Which libraries should wxWidgets use?
+                                       STL                no
+                                       jpeg               builtin
+                                       png                builtin
+                                       regex              builtin
+                                       tiff               builtin
+                                       zlib               sys
+                                       expat              builtin
+                                       libmspack          no
+                                       sdl                no
+
+
+If you don't need the debugging symbols then you can remove the --enable-debug parameter.
 
 Compiling and installing:
 make
@@ -119,7 +140,6 @@ ld: warning: in /Developer/SDKs/MacOSX10.6.sdk/System/Library/Frameworks//QuickT
 
 You get this error because the QuickTime 10.6 framework is not build with 64bit support. This not a real issue for KiCad because we don't use it anyway.
 
-
 Undefined symbols:
   "TestForIntersectionOfStraightLineSegments(int, int, int, int, int, int, int, int, int*, int*, double*)", referenced from:
       clipLine(EDA_Rect*, int&, int&, int&, int&)in libcommon.a(gr_basic.cpp.o)

INSTALL.txt

@@ -100,6 +100,24 @@ Do not change the KiCad tree, or the location of binary files,
 else KiCad will not be able to find its required files (configuration,
 libraries, etc.).
 
+Mac OS X KiCad tree
+-------------------
+
+System wide files
+
+/Library/Application Support/kicad/demos 
+/Library/Application Support/kicad/internat 
+/Library/Application Support/kicad/library
+/Library/Application Support/kicad/modules 
+/Library/Application Support/kicad/modules/packages3d
+
+User files can be the same as the system wide files but only inside the users home directory.
+
+$HOME/Library/Application Support/kicad
+
+Warning:
+These paths are hardcoded into KiCad, if you put them somewhere else KiCad will not find them when a new 
+project is created. 
 
 Installation from source code
 -----------------------------