kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #16242
Re: OS X Packaging Update
Hi, I'm the guy who emailed the list on Sunday. Sorry, I've been swamped with things but I will be more present and involved. I have python scripting working great, but involves some of that python voodoo I mentioned. It does require downloading the official python redistributable framework and (optionally) removing some innards to slim it down to the basic framework build target. But after that, it just needs to be pointed to when building wxpython and then kicad. For now, I am just going to include instructions on this in the branch description, as I am unsure how everyone wants to handle that. I'd be happy to incorporate it to Adam Wolf's build script if desired, or whatever else, but for now...check the branch description :). Writing documentation and doing general polishing but that branch is imminent.
A couple other things related to builds and OS X:
For a tiny bit, I've been providing (very) unofficial KiCad builds for OS X users, but I intentionally have done this without any web presence beyond a single forum thread, to make it simple to direct people to official mac builds and not have weird moonshiney binaries of KiCad floating around. I hope this isn't something frowned upon, I really did it with best intentions. I have stopped this since joining the developer list (I don't want any possibility of people thinking it's official), and tried to word things well. Here is the thread: https://forum.kicad.info/t/new-os-x-kicad-build-with-all-the-trimmings <https://forum.kicad.info/t/new-os-x-kicad-build-with-all-the-trimmings>
As you can see, the response and enthusiasm from OS X users has been enormous! Many users have desperately wanted a newer version of KiCad, but its sheer insurmountability that bars them. Building a package from source is just too far outside their knowledge base. Some can deal with running a script or using homebrew or macports to install something, but we OS X users in general do not have much experience or knowledge of traditional build systems (XCode handles that stuff for us) and have only the most basic knowledge of unix shells. This is not to our fault - there is, for most users and developers, no need and very limited benefits to learning those skills, so of course, we don't. That's a huge generalization of course, but based on what I've observed as well as issue threads for mac ports and homebrew, OS X users just seem extremely weak in these areas, far weaker than the rest of the *nix communities, in my opinion. And its often overlooked or unnoticed, in my opinion.
My point is, OS X users are jonesing for builds! :D They''d be happy with monthlies, but nightlies are of course even better. Adam Wolf's osx builder script will be welcomed, that much I am certain of! Even with the terrific documentation on how to build KiCad on OS X that is right there in the repo, it is a bit much to ask of the average OS X electrical engineer :). A single script will make a lot of people pretty happy.
Finally, the last thing I want to mention. I haven't gone public with it yet, but I also have a working --HEAD only tap that will build and install KiCad for OS X. I'd like to add automatic kicad-library cloning before telling anyone about it and clean up the real dirty ruby code that it is right now, but if anyone is interested, https://github.com/metacollin/homebrew-kicad <https://github.com/metacollin/homebrew-kicad> is it and it works, at least on my system. Not sure if its any use to anyone, but thought I'd let you guys know.
> On Jan 6, 2015, at 11:31 AM, Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> No problem. I hope you enjoyed your break--I definitely enjoyed mine!
>
> I'm going to stick with the OS X nightlies, and get them actually uploading nightly. I realized I do not have Python scripting enabled with those, so that'll be the next thing, but I think between Bernhard and the person who emailed the list on Sunday, we should be pretty good there.
>
> I think Windows is in a better place than OS X was a year ago, but I think it would be good if we had official builds somewhere. I do not quite understand what msys2 is, so I'll wade in and see how it all fits together.
>
> Thanks for everything, and enjoy your upcoming trip to Brussels.
>
> Adam Wolf
> Cofounder and Engineer
> W&L
>
> On Tue, Jan 6, 2015 at 12:17 PM, Wayne Stambaugh <stambaughw@xxxxxxxxx <mailto:stambaughw@xxxxxxxxx>> wrote:
> Hey Adam,
>
> Sorry for the late reply. I'm finally getting caught up from my lazy
> holiday break. I though our current Linux (at least Ubuntu and other
> Debian based distros) situation was pretty good. I would like to see
> more up to date Windows nightly builds if at all possible. You might
> want to get in touch with the person who runs the site
> http://kicad.nosoftware.cz/ <http://kicad.nosoftware.cz/>. I don't know that we need full installers
> as they are rather large. Maybe we could provide updated binaries in an
> archive format that could be installed over top of an existing setup.
> The other option is to us the msys2 environment to build 32 and 64 bit
> pacman mingw packages. This should be very straight forward now that I
> have the full package build defined. If you need the msys2 build
> instructions, please let me know and I will write up a quick cheat
> sheet. One of these days, I will add the msys2 build instructions to
> the developer documentation. Thanks for all of your hard work on the
> OSX nightly builds.
>
> Cheers,
>
> Wayne
>
>
> On 12/23/2014 5:17 PM, Adam Wolf wrote:
> > Thanks. That first response by me really made me sound grumpy--I wish I
> > could unsend it!
> >
> > I think the drag and drop is good for nightlies, but if we make a
> > package and put it in the App Store, we get around the issues from drag
> > and drop, as long as we follow Apple policy on where to put stufff
> > (which I think we do, thanks to Bernhard and all the other OS X Kicad
> > devs scattered throughout time and space).
> >
> > I expect there will be discussion and certainly some modification s
> > after the next progress update, but then I am going to ask Wayne what he
> > wants me to work on next for packaging -- Windows, some Linux, or pursue
> > getting Kicad into the Mac App Store (for free of course) so Mac folks
> > can install the upcoming "stable" versions through the App Store.
> >
> > Adam Wolf
> > Cofounder and Engineer
> > W&L
> >
> >
> > On Tue, Dec 23, 2014, 4:11 PM Martijn Kuipers <martijn.kuipers@xxxxxxxxx <mailto:martijn.kuipers@xxxxxxxxx>
> > <mailto:martijn.kuipers@xxxxxxxxx <mailto:martijn.kuipers@xxxxxxxxx>>> wrote:
> >
> > Hi Adam, and others,
> >
> > I myself several years ago tried a OS X package and know the pain it
> > gives. I think the Drag & Drop you have is fine.
> >
> > If you want to do more interesting things, then I would like to
> > suggest a program called Packages
> > (http://s.sudre.free.fr/Software/Packages/about.html <http://s.sudre.free.fr/Software/Packages/about.html>).
> > It should even allow to add multiple bundles and have the user
> > choose what to install.
> >
> > Although I am not sure how to incorporate that into a cake-build,
> > but I guess we have some of the most knowledgeable cmake-builders
> > (people) on board.
> >
> > Adam, please do not take this as a complaint. I think the work you
> > have done for OS X users is excellent. I just happen to stumble upon
> 7> this and think it might be of help, alleviating some of your
> pains ;-)
> >
> > Anyway, to you and the entire KiCad list: A Merry Christmas and
> > thanks for KiCad.
> >
> > /Martijn
> >
> >
> >> On 23 Dec 2014, at 21:27, Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx <mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx>
> >> <mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx <mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx>>> wrote:
> >>
> >> Thanks! Great eye!
> >>
> >> Adam Wolf
> >> Cofounder and Engineer,
> >> W&L
> >>
> >> On Tue, Dec 23, 2014 at 3:21 PM, Nick Østergaard
> >> <oe.nick@xxxxxxxxx <mailto:oe.nick@xxxxxxxxx> <mailto:oe.nick@xxxxxxxxx <mailto:oe.nick@xxxxxxxxx>>> wrote:
> >>
> >> 2014-12-23 22:03 GMT+01:00 Adam Wolf
> >> <adamwolf@xxxxxxxxxxxxxxxxxxxx <mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx>
> >> <mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx <mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx>>>:
> >> > I think Lorenzo made that image. I am not sure if it is the logo we want to
> >> > go with, but I found the SVG inside of bitmaps_png/source or something and
> >> > dragged it into Inkscape.
> >>
> >> Aha! I did not notive that. But the reason the logo you have
> >> looks odd
> >> is becuase you don't have the "original" font, which is Tiresias
> >> LPfont. I can be found on
> >> http://www.tiresias.org/fonts/lpfont.zip <http://www.tiresias.org/fonts/lpfont.zip> if
> >> it is of interest. Seems to be a GPL font, I did not really
> >> read the
> >> copying note. Also note that curl and wget fails on that URL,
> >> downloading with a browser works fine.
> >>
> >> > I definitely think we need to change the arrowheads, both in
> >> size and not
> >> > being pure black--they are very harsh. I also think that we
> >> might want to
> >> > investigate what a nice subtle texture background looks like
> >> too.
> >> >
> >> > http://subtlepatterns.com/ <http://subtlepatterns.com/>
> >> >
> >> > I will take a stab at a better set of backgrounds in soon,
> >> and also I will
> >> > make my script use an svg from the source, I think, so that
> >> anyone with
> >> > commit access can update the svg and it'll show up in the
> >> next day's
> >> > package.
> >> >
> >> > Adam Wolf
> >> > Cofounder and Engineer
> >> > W&L
> >> >
> >> > On Tue, Dec 23, 2014 at 2:25 PM, Nick Østergaard
> >> <oe.nick@xxxxxxxxx <mailto:oe.nick@xxxxxxxxx> <mailto:oe.nick@xxxxxxxxx <mailto:oe.nick@xxxxxxxxx>>> wrote:
> >> >>
> >> >> 2014-12-23 21:08 GMT+01:00 Adam Wolf
> >> <adamwolf@xxxxxxxxxxxxxxxxxxxx <mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx>
> >> <mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx <mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx>>>:
> >> >> > I do not think I ever got connected with Miguel enough to
> >> get a working
> >> >> > login to the server. If you have access, I can give you
> >> an ssh public
> >> >> > key
> >> >> > that you can add to a user.
> >> >>
> >> >> I don't have login access to the machine itself, just the
> >> Jenkins
> >> >> interface.
> >> >>
> >> >> > Also, sneak peek. (I am not a graphics guy, but I
> >> whipped this up as a
> >> >> > barebones example.)
> >> >>
> >> >> Looks great to me, although I think those arrowheads are
> >> massive
> >> >> comared to the arrow line part. And the KiCad logo looks
> >> odd to me,
> >> >> compared to:
> >> >>
> >> >>
> >> http://www.kicad-pcb.org/download/attachments/589828/kicad_logo.png?version=1&modificationDate=1334481453000&api=v2 <http://www.kicad-pcb.org/download/attachments/589828/kicad_logo.png?version=1&modificationDate=1334481453000&api=v2>
> >> >>
> >> >> But I am not really sure where the original vectorized
> >> version is, I
> >> >> think it was Lorenzo that made it, is that right?
> >> >>
> >> >> > Adam Wolf
> >> >> > Cofounder and Engineer
> >> >> > W&L
> >> >> >
> >> >> > On Tue, Dec 23, 2014 at 1:37 PM, Nick Østergaard
> >> <oe.nick@xxxxxxxxx <mailto:oe.nick@xxxxxxxxx> <mailto:oe.nick@xxxxxxxxx <mailto:oe.nick@xxxxxxxxx>>>
> >> >> > wrote:
> >> >> >>
> >> >> >> 2014-12-23 19:14 GMT+01:00 Adam Wolf
> >> <adamwolf@xxxxxxxxxxxxxxxxxxxx <mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx>
> >> <mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx <mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx>>>:
> >> >> >> > Hi Nick,
> >> >> >> >
> >> >> >> > I have a jenkins system here--I can upload my build
> >> artifacts to the
> >> >> >> > Kicad
> >> >> >> > Jenkins though. I would prefer not to make my system
> >> be a direct
> >> >> >> > build
> >> >> >> > slave
> >> >> >> > for security reasons.
> >> >> >>
> >> >> >> Ok, this is fair enough.
> >> >> >>
> >> >> >> But did Miguel ever get around to give you the access to
> >> get the
> >> >> >> automated uploads working?
> >> >> >>
> >> >> >> > I was out sick all last week with a 102F fever, but
> >> this weekend I
> >> >> >> > updated
> >> >> >> > my script to build a good Kicad footprints dmg. I
> >> think the last
> >> >> >> > thing
> >> >> >> > left
> >> >> >> > before the next status update is setting KIGITHUB. I
> >> tested it and
> >> >> >> > it
> >> >> >> > works
> >> >> >> > well, but I need to do it automatically.
> >> >> >>
> >> >> >> Ok, get well soon. Good to hear you are still progressing.
> >> >> >>
> >> >> >> > Adam Wolf
> >> >> >> > Cofounder and Engineer
> >> >> >> > W&L
> >> >> >> >
> >> >> >> > On Tue, Dec 23, 2014 at 12:01 PM, Nick Østergaard
> >> <oe.nick@xxxxxxxxx <mailto:oe.nick@xxxxxxxxx> <mailto:oe.nick@xxxxxxxxx <mailto:oe.nick@xxxxxxxxx>>>
> >> >> >> > wrote:
> >> >> >> >>
> >> >> >> >> Hello Adam
> >> >> >> >>
> >> >> >> >> I see that your builds is not added to the Jenkins
> >> running on
> >> >> >> >> ci.kicad-pcb.org <http://ci.kicad-pcb.org/> <http://ci.kicad-pcb.org/ <http://ci.kicad-pcb.org/>>. I want
> >> to see that happen, and Miguel gave me
> >> >> >> >> rights
> >> >> >> >> on Jenkins some time ago.
> >> >> >> >>
> >> >> >> >> So if you are ready to set this up, it should be
> >> straight forward to
> >> >> >> >> add a slave node (your OSX machine). All it takes is
> >> jave on the
> >> >> >> >> slave, and a SSH connection. Jenkins copies a jar to
> >> the slave where
> >> >> >> >> jenkins operate from.
> >> >> >> >>
> >> >> >> >> It can be used with a username and password, or via
> >> SSH keys. I
> >> >> >> >> tried
> >> >> >> >> both with the fedora20 connection. Seems to work nicely.
> >> >> >> >>
> >> >> >> >> Basically what is needed for the SSH key method, that
> >> is a private
> >> >> >> >> key
> >> >> >> >> on the master and the public key in the
> >> authorized_keys file on the
> >> >> >> >> relevant user on the slave. I guess it is best to
> >> have a dedicated
> >> >> >> >> user on the box for the kicad build, just for
> >> seperation of access
> >> >> >> >> to
> >> >> >> >> the filesystem.
> >> >> >> >>
> >> >> >> >> The jenkins job is just invoking commands on the
> >> shell, so if you
> >> >> >> >> already have a script to do the work, I can just call
> >> that from
> >> >> >> >> jenkins, and you can easily maintain it. I think.
> >> Maybe some
> >> >> >> >> catches
> >> >> >> >> for errors is needed for proper buildfailure
> >> detection. Otherwise I
> >> >> >> >> guess I can give you rights on the master.
> >> >> >> >>
> >> >> >> >> Regards
> >> >> >> >> Nick Østergaard
> >> >> >> >>
> >> >> >> >> 2014-10-30 15:01 GMT+01:00 Adam Wolf
> >> >> >> >> <adamwolf@xxxxxxxxxxxxxxxxxxxx <mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx>
> >> <mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx <mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx>>>:
> >> >> >> >> > Hi folks,
> >> >> >> >> >
> >> >> >> >> > Things are progressing very well on the OS X
> >> packaging front!
> >> >> >> >> >
> >> >> >> >> > Every time bzr is updated for lp:kicad, a Mac build
> >> is generated,
> >> >> >> >> > and
> >> >> >> >> > every
> >> >> >> >> > night, a clean build is generated and packaged as a
> >> dmg. Miguel
> >> >> >> >> > is
> >> >> >> >> > working
> >> >> >> >> > on fixing my SSH credentials on the server, so I
> >> can push the
> >> >> >> >> > build
> >> >> >> >> > logs
> >> >> >> >> > and
> >> >> >> >> > dmgs.
> >> >> >> >> >
> >> >> >> >> > I've done my best to script a dmg creator that
> >> matches what
> >> >> >> >> > end-users
> >> >> >> >> > expect
> >> >> >> >> > from downloaded Mac applications. I think it is
> >> very good at this
> >> >> >> >> > point.
> >> >> >> >> >
> >> >> >> >> > You can see an image of what it looks like inside
> >> one of these
> >> >> >> >> > dmgs,
> >> >> >> >> > attached to this email.
> >> >> >> >> >
> >> >> >> >> > The build log is included with every package, and
> >> also will be
> >> >> >> >> > uploaded
> >> >> >> >> > next
> >> >> >> >> > to every package, so that you don't have to
> >> download the entire
> >> >> >> >> > package
> >> >> >> >> > to
> >> >> >> >> > see a build log.
> >> >> >> >> >
> >> >> >> >> > The package is currently around 200 megs.
> >> >> >> >> >
> >> >> >> >> > The README is dynamically generated at package
> >> time. A sample one
> >> >> >> >> > follows.
> >> >> >> >> > Please let me know if you have any additions or
> >> suggestions:
> >> >> >> >> >
> >> >> >> >> > KiCad
> >> >> >> >> > =====
> >> >> >> >> > KiCad is an EDA software suite for the creation of
> >> professional
> >> >> >> >> > schematics
> >> >> >> >> > and printed circuit boards up to 32 copper layers.
> >> KiCad runs on
> >> >> >> >> > Windows,
> >> >> >> >> > Linux and OS X and is released under the
> >> open-source GNU GPL v2
> >> >> >> >> > free
> >> >> >> >> > of
> >> >> >> >> > charge.
> >> >> >> >> >
> >> >> >> >> > With KiCad you can create schematic diagrams and
> >> printed circuit
> >> >> >> >> > board
> >> >> >> >> > up to
> >> >> >> >> > 32 copper layers. KiCad comes with a rich set of
> >> libraries with 3D
> >> >> >> >> > models as
> >> >> >> >> > well.
> >> >> >> >> >
> >> >> >> >> > KiCad is a mature EDA software tool under active
> >> development by a
> >> >> >> >> > team
> >> >> >> >> > of
> >> >> >> >> > developers and a vibrant user group. KiCad team
> >> counts three main
> >> >> >> >> > developers
> >> >> >> >> > and a dozen of regular contributors.
> >> >> >> >> >
> >> >> >> >> > Documentation
> >> >> >> >> > =============
> >> >> >> >> > Documentation is available in this disk image under
> >> docs/, and is
> >> >> >> >> > available
> >> >> >> >> > online at http://www.kicad-pcb.org/ <http://www.kicad-pcb.org/>.
> >> >> >> >> >
> >> >> >> >> > Changelog
> >> >> >> >> > =========
> >> >> >> >> > You can browse the changelog at
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> >
> >> https://bazaar.launchpad.net/~kicad-product-committers/kicad/product/changes <https://bazaar.launchpad.net/~kicad-product-committers/kicad/product/changes>.
> >> >> >> >> >
> >> >> >> >> > Reporting Issues
> >> >> >> >> > ================
> >> >> >> >> > The KiCad developers are working hard to provide
> >> quality, binary
> >> >> >> >> > releases to
> >> >> >> >> > our users. As of September 2014, the OS X package
> >> is under heavy,
> >> >> >> >> > active
> >> >> >> >> > development.
> >> >> >> >> >
> >> >> >> >> > If you encounter issues with this software, please
> >> report a bug at
> >> >> >> >> > https://bugs.launchpad.net/kicad <https://bugs.launchpad.net/kicad>.
> >> >> >> >> >
> >> >> >> >> > To help us, please include the details from "About
> >> This Build" in
> >> >> >> >> > this
> >> >> >> >> > file
> >> >> >> >> > or the name of the download file (kicad-r*.dmg).
> >> Please also
> >> >> >> >> > include
> >> >> >> >> > the
> >> >> >> >> > output from running the following command in the
> >> Terminal:
> >> >> >> >> >
> >> >> >> >> > sw_vers
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > About This Build
> >> >> >> >> > ================
> >> >> >> >> > KiCad revision: r5237
> >> >> >> >> > Packaged on 20143010-034759
> >> >> >> >> > Packaging script revision: r20
> >> >> >> >> > Build script revision: r20
> >> >> >> >> > CMake Settings: -DCMAKE_C_COMPILER=/usr/bin/clang
> >> >> >> >> > -DCMAKE_CXX_COMPILER=/usr/bin/clang++
> >> >> >> >> > -DwxWidgets_CONFIG_EXECUTABLE=../wx-bin/bin/wx-config
> >> >> >> >> > -DKICAD_SCRIPTING=OFF
> >> >> >> >> > -DKICAD_SCRIPTING_MODULES=OFF
> >> -DKICAD_SCRIPTING_WXPYTHON=OFF
> >> >> >> >> > -DCMAKE_INSTALL_PREFIX=../bin
> >> -DCMAKE_BUILD_TYPE=Release
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > QA/Testing:
> >> >> >> >> > At the moment, I have set up another OS X machine
> >> running a
> >> >> >> >> > freshly
> >> >> >> >> > installed 10.10. I haven't installed anything
> >> else, and I am
> >> >> >> >> > testing
> >> >> >> >> > the
> >> >> >> >> > Kicad packages on there, and then once I have
> >> tested them, I am
> >> >> >> >> > reverting
> >> >> >> >> > the system back to the state as it was "freshly
> >> installed." This
> >> >> >> >> > is
> >> >> >> >> > not
> >> >> >> >> > ideal at all, but every day these packages aren't
> >> available is
> >> >> >> >> > another
> >> >> >> >> > day I
> >> >> >> >> > spend 20 minutes replying to people asking me where
> >> Mac builds are
> >> >> >> >> > :)
> >> >> >> >> >
> >> >> >> >> > What's Left:
> >> >> >> >> >
> >> >> >> >> > * Automated uploads to the website. I poked Miguel
> >> about this
> >> >> >> >> > recently,
> >> >> >> >> > and
> >> >> >> >> > he says he'll try to get to it today.
> >> >> >> >> >
> >> >> >> >> > * The current Mac build appears to have some
> >> dependencies beyond
> >> >> >> >> > what
> >> >> >> >> > we
> >> >> >> >> > include in the bundle. For example, on a freshly
> >> installed 10.10
> >> >> >> >> > system
> >> >> >> >> > with this bundle, I cannot open pcbnew. I verified
> >> this myself.
> >> >> >> >> > A
> >> >> >> >> > tester
> >> >> >> >> > reported to me that he was able to fix it by
> >> installing brew,
> >> >> >> >> > libpng,
> >> >> >> >> > libpixman, and libfontconfig. I have not verified
> >> that fix yet.
> >> >> >> >> >
> >> >> >> >> > The error is: 06:53:16:
> >> >> >> >> > dlopen(/Volumes/Contents/PlugIns/_pcbnew.kiface,
> >> >> >> >> > 10): image not found
> >> >> >> >> > 06:53:16: IO_ERROR: Fatal Installation Bug
> >> >> >> >> > missing file:
> >> >> >> >> > '/Volumes/Contents/PlugIns/_pcbnew.kiface'
> >> >> >> >> >
> >> >> >> >> > argv[0]:
> >> >> >> >> > '/Volumes/Kicad/Kicad/pcbnew.app/Contents/MacOS/pcbnew'
> >> >> >> >> > from
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> >
> >> /Users/jenkins/remoteroot/workspace/KiCadMacBuild/kicad/common/kiway.cpp
> >> >> >> >> > :
> >> >> >> >> > KiFACE() : line 219
> >> >> >> >> > It appears that it is looking for
> >> Contents/PlugIns/_pcbnew.kiface
> >> >> >> >> > at
> >> >> >> >> > the
> >> >> >> >> > wrong place, and I am not sure why installing those
> >> libraries
> >> >> >> >> > would
> >> >> >> >> > fix
> >> >> >> >> > that
> >> >> >> >> > problem. I am going to pull this out into its own
> >> email so
> >> >> >> >> > discussion
> >> >> >> >> > of
> >> >> >> >> > this doesn't get merged with other nightly build
> >> questions.
> >> >> >> >> >
> >> >> >> >> > * Including libraries? Not sure about this one.
> >> >> >> >> >
> >> >> >> >> > What has been done:
> >> >> >> >> >
> >> >> >> >> > * We redid our build cluster in a way that we could
> >> let in other
> >> >> >> >> > people,
> >> >> >> >> > and
> >> >> >> >> > not see the rest of the Wayne and Layne internal
> >> projects. I hope
> >> >> >> >> > to
> >> >> >> >> > get
> >> >> >> >> > some more people in the packaging group, and this
> >> was a crucial
> >> >> >> >> > first
> >> >> >> >> > step.
> >> >> >> >> >
> >> >> >> >> > * We have an OS X machine for building, and an OS X
> >> machine for
> >> >> >> >> > testing,
> >> >> >> >> > and
> >> >> >> >> > can restore it to the "freshly installed" state
> >> very easily.
> >> >> >> >> >
> >> >> >> >> > Thanks,
> >> >> >> >> >
> >> >> >> >> > Adam Wolf
> >> >> >> >> > Cofounder and Engineer
> >> >> >> >> >
> >> >> >> >> > _______________________________________________
> >> >> >> >> > Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> >> >> >> >> > Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> >> <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>>
> >> >> >> >> > Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> >> >> >> >> > More help : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
> >> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >
> >> >> >
> >> >
> >> >
> >>
> >>
> >> _______________________________________________
> >> Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> >> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> >> <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>>
> >> Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> >> More help : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
> >
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> > Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> > Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> > More help : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
> >
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> More help : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
>
> _______________________________________________
> 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
Follow ups
References
-
OS X Packaging Update
From: Adam Wolf, 2014-10-30
-
Re: OS X Packaging Update
From: Nick Østergaard, 2014-12-23
-
Re: OS X Packaging Update
From: Adam Wolf, 2014-12-23
-
Re: OS X Packaging Update
From: Nick Østergaard, 2014-12-23
-
Re: OS X Packaging Update
From: Adam Wolf, 2014-12-23
-
Re: OS X Packaging Update
From: Nick Østergaard, 2014-12-23
-
Re: OS X Packaging Update
From: Adam Wolf, 2014-12-23
-
Re: OS X Packaging Update
From: Nick Østergaard, 2014-12-23
-
Re: OS X Packaging Update
From: Adam Wolf, 2014-12-23
-
Re: OS X Packaging Update
From: Martijn Kuipers, 2014-12-23
-
Re: OS X Packaging Update
From: Adam Wolf, 2014-12-23
-
Re: OS X Packaging Update
From: Wayne Stambaugh, 2015-01-06
-
Re: OS X Packaging Update
From: Adam Wolf, 2015-01-06
