Re: [Kicad-developers] wxwidgets fork progress

Yes, this needs to be fixed. On 02/12/2018 07:04 PM, Michael Kavanagh wrote: I think the docs need to be updated to reflect these changes: http://docs.kicad-pcb.org/doxygen/md_Documentation_development_compiling.html#build_osx Cheers, Michael On 31 January 2018 at 15:24, Wayne Stambaugh

Re: [Kicad-developers] wxwidgets fork progress

I think the docs need to be updated to reflect these changes: http://docs.kicad-pcb.org/doxygen/md_Documentation_development_compiling.html#build_osx Cheers, Michael On 31 January 2018 at 15:24, Wayne Stambaugh wrote: > OK, these patches have be reduced to historical

Re: [Kicad-developers] wxwidgets fork progress

OK, these patches have be reduced to historical footnotes. Thanks everyone for the feedback. Cheers, Wayne On 1/30/2018 5:04 PM, Adam Wolf wrote: > You can remove the boost patches. They are only of historical > concern, and they'll live in Git for any future archaeologist who > cares. > >

Re: [Kicad-developers] wxwidgets fork progress

You can remove the boost patches. They are only of historical concern, and they'll live in Git for any future archaeologist who cares. Adam On Tue, Jan 30, 2018 at 3:20 PM, Jeff Young wrote: > Yeah, I didn’t patch my boost either. (I can’t remember if I MacPorts’d it > or

Re: [Kicad-developers] wxwidgets fork progress

Yeah, I didn’t patch my boost either. (I can’t remember if I MacPorts’d it or Homebrew’d it, but I didn’t do anything beyond that.) > On 30 Jan 2018, at 21:13, Bernhard Stegmaier wrote: > > Wayne, > > I don’t think so. > > I use a stock MacPorts boost since long

Re: [Kicad-developers] wxwidgets fork progress

Wayne, I don’t think so. I use a stock MacPorts boost since long before you removed boost from KiCad build. This might not be representative, but I didn’t see any problems. I had a quick look into Adams build scripts and I didn’t see that he is building his own boost (with the patches)

Re: [Kicad-developers] wxwidgets fork progress

That patch may be needed to build on older macOS versions and older targets. I am not worried about removing it--it hasn't been in builds for a long time. Good work Bernhard. Adam On Jan 29, 2018 12:11 PM, "Bernhard Stegmaier" wrote: > The full original soname patch

Re: [Kicad-developers] wxwidgets fork progress

Wayne, yes, from my side you can delete them. Even if deleted they are in git anyway, so we can restore them if really needed. I’ll try to change documentation ASAP. Regards, Bernhard > On 29. Jan 2018, at 19:15, Wayne Stambaugh wrote: > > Bernhard, > > Am I safe

Re: [Kicad-developers] wxwidgets fork progress

Bernhard, Am I safe deleting the macos patches from the source repo or do I need to hold off until the dust has settle on the new wx repo? Thanks, Wayne On 1/29/2018 1:11 PM, Bernhard Stegmaier wrote: > The full original soname patch seems to fix the issue in my builds (I > did apply only half

Re: [Kicad-developers] wxwidgets fork progress

The full original soname patch seems to fix the issue in my builds (I did apply only half of it to our fork because of the comments in wxWidgets trac). I pushed it to the fork. The next build should pick it up automatically and be good again… sorry for not having checked this before. I also did

Re: [Kicad-developers] wxwidgets fork progress

Just a short status… I just tried the compile_wx.sh script and it generally seems to be fine. But, I can see that obviously the wxPython installer duplicates libs instead of symlinking them. Maybe the original soname patch we had is needed for that one to work correctly. I’ll check… Regards,

Re: [Kicad-developers] wxwidgets fork progress

I think I see it now. I can probably fix this tonight. Thanks! Adam On Jan 28, 2018 5:30 PM, "Bernhard Stegmaier" wrote: > Quick look into the build… seems to pull in wrong wxWidgets libs. > The build in question includes some 3.0.0 wxWidgets libraries which I >

Re: [Kicad-developers] wxwidgets fork progress

Yeah. The previous build script downloaded a wxpython tarball, which included wxwidgets. All my update did was move the wxpython subdirectory into a git checkout of the wxwidgets tree, and build that way. One quick thing would be to just do a diff between the wxwidgets included with wxpython

Re: [Kicad-developers] wxwidgets fork progress

Sure. I’ll have a look tomorrow and try to build wxWidgets/wxPython the same way the script does. > On 28. Jan 2018, at 23:44, Nick Østergaard wrote: > > You don't need to revert it. I can just choose the latest workin hash in the > jenkins job. I would rather we fix it

Re: [Kicad-developers] wxwidgets fork progress

That seems to be the same error as when the former so-name patch was not applied and original wxWidgets build stuff rewrites library names. The bundle is corrupt then, because the bundling code fails to create symlinks and copies libs instead multiple times. If you can send me where to find the

Re: [Kicad-developers] wxwidgets fork progress

You don't need to revert it. I can just choose the latest workin hash in the jenkins job. I would rather we fix it somehow. :) @Bernhard, the build scripts in question are https://github.com/wayneandlayne/KiCadMacOSPackaging Maybe you can have a got at it? 2018-01-28 23:41 GMT+01:00 Nick

Re: [Kicad-developers] wxwidgets fork progress

Which bug? Bernhard > On 28. Jan 2018, at 23:14, Adam Wolf wrote: > > I was able to get the wxwidgets stuff switched over but there's a bug in the > big tracker saying it didn't work. I will continue to look into it as I can. > I should be over this illness

Re: [Kicad-developers] wxwidgets fork progress

I assume this is the bug you are talking about: https://bugs.launchpad.net/kicad/+bug/1745868 2018-01-28 23:14 GMT+01:00 Adam Wolf : > I was able to get the wxwidgets stuff switched over but there's a bug in > the big tracker saying it didn't work. I will continue

[Kicad-developers] wxwidgets fork progress

I was able to get the wxwidgets stuff switched over but there's a bug in the big tracker saying it didn't work. I will continue to look into it as I can. I should be over this illness by the end of this week, it looks like. I can revert the packaging change so the next builds will work again.