Paris (U.E.), le 17/08/2013

        Bonsoir

                Building for various architectures than one is on, on the Mac, 
is something I regretfully bought into (Apple in the beginning told us to go 
for it) but latter found out to be a useless hassle (Apple silently removing 
PPC64 dev tools anybody? Urgh!)

        Bon courage

                        Hubert Holin


On 16 août 2013, at 18:08, Chris Barker - NOAA Federal <chris.bar...@noaa.gov> 
wrote:

> On Fri, Aug 16, 2013 at 7:32 AM, Michael Droettboom <md...@stsci.edu> wrote:
>> We actually discussed this very issue yesterday in our Google hangout about
>> continuous integration.  We're probably going to need to script a full setup
>> from a clean Mac + XCode to a working matplotlib development environment in
>> order to make that happen,
> 
> Just a note -- this did NOT "just work" the other day for me -- it
> found the freetype libs that OS-X has in the X11 build, but didn't
> like them at compile time. I haven't debugged it yet, sorry.
> 
> But the real trick here is what you want to build: which OS-X versions
> do you want to support? which architectures? which Python Build(s)?
> 
> What I've been planning on doing is setting up a gitHub (or something)
> project for building the various dependencies that various python
> packages need -- there are a few that are broadly used: libpng,
> libfreetype (used by MPL, PIL, wxPython, ???). The idea is that if you
> wanted to build MPL (or PIL, or ???) you'd grab the
> MacPyton_Dependencies project, build it, then go from there.
> 
> Anyone want to help? It just feels like we are all repeating
> each-others work a LOT here!
> 
> NOTE: the big issues come up if you want to build binaries that are
> re-distributable (as a package, or with py2app, or???). In this case,
> you need binaries that can run on perhaps older machines than the one
> you're building on, or a different architecture. Building to run on
> the machine it's built-on is a lot easier. (particularly with macport
> or homebrew)
> 
> -CHB
> 
> 
> 
> 
> 
> 
> 
> 
> and obviously that will be shared with the world.
>> Things are even more complex on Windows, and I'd like to do that there, too.
>> So stay tuned.
>> 
>> Mike
>> 
>> 
>> On 08/16/2013 10:02 AM, Paul Hobson wrote:
>> 
>> Mike,
>> 
>> That's great news. Is there any chance we can look forward to "official"
>> instructions for setting up a Mac to develop matplotlib?
>> 
>> I gave up a long time ago and started piecing to together my meager PRs in a
>> linux VM.
>> -paul
>> 
>> 
>> On Fri, Aug 16, 2013 at 6:52 AM, Michael Droettboom <md...@stsci.edu> wrote:
>>> 
>>> Thanks to the gracious donation from Hans Petter Langtangen and the
>>> Center for Biomedical Computing at Simula (http://home.simula.no/~hpl),
>>> I now have a new Mac Mini sitting at my desk.  This should allow me to
>>> keep on top of changes that affect the Mac builds and to better track
>>> down Mac-only issues.
>>> 
>>> Stay tuned over the next few weeks and months as we will most likely be
>>> using some more of these funds to pay for hosted continuous integration
>>> services (as discussed yesterday in our MEP19 Google Hangout).
>>> 
>>> Cheers,
>>> Mike
>>> 
>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> Get 100% visibility into Java/.NET code with AppDynamics Lite!
>>> It's a free troubleshooting tool designed for production.
>>> Get down to code-level detail for bottlenecks, with <2% overhead.
>>> Download for free and get started troubleshooting in minutes.
>>> 
>>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Matplotlib-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>> 
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> Get 100% visibility into Java/.NET code with AppDynamics Lite!
>> It's a free troubleshooting tool designed for production.
>> Get down to code-level detail for bottlenecks, with <2% overhead.
>> Download for free and get started troubleshooting in minutes.
>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Matplotlib-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>> 
> 
> 
> 
> -- 
> 
> Christopher Barker, Ph.D.
> Oceanographer
> 
> Emergency Response Division
> NOAA/NOS/OR&R            (206) 526-6959   voice
> 7600 Sand Point Way NE   (206) 526-6329   fax
> Seattle, WA  98115       (206) 526-6317   main reception
> 
> chris.bar...@noaa.gov
> 
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead. 
> Download for free and get started troubleshooting in minutes. 
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Reply via email to