Hi, FYI, cad/kicad* does not build with wxgtk3.2. A problem with the AddTool method for the toolbar (eeschema/sim/sim_plot_frame.cpp). I made a quick fix using wxEmptyString that seems used everywhere. BTW, I took the opportunity to update kicad-devel to the latest git commit (yesterday). I have a doubt about the latest number of GIT_SRC_DATE. Thanks, Loïc
Created attachment 236568 [details] cad/kicad: prepare to wxgtk32
Created attachment 236569 [details] cad/kicad-devel: update and prepare to wxgtk32
Thanks but no thanks. There are more issues around kicad/wxgtka3.2, which will be addressed by an upcoming release from upstream. For the time being, kicad will stick with wxgtk 3.1, I'll update that once upstream declares it ready. I certainly do not have time to support unsupported framework combinations. P.S. kicad-devel is maintained by mr@, not me.
(In reply to Christoph Moench-Tegeder from comment #3) > Thanks but no thanks. There are more issues around kicad/wxgtka3.2, which will be addressed by an upcoming release from upstream. Do you know when? AFAIK, some systems support kicad with wxgt32 > For the time being, kicad will stick with wxgtk 3.1, I'll update that once upstream declares it ready. We'd like to remove wxgtk31 :/
(In reply to Loïc Bartoletti from comment #4) > Do you know when? Next release is planned for next week (I haven't checked if all the issues have been adressed) > AFAIK, some systems support kicad with wxgt32 Maybe they like to be experimental, maybe they have someone with more spare time on their hands. > We'd like to remove wxgtk31 :/ Why don't you start with the oldest versions (there's still wxgtk28 in use)? Let projects catch up, and perhaps provide a way to actually test against 3.2 (bug #265093, comment #32 does not instill confidence) - wxgtk 3.1 branch sometimes felt like it had too many surprises for my comfort (I tried and failed...), so I'm rather reluctant to just jump ship.
(In reply to Christoph Moench-Tegeder from comment #5) > Why don't you start with the oldest versions (there's still wxgtk28 in use)? wxgtk28 will be removed soon, some ports will be updated to 30 or 32, some will be deprecated and removed. > Let projects catch up, and perhaps provide a way to actually test against 3.2 (bug #265093, comment #32 does not instill confidence) - It was my fault on b.f.o. A wrong git diff or something like, i don't remember. The exp-run passed and some ports have been tested with wxgtk32. > wxgtk 3.1 branch sometimes felt like it had too many surprises for my comfort (I tried and failed...), so I'm rather reluctant to just jump ship. as mentioned, 3.1 branch was a "development" branch, but required by some ports, so it was introduced for these ports and does not cause conflicts with 3.0. wxgtk 3.2 is the stable version and ports using 3.1 can use 3.2 - only with a cast for 2-3 ports.