Code::Blocks
Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: tomay3000 on February 07, 2019, 09:40:49 am
-
Hello,
I have successfully compiled CB SVN 11562 32 bit via Mingw-w64 gcc v7.4.0. When I try launch CB, it fails to load wxSmith.dll plugin.
What could be the problem?
Is it possible that strip.exe corrupted it!
Are the 32 bit *.cbp and *.workspace files updated?
Also the svn number is displayed as 0 in the about dialog or splash screen.
NB: I use wxWidgets v3.1.2
Thank you in advance.
-
Did you load the workspace and click the "Build workspace" menu option?. Clicking the yellow gear only builds the active project. Make sure the selected target is "All".
When the workspace is built you must open a console, move to (cbfolder)\src and execute update31.bat (or update30.bat or update.bat, depending on the wxWidgets version used).
-
it is working now,
I had to add wxWidgets bin folder to the Path environment.
Whereas the svn number is still 0.
-
Please note that there are two known bugs in Code Completion with wx3.1.2 in MSW; one make C::B crash and the other makes the caret invisible.
There is a temporary patch for C::B here:
http://forums.codeblocks.org/index.php/topic,22974.msg156799.html#msg156799 (http://forums.codeblocks.org/index.php/topic,22974.msg156799.html#msg156799)
Or a patch for wx3.1.2 here:
http://forums.codeblocks.org/index.php/topic,22974.msg156992.html#msg156992 (http://forums.codeblocks.org/index.php/topic,22974.msg156992.html#msg156992)
You can use one or the other. The second is the "official" patch for the issue, backported from wxWidgets trunk, and will be active in wx3.1.3
Did you get the source via SVN or as a zip? The latter would explain SVN 0
-
Thank you for the info ;).
I just became wondering why I am getting C::B crashing.
I get C::B source via SVN.
-
The svn command must be in the path used by C::B or you get a zero SVN.
Tim S.
-
Could you please explain what do you mean!
Because I have downloaded C::B via MSYS2 MinGW 32-bit using the following command:
svn checkout svn://svn.code.sf.net/p/codeblocks/code/trunk
Then compiled it as usual.
Then copied the content of "trunk\src\output31" to "C:\Program Files\CodeBlocks" directory.
I tried copying "svn.exe" from "C:\msys32\usr\bin" to "C:\Program Files\CodeBlocks".
I also tried copying the global ".subversion" and "trunk\.svn" to C::B installation directory without success.
So please explain it a little bit more.
Thank you in advance.
-
Before building codeblocks the buildprocess tries to figure out what version of codeblocks you use. This is done by calling svn in a prebuild step. So you have to have svn in the path during compiling.
How do you compile "as usual" by using codeblocks, or by using configure && make ? If you use the later from the msys2 console it should work. (disclaimer: this version numbering never worked for me and i have no interest in it so i do not look why it does not work...)
-
I use C::B to build C::B
After I switched Mingw-W64 to SJLJ for exceptions and Win32 for threads, all is working as expected now.
You should avoid Dwarf exception model and Posix Thread model for better compatibility.
Not just for C::B but it helped me get rid of many crashes during xwWidgets development.