Buster wx3.1: wx-config doesn't find configuration info

CodeLite installation/troubleshooting forum
mdjurfeldt
CodeLite Curious
Posts: 2
Joined: Fri Jan 24, 2020 1:30 am
Genuine User: Yes
IDE Question: C++
Contact:

Buster wx3.1: wx-config doesn't find configuration info

Post by mdjurfeldt » Fri Jan 24, 2020 1:39 am

Hi,

I have followed the instructions here:

https://wiki.codelite.org/pmwiki.php/Ma ... 31Binaries

for installing wx3.1.3 on Debian Buster.

However, if I then do

wx-config --libs

I get:

Warning: No config found to match: /usr/bin/wx-config --libs ...

CMake FindPackage also seems to conclude that no wx libraries are installed.

Can you advise what could be wrong?

Best regards,
Mikael

DavidGH
CodeLite Plugin
Posts: 642
Joined: Wed Sep 03, 2008 7:26 pm
Contact:

Re: Buster wx3.1: wx-config doesn't find configuration info

Post by DavidGH » Fri Jan 24, 2020 2:06 am

Hi,

Which packages did you install? Did you install the -dev packages too? If not, you need to do so for building wx programs.
Did apt complain, or did the installing seem to go OK?

What is the result of doing, in a terminal,

Code: Select all

sudo update-alternatives --list wx-config
Regards,

David

mdjurfeldt
CodeLite Curious
Posts: 2
Joined: Fri Jan 24, 2020 1:30 am
Genuine User: Yes
IDE Question: C++
Contact:

Re: Buster wx3.1: wx-config doesn't find configuration info

Post by mdjurfeldt » Fri May 01, 2020 12:49 am

Hi,

Sorry for the long delay.

I did install the -dev packages and wx-config was correctly configured to the alternative I wanted.

I did some debugging myself and discovered that the codelite packages for Debian buster assume that grep is at /usr/bin/grep, but in Buster it is in fact at /bin/grep. This caused the wx-config malfunction and editing the wx-config script fixed my problem.

Best regards,
Mikael

DavidGH
CodeLite Plugin
Posts: 642
Joined: Wed Sep 03, 2008 7:26 pm
Contact:

Re: Buster wx3.1: wx-config doesn't find configuration info

Post by DavidGH » Fri May 01, 2020 1:10 am

Sorry for the long delay.
What's 3 months between friends ;) .
I did some debugging myself and discovered that the codelite packages for Debian buster assume that grep is at /usr/bin/grep, but in Buster it is in fact at /bin/grep.
I can see that would account for your problem. However I use buster too and, for me, /bin/ is a symlink to /usr/bin/. That's also true for a virtualbox guest buster. And, assuming I understand this link correctly, that's what should have happened.

Anyway, I'm glad you have it sorted out.

Post Reply