This bug records the build problem originally reported in bug# 260397 comment #5. I'm opening this because I ran into the same problem and thought it might be helpful to record my solution somewhere that anyone else running into the same problem might find it. The error message encountered during build was: -- Check for installed wxWidgets -- not found CMake Error at CMakeModules/CheckFindPackageResult.cmake:6 (message): wxWidgets was not found - it is required to build Kicad On my system this was cured by selecting a wxwidget set using eselect. Since I don't have any other programs installed using wxwindows, I had never selected the widget set to use. I just did "eselect wxwidgets list" to find the list of options available and "eselect wxwidets set <n>" to select the one that seemed best to me.
(In reply to comment #0) > On my system this was cured by selecting a wxwidget set using eselect. Thanks for your report. Which one did you select ? Ryan, Mart: I've added the wx in CC as you can see. I believe this is not the first time we're told about this but I have no clue what it could be. I'll try and dig the other bug report(s) that seem similar to me. In the meantime, do you have any idea ? Denis.
I think a check for a selected gtk2-unicode-release-2.8 in the wxwidgets profile inside a pkg_setup block can be a workaround. And also, firing an eerror if the profile is not selected.
I reported bug# 260397 comment #5. Probably I should have started a new bug - my apologies. The solution in comment #0 works for me: # eselect wxwidgets list Available wxWidgets profiles: [1] gtk2-ansi-release-2.6 [2] gtk2-unicode-release-2.6 [3] gtk2-unicode-release-2.8 # eselect wxwidgets set 3 Setting wxWidgets profile to gtk2-unicode-release-2 Following which kicad compliled with no problems, and works well.
My bad. I switched the ebuild to EAPI2 and the need-wxwidgets statement got lost. I have fixed that and even made more use of EAPI2 features. For your information, ebuilds should not need that you set a wxwidget profile with eselect. If they do it means there's a problem. Profiles are only when using wxGTK outside of your package manager. Some apps will require 2.6 and others 2.8 for example. And we just can't afford relying on the user setting the proper profile prior to emerging the package. That would be too cumbersome for you guys. So the eclass takes care of this, but if you don't call the proper function when you should, well... you know what happens now. I haven't revbumped the ebuild as it is not necessary in such a situation. In case you'd want to verify it works just set a 2.6 profile and emerge kicad. The ebuild will pick up wxGTK-2.8 and build kicad against it and it should all work. Denis.
Thanks for a fast fix.
Worked for me. I'd also like to say thank you for the fix and for the detailed explanation. It definitely helped me to better understand what is supposed to happen when packages are built.
