Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Bootstrap with no wxWidgets packet installed
oBFusCATed:
--- Quote from: ollydbg on August 15, 2018, 03:39:02 am ---Now, I can use C::B to debug. So, this looks like a GCC optimization bug? ;)
--- End quote ---
Hehe, it is so easy to blame the compiler for hard to explain bugs.
GCC is rarely to blame when there are race conditions or other threading bugs...
oBFusCATed:
Can you try to build wx from the wx_3_0_branch and see if the problem reproduces?
oBFusCATed:
I've just tried to reproduce your setup and debugging works fine when starting cb from terminal.
ollydbg:
--- Quote from: oBFusCATed on August 15, 2018, 07:30:50 am ---Can you try to build wx from the wx_3_0_branch and see if the problem reproduces?
--- End quote ---
OK, I will do this soon.
Do I only need to build the wx_3_0_branch library, and use the previous built C::B? I mean I can use the
--- Code: ---export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/somewhere/wx/library/installed
./codeblocks --multiply-instance --no-ipc &
--- End code ---
to let C::B pick the wx library.
I have a question, if I have several wx library, such as:
--- Code: ---/home/zyh/code/wx3install release version of wx 3.1.1 library
/home/zyh/code/wx3install-debug debug version of wx 3.1.1 library
/home/zyh/code/wx30install release version of wx 3.0 branch library
--- End code ---
How do I adjust the wx-config?
In my previous post, I have to run the command:
--- Code: ---update-alternatives --install /usr/bin/wx-config wx-config /home/zyh/code/wx3install/bin/wx-config 50
--- End code ---
which point the wx-config to the wx library before I run the bootstrap command.
I mean, I have to run the update-alternatives command before I build a new C::B?
oBFusCATed:
It is better to rebuild the whole codeblocks.
For the wx-config check the help of the cb's configure script. There is an option which allows you to select the exact binary you want to use.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version