Thanks Nick for sorting out all the build issues on Windows - it would have taken much longer without all your work.
- Cirilo On Wed, Sep 7, 2016 at 6:31 PM, Nick Østergaard <[email protected]> wrote: > FYI the windows nightlies now built with OCE enabled. The first > nightlies are ready and my sanity check says that it works. As I write > this only the x86_64 build have it enabled, but I expect the i686 > build to be ready within a few hours from now on. > > I know that js-reynaud also enabled it on the ubunut PPA's. > > I don't know what the status for getting OSX nightlies running again is. > > So all in all this is good news. Lets see if we get any new bug > reports on its usage now. :) > > Cirilo and Mario (and others), thank you for making this feature a reality. > > 2016-09-03 2:18 GMT+02:00 Cirilo Bernardo <[email protected]>: > > > > > > On Sat, Sep 3, 2016 at 5:25 AM, Wayne Stambaugh <[email protected]> > > wrote: > >> > >> Cirilo, > >> > >> Someone still needs to address building oce on msys2. I just spent way > >> too much time building oce from source on msys2. The oce folks decided > >> to ignore CMAKE_INSTALL_PREFIX and use there own install path stuff > >> which is is not compatible with the msys2 file system hierarchy. The > >> bad thing is you cannot manually copy the dlls and link stub files to > >> the appropriate paths because the generated cmake oce find stuff will > >> point to the incorrect paths. To create PKGBUILD for msys2 will require > >> JP's patch to fix long command lengths along with a patch to fix oce's > >> install path issues. If someone else has time to work on this please > do. > >> > >> Thanks, > >> > >> Wayne > >> > > > > Nick's been doing all the hard work on OCE + MSYS2 issues; I'm pretty > > awful at working within MSYS2 and it doesn't help that the MSYS2 > > ecosystem is frequently broken. I was finally able to build OCE and > > the plugins on MSYS2 about a week ago only to discover catastrophic ABI > > incompatibilities between wxWidgets and the newly compiled software. > > I have no doubt these issues will be resolved before the next release > > thank's to Nick's persistence, and I keep in touch on IRC and try to > > help out however I can. Having the code in the main branch is a huge > > help though; some OSX devs in particular had been cursing me due to > > numerous problems with building the plugin out of the tree but building > > the same code from within the kicad tree was painless. > > > > - Cirilo > > > >> > >> On 9/2/2016 6:22 AM, Cirilo Bernardo wrote: > >> > Thanks for the merge and to everyone who's helped out with the > >> > cross-platform issues. > >> > I've got a new feature branch "kicad-step" with the kicad2step > >> > standalone tool if anyone > >> > feels like playing with it and providing some feedback. This is the > >> > tool which I plan to > >> > make available as an item in the "Export" menu to give KiCad it's own > >> > built-in MCAD > >> > export. > >> > > >> > https://code.launchpad.net/~cirilo-bernardo/kicad/+git/kicad-oce > >> > > >> > The long-term plan is to make this tool a genuine plugin, but the API > >> > required for that > >> > is turning out to be quite a big job and is currently on hold due to > my > >> > limited free time. > >> > > >> > This stand-alone tool makes use of mRoszko's SEXPR parser which is a > >> > great tool > >> > for making third-party tools that can read KiCad PCB files. > >> > > >> > - Cirilo > <snip> >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
