Bug #17
gr-wxgui configure doesn't fail when wx not present
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Johnathan Corgan | % Done: | 0% |
|
| Category: | build | |||
| Target version: | release-3.0 | |||
| Resolution: | fixed |
Description
On a virgin machine without wxwindows or wxpython, the configure process for gr-wxgui goes ahead even though things won't work when its done.
History
Updated by Johnathan Corgan almost 7 years ago
I noted in the grc_gr_wxgui.m4 file whether we should check this or not. Technically, it's not a compile time requirement as there is no compilation done in gr-wxgui.
I think runtime requirements should be checked at runtime. YMMV.
Updated by Matt Ettus almost 7 years ago
I think that it should refuse to configure and install gr-wxgui if wx isn't there. Otherwise everything looks ok, and then you get an error message when you try to run anything. I don't know about you, but I'm tired of answering the "No module named wx" question on the mailing list.
Updated by Johnathan Corgan almost 7 years ago
- Status changed from New to Assigned
Ok, fair enough. I'll accept the ticket.
Updated by Johnathan Corgan almost 7 years ago
- Status changed from Assigned to Closed
- Resolution set to fixed
Fixed in 3221. gr-wxgui will not get installed if wxPython is not detected at configuration time. However, this just shifts the error message to scripts that are trying to import from gr.wxgui.