wxWidgets Discussion Forum

As I'm sure you realised immediately after you made that post, it means that you've not installed the package that contains the python headers. That usually means a package with the ending '-dev'. If you went to the debian packages page, https://www.debian.org/distrib/packages#search_packages, and r...

Why not use the latest one? If it's good enough for VZ....

AFAIK no distro ever supplied binaries. To see what's available from the bakefile site, see https://github.com/vslavik/bakefile/releases.

From the way you phrased your question, closely following your previous topic , I think one of us misunderstands what is wanted. In that topic I suggested installing VirtualBox inside your current machine's OS. That's not a wx issue; just look at the VirtualBox site, or see what your OS provides, or...

Sorry, no idea. Cross-compiling is something I've never needed/wanted to do.

However I've seen it discussed in other threads here, so...

Install e.g. VirtualBox in your current machine. Then install e.g. debian buster (which is 'oldstable' and so still supported) into VirtualBox.
Install Bakefile inside the debian buster guest, and you're set up for years of use.

I have been able to compile, and build the minimal sample. Try copy/pasting your current wxT("Minimal wxWidgets App") into that, e.g. as wxString foo(wxT("Minimal wxWidgets App") ); and, for bonus points, also try editing away the wxT(): wxString bar("Minimal wxWidgets App&...

Did you, perhaps, copy/paste that string or a similar one from a web-page? I do sometimes see html quote-marks that look like that online.

Code: Select all

g++ -o myprog `wx-config --cxxflags --libs` mysource.cpp

Note that those are backticks (`), not commas ('). An alternative, harder-to-get-wrong, way of doing the same thing is

Since I did a shared build this is in my /usr/lib/ folder, No it isn't. wx-config --cxxflags -I/usr/ local /lib/wx/include/gtk3-unicode-3.2 wx-config --libs -L/usr/ local /lib By default, ./configure... and (sudo) make install will install to /usr/local/. I don't know about arch, but /usr/local/* i...

Hi, It seems it is some sort of linking issues. Not linking (yet). Can't find wx/wxprec.h and wx/wx.h means it's still at the compile stage. I did a shared build this is in my /usr/lib/ What is the output of doing, in a terminal: wx-config --cxxflags wx-config --libs How are you trying to compile he...

Hi,

This has the smell of a wxChar* that's pointing at a temporary char*. See for example this wxWiki page.

What happens if you change your code from
const wxChar* extension = filterBuffer.t_str();
to
wxCharBuffer extension = filterBuffer.t_str());

Regards,

David

I don't understand enough of the situation to be sure it's relevant, but have you thought of using the XRCCTRL macro?
See the XRC and IDs section of https://docs.wxwidgets.org/stable/overview_xrc.html. It's not restricted to XRC, though; it's useful elsewhere too.

Linking statically means everything is in the library/executable. You misunderstand. It means linking statically to the wx libs, not to everything. See my earlier post about a statically-linked 'minimal'. That linked dynamically to 76 libs, including libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3....

OK. Then I don't know why you have that problem, especially if it's only on one distro. However a couple of suggestions (which you've probably already tried, but still...) 1) Check (on Rocky) that the wxWidgets samples build and run, and that they find the correct wx headers and libs. You can confir...