I like to put the actual commands used in the build server in a source tree somewhere, so there's no magic behind the scenes.
Adam Wolf Wayne and Layne LLC On Mar 10, 2013 8:04 PM, "Miguel Angel Ajo Pelayo" <[email protected]> wrote: > Adam, it sounds great, you're killing my excuse to buy a Mac Mini ;-), > but ok :D, will reinvest it wisely > on KiCad :) > > I can provide you with an account to kicad-pcb.org to upload files as > they build, just let me know > if you need any help for the setup. > > I think that's important that we keep the "building recipe" and > enhancements fully open, so > anybody can rebuild it easily, even if we're "caught by a bus" (thing I > don't expect or want) :D > In fact, many parts (like packaging, loading or linking tweaks) would be > better integrated into > KiCad cmake scripts, and pulled out of the "build.sh". > > > PS: I'm remembering that Jean Pierre asked me so long ago about a download > area, and I totally forgotten, > may be soon will be the time for downloads.kicad-pcb.org or equivalent > place. > > Miguel Angel Ajo > http://www.nbee.es > +34911407752 > skype: ajoajoajo > > On 11/03/2013, at 01:50, Adam Wolf <[email protected]> wrote: > > Miguel, > > Wayne and Layne recently purchased a Mac Mini for Kicad builds. We have a > spare Windows license too, so I can host a Windows and Linux VM on it as > well. > > I can set this up on a Jenkins instance. I'm considering doing the same > with the Linux builds. While I like the PPA autobuilder, the build > environment isn't like what the devs use, so the PPA breaks on a regular > basis--and then it's hard to see why, because my box isn't emulating the > PPA environment exactly. This is currently the case with the cmake thing. > > I can even push my built packages back up to my PPA, so the transition > could be seamless to end users. > > What do you guys think? > > Adam Wolf > Wayne and Layne, LLC > > > On Sun, Mar 10, 2013 at 7:43 PM, Miguel Angel Ajo Pelayo < > [email protected]> wrote: > >> This tuesday I must decide if I keep renewing our *ltium license, or if >> we won't. >> >> I'm thinking about donating 1/2 - 2/3 of it's cost to buy one of those >> mac minis to >> provide continuous integration/building of kicad binaries for OSX on >> every bzr release. >> >> It would be wonderful also if we managed to do same thing for Windows >> users, I can >> provide a windows VM for that somewhere, or try to setup a cross >> compiling from linux >> once all the python+mingw+wxython mess gets working (and Dick + Brian + >> Wayne >> are working hard on this). >> >> >> >> >> Miguel Angel Ajo >> http://www.nbee.es >> +34911407752 >> skype: ajoajoajo >> >> On 11/03/2013, at 01:35, Miguel Angel Ajo Pelayo <[email protected]> >> wrote: >> >> Awesome!!, thanks for testing Martijn, :-) >> >> I think I used cmake from homebrew: >> >> MacBook-Air-de-Miguel:src ajo$ which cmake >> /Users/ajo/.rvm/bin/cmake >> MacBook-Air-de-Miguel:src ajo$ ls -la `which cmake` >> lrwxr-xr-x 1 ajo staff 47 2 mar 00:24 /Users/ajo/.rvm/bin/cmake -> >> ../../.homebrew/Cellar/cmake/2.8.10.2/bin/cmake >> >> So we should document how to install brew, and cmake + wget + bzr + >> swig >> >> >> >> Miguel Angel Ajo >> http://www.nbee.es >> +34911407752 >> skype: ajoajoajo >> >> On 11/03/2013, at 01:29, Martijn Kuipers <[email protected]> >> wrote: >> >> Congratulations Miguel! >> >> I just completed a build on a pristine Macbook Air. >> >> Some (minor) comments: >> You need "wget", "bzr" and "swig". I installed all of these with homebrew >> without any problems. And you need cmake (not from homebrew, but cmake has >> native OSX version). >> >> Other prerequisites: >> XCode and Xcode command line tools (obviously), which you can get from >> Apple. >> >> Then be patient and just watch the screens scroll by, but the result is >> really nice :-) >> The entire directory needs about 2.5GB, The zipped Kicad is almost 100 >> MB, which is around 350MB unpacked. >> >> Um abraço, >> Martijn >> >> >> On Mar 10, 2013, at 6:56 PM, Miguel Angel Ajo Pelayo <[email protected]> >> wrote: >> >> 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 >> ? >> >> >> Look to the patches/loader.sh on github, at this moment, all the >> libraries *.dylib and files go inside kicad.app/Frameworks/ and the other >> apps use them from there (../../../kicad.app/Frameworks) , wx and >> python-site mainly. >> >> Also there are the demos+modules+etc in kicad.app/Resources/ or something >> like that that's what I was planning to pull out of kicad.app again and >> yet leave it findable for all the apps. >> >> >> >> >> https://github.com/mangelajo/KicadOSXBuilder/commit/c41f116620182d56c07aee75cd751fe1ba922f7f >> This is the change, I also re-uploaded >> kicad-scripting-osx-3992.zip<http://dev.kicad-pcb.org/pkgs/macosx/kicad-scripting-osx-3992.zip> >> >> :-) >> I think it's better like this, people can go into the data directory and >> change/fetch whatever they like :) >> >> >> >> >> Kind regards, >> Martijn >> >> >> >> >> >> >> >> Miguel Angel Ajo >> http://www.nbee.es >> +34911407752 >> skype: ajoajoajo >> >> On 10/03/2013, at 11:18, Martijn Kuipers <[email protected]> >> 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 <[email protected]> >> 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<http://dev.kicad-pcb.org/pkgs/macosx/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 : [email protected] >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> >> > >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
