On 10 Apr 2009, at 03:55, William Matthew Pfenninger wrote:

> John,
>
> I'm relatively new to Kicad as well, so take these instructions  
> with a grain of salt (Developers & others in-the-know, feel free to  
> correct any errors I may make).
>
> You can use the link dioiioib provided to download a working copy  
> of the application suite (just choose the latest build from the  
> main list).  Then un-gzip/un-tar the download.  You can move the  
> resulting unpacked folder elsewhere on the disk of you'd like  
> (seems to work OK in /Applications).
>
> Next, you'll want to download the default library elements.  You  
> can either do this via SVN (follow the instructions at http:// 
> kicad.sourceforge.net/wiki/index.php/Download) or use a direct  
> download (http://sourceforge.net/project/showfiles.php? 
> group_id=145591&package_id=267495).  Either way, you should be be  
> able to move the two contained folders ("library/" and "modules/"  
> into the "<kicad-folder>/share/" directory.
>
> On my system (and presumably, yours), you should be able to start  
> Kicad by double-clicking "<kicad-folder>/bin/kicad.app".  Primary  
> documentation is still the wiki (http://kicad.sourceforge.net/wiki/ 
> index.php/Main_Page) and I recommend going through the tutorial  
> (http://kicad.sourceforge.net/wiki/index.php/Mini_tutorial).
>
> If the default libraries don't contain the parts you're using, you  
> can find a wealth of volunteer-supported libraries through a Google  
> search ("kicad library").  Otherwise it's relatively easy to create  
> your own.
>
> Hope this helps.  Cheers,
>
> - Matt

Thanks Matt,

I have done exactly as you say and installed the two folders into the  
share directory. When I click the kicad.app or right click and open  
it, nothing launches and nothing happens. I am running OS X 10.4.11  
on a Dual 2 GHz PowerPC G5.

Any further advice? I have been through this exercise twice before  
with no success. I could try a Mac with OS X 10.5, but it's still a  
PowerPC, not Intel.

Best wishes,

John

Reply via email to