kicad-developers team mailing list archive

[Martijn Kuipers <martijn.kuipers@xxxxxxxxx>]

Viva,

On Mar 10, 2013, at 10:23 AM, Miguel Angel Ajo Pelayo <miguelangel@xxxxxxx> wrote:

> Hehe, yes, you're right, universal is ppc+x86+x64, x86+x64 is only multi binary.
> 
> My system cannot compile for ppc (it's a mountain lion and has not ppc sdk or rosseta anymore -the emulation layer-.)
> 
Neither can mine. I usually build single versions, because otherwise you are basically downloading the program twice (or thrice when also including ppc).


> Edit the wx patch in patches directory and look for a line that removes ppc (if you want to try with ppc) :)
Also only Mountain Lion (so happy to not have Rosetta around).


> I send your thanks to my wife :)
> 
> I'm also thinking of a new structure to keep the demos & system libs out of the app bundle but in the app directory, as some other apps do
> 
> like
> 
> Applications/kicad/kicad.app (with the libs,etc)
> Applications/kicad/pcbnew.app
> Applications/kicad/*.app  
> Applications/kicad/shared/{libs,modules,templates,plugins…}
> 

I was always hoping to see the libraries ("DLLs") to go into /Library/Kicad, so we can keep the memory footprint down of the separate Kicad components. But it is not a trivial task, so it seems.
I am not following what you want to do. Is it like:
/Applications/kicad/kicad.app <- the app with the libs
/Applications/kicad/libraries <- footprints, components, etc.
/Applications/kicad/scripts <- python user scripts
/Applications/kicad/doc <- documentation and demos
?

Kind regards,
Martijn




> 
> 
> 
> Miguel Angel Ajo
> http://www.nbee.es
> +34911407752
> skype: ajoajoajo
> 
> On 10/03/2013, at 11:18, Martijn Kuipers <martijn.kuipers@xxxxxxxxx> wrote:
> 
>> Hi Miguel,
>> 
>> Downloading as we speak. On the github page you call it a universal OSX binary, but that would mean it supports both PowerPC and Intel based MACS, whereas is this email announcement you call it i386 +x64 build.
>> 
>> I'm looking forward in compiling it myself, just to see if your solution is "portable". 
>> 
>> Thanks also to your wife ;-)
>> 
>> /Martijn
>> 
>> 
>> On Mar 10, 2013, at 2:19 AM, Miguel Angel Ajo Pelayo <miguelangel@xxxxxxx> wrote:
>> 
>>> 
>>> 
>>> Hi, 
>>> 
>>> I've been working on the release of Kicad with scripting for MacOSX, also tried to package it all together with 
>>> all kicad libs, and the templates.
>>> 
>>> It's supposed to be a i386 + x64 binary build, with scripting support.
>>> 
>>> kicad-scripting-osx-latest.zip
>>> 
>>> 
>>> It has all the new kicad templates system and libraries inside kicad.app, and it's supposed to be accessible from all the other apps.
>>> 
>>> I'm not sure if it will only work in 10.8, or may be 10.5-10.8, (it has a dependency to system's python2.7).
>>> 
>>> If there is any adventurous out there, please try, and tell me how does it work (or doesn't).
>>> 
>>> 
>>> PS:
>>> 
>>>    The codename for the release is "wife", as my wife has been taking care all saturday of our little "Margarita", so she's a time donor to kicad now too ;)
>>> 
>>> My build & packaging script is temporarily here, for just in case anyone wants to compile himself.. 
>>> https://github.com/mangelajo/KicadOSXBuilder
>>> 
>>> Cheers!! ;)
>>> 
>>> Miguel Angel Ajo
>>> http://www.nbee.es
>>> +34911407752
>>> skype: ajoajoajo
>>> 
>>> Miguel Angel Ajo
>>> http://www.nbee.es
>>> +34911407752
>>> skype: ajoajoajo
>>> 
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>> 
>