Thanks for the info. (Also, I think my 10.10/10.10 build is going through now at least.)
Adam Wolf On Wed, May 13, 2015 at 12:27 PM, Bernhard Stegmaier < [email protected]> wrote: > Hi, > > I made successfully some builds last weekend… after I sorted out the cmake > problems with using a non-system openssl I have posted. > I always use external boost from MacPorts (just like all other > dependencies) at least half a year now… 1.56 and after the MacPorts update > 1.58. > > I didn’t rebuild wxWidgets… still using a 3.0.2 built maybe half a year > ago with a target version of 10.9. > KiCad also was built with a target version of 10.9 (forgot to switch to > 10.10 now that all my machines are updated). > boost 1.58 was built with a target version 10.10. > > Quite a mess, but works without any problem… :) > > OS X is 10.10.3, Xcode is 6.1 and command line tools are 6.3. > > Do you use wxPython? > If I remember correctly, then the wxPython build script > (build-wxpython.py) had some issues with the target version parameter or > didn’t support it at all… that’s why I didn’t use it in my osx_build_wx.sh, > but manually compiled wxWIdgets/wxPython in two steps… > > > Regards, > Bernhard > > > > On 13 May 2015, at 18:50, Adam Wolf <[email protected]> > wrote: > > > > Hi folks, > > > > The nightly OS X builds are continuing fine. > > > > I am debugging some issues on my development machine. > > > > Who is able to make a Mac build, and what version of XCode are you > running? > > > > The issues I'm having are mismatches between wx and boost and kicad. > When I build for 10.7 on 10.10, like I do on the build cluster, I get an > issue where wx doesn't appear to be built for 10.7, but kicad is, so > there's a linking issue. > > > > When I build for 10.10 on 10.10, after clearning out all my builds and > everything, I get an issue where boost and kicad don't appear to be built > with the same version. > > > > I'm going to try another OS X machine, but I don't have a limitless > supply of Macs, and there's absolutely no way I'm going to touch my build > cluster at this point :) > > > > It may be some artifact left over i'm not seeing--it may be a bug in my > build scripts, or it may be an issue caused by an XCode update I did about > a month ago. > > > > Adam Wolf > > _______________________________________________ > > 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
