Maybe worth to look at : http://virtualenvwrapper.readthedocs.org/en/latest/command_ref.html That is what I use for environments that have multiple configurations (and libraries). Keep going ! Edwin van den Oetelaar
On Mon, Mar 11, 2013 at 2:19 PM, Miguel Angel Ajo Pelayo <miguelan...@nbee.es> wrote: > I also think, that it's important to provide a way for users to have access > to our modules from outside kicad, > that can be easily fixed letting them set (or appending to) PYTHONPATH, as > I'm doing now for MacOSX, > > In linux are you sure they do like that?, in windows for sure. > > If you bundle your own python in linux you stop getting access to all the > libraries available systemwide, > that's important too, where possible (win32 is a different story) > > > Miguel Angel Ajo > http://www.nbee.es > +34911407752 > skype: ajoajoajo > > On 11/03/2013, at 14:14, Adam Wolf <adamw...@feelslikeburning.com> wrote: > > I believe Blender has a Python environment of its own embedded inside of it, > and doesn't reuse a system Python. > > Adam Wolf > Wayne and Layne, LLC > > > On Sun, Mar 10, 2013 at 10:21 PM, Dick Hollenbeck <d...@softplc.com> wrote: >> >> >> On Mar 10, 2013 8:32 PM, "Miguel Angel Ajo Pelayo" <miguelan...@nbee.es> >> wrote: >> > >> > >> > On 11/03/2013, at 03:25, Dick Hollenbeck <d...@softplc.com> wrote: >> > >> >> >> >> On Mar 10, 2013 8:10 PM, "Adam Wolf" <adamw...@feelslikeburning.com> >> >> wrote: >> >> > >> >> > Dick, >> >> > >> >> > We can do it either way. We can push binaries up to the PPA, or we >> >> > can continue to do the bzrbuilder recipe->PPA. I would actually be >> >> > doing >> >> > the bzrbuilder recipe on my local machine. >> >> > >> >> > I can always fix the current cmake issue and do the Mac and >> >> > eventually Windows builds. I'd like to get Linux builds happening >> >> > locally >> >> > for Fedora users anyway. >> >> > >> >> > Anyway, I'm going to fix the cmake pythonpath thing, and get osx >> >> > autobuilds working first, and we can revisit the others when those are >> >> > tested and working. >> >> >> >> Speaking of pyhonpath, we need to rethink where we are going to put >> >> python modules, even for the case when we are not installing to a staging >> >> dir for purposes of packaging. >> >> >> >> Installing things that may need to be edited, into a read only (root >> >> writable) >> >> dir is not a practice that we have to continue. If we allow for >> >> setting env vars, then pythonpath can be modified to point additionally >> >> to a >> >> place that is convenient for kicad python module editor people. >> >> >> >> So I am not content with current. Cmakelists.txt strategy regarding >> >> over usage of system dirs. >> >> My concern remains, as stated above. Think well beyond the current >> situation to many more modules. >> >> And to the day when pcbnew is primatily a dso/dll. >> >> So no, I am not on board with your suggestion. >> >> Just lets find a place where modules can go that is a writable dir. >> >> After all don't we want people writing them? >> >> If you want to move into the future you have to be willing to challenge >> the past. >> >> How does blender do it? >> >> > >> > >> > There, may be it makes sense to make a second package for >> > "KICAD_SCRIPTING_MODULES", as it's just a module to python, >> > it could be the case that somebody wanted to install the pcbnew module >> > in a server, without installing kicad itself, for example. >> > >> > That should go to site-packages of python. >> > >> > For kicad itself, the modules don't need to be installed anywhere, they >> > are linked together into pcbnew itself to allow introspection, >> > so may be for making the normal kicad ppa build, KICAD_SCRIPTING_MODULES >> > should be disabled, >> > and then a second build that only makes the "KICAD_SCRIPTING_MODULES", >> > that needs some cmake scripts rework. >> > >> > Does it make sense? >> > >> >> > >> >> > Adam Wolf >> >> > Wayne and Layne, LLC >> >> > >> >> > On Mar 10, 2013 8:45 PM, "Dick Hollenbeck" <d...@softplc.com> wrote: >> >> >> >> >> >> >> >> >> On Mar 10, 2013 6:50 PM, "Adam Wolf" <adamw...@feelslikeburning.com> >> >> >> 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? >> >> >> >> >> >> The PPA concept is a familiar and trusted one in ubuntu circles, >> >> >> would not want to lose that trust factor among new users of the daily >> >> >> testing builds. >> >> >> >> >> >> Note I said users. These binaries are for usage first, testing is a >> >> >> secondary issue, which is in proportion to numbers of users actually >> >> >> using >> >> >> it. >> >> >> >> >> >> > >> >> >> > Adam Wolf >> >> >> > Wayne and Layne, LLC >> >> >> > >> >> >> > >> >> >> > On Sun, Mar 10, 2013 at 7:43 PM, Miguel Angel Ajo Pelayo >> >> >> > <miguelan...@nbee.es> 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 >> >> >> >> <miguelan...@nbee.es> 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 >> >> >> >>> <martijn.kuip...@gmail.com> 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 >> >> >> >>>> <miguelan...@nbee.es> 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 >> >> >> >>>>> >> >> >> >>>>> :-) >> >> >> >>>>> 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 >> >> >> >>>>>>>> <martijn.kuip...@gmail.com> 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 >> >> >> >>>>>>>>> <miguelan...@nbee.es> 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@lists.launchpad.net >> >> >> >>>>>>>>>> Unsubscribe : https://launchpad.net/~kicad-developers >> >> >> >>>>>>>>>> More help : https://help.launchpad.net/ListHelp >> >> >> >>>>>>>>> >> >> >> >>>>>>>>> >> >> >> >>>>>>>> >> >> >> >>>>>>> >> >> >> >>>>>> >> >> >> >>>>> >> >> >> >>>> >> >> >> >>> >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> Mailing list: https://launchpad.net/~kicad-developers >> >> >> >> Post to : kicad-developers@lists.launchpad.net >> >> >> >> Unsubscribe : https://launchpad.net/~kicad-developers >> >> >> >> More help : https://help.launchpad.net/ListHelp >> >> >> >> >> >> >> > >> >> >> > >> >> >> > _______________________________________________ >> >> >> > Mailing list: https://launchpad.net/~kicad-developers >> >> >> > Post to : kicad-developers@lists.launchpad.net >> >> >> > Unsubscribe : https://launchpad.net/~kicad-developers >> >> >> > More help : https://help.launchpad.net/ListHelp >> >> >> > >> > >> > > > > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
