Developer forums (C::B DEVELOPMENT STRICTLY!) > Contributions to C::B

wxWidget with codeblocks problem

<< < (9/10) > >>

Miguel Gimenez:

--- Quote from: BlueHazzard on April 07, 2017, 12:48:58 am ---If you still have the problem: http://forums.codeblocks.org/index.php/topic,21867.0.html

--- End quote ---

BlueHazzard, there is a typo in your comprehensive guide that should be edited in order to avoid future problems: -fno-keep-inlline-dllex should be -fno-keep-inlline-dllexport

BlueHazzard:
fixed it, but this should go to the wiki...

gtafan:

--- Quote from: BlueHazzard on April 07, 2017, 12:48:58 am ---
--- Quote ---Thanks, have already apolgies, was really not my goal to troll somebody here. At least somebody understands how hard is to comunicate in a language that´s not yours.
--- End quote ---
Honestly? tim wanted to know your filenames and you refuse since x posts to give them. And we told you 10 times that in the post you showed the files there are some missing.

If you still have the problem: http://forums.codeblocks.org/index.php/topic,21867.0.html
if this does not help, answer the questions (filenames, error messages...) otherwise i will, like tim, refuse to help you (because i can't help you without information from your side)...

--- End quote ---
Which filenames? I have posted all filenames generated after building in post #6. If he meaned other filenemes, I asked him which ones, but instead of answering that he called me a troll.
I have to stres out once again, that I have problems with the US language and I also never had to build anithing on comandline, so not familiar with that stuff. For me personal there is no much diference between comandline and bat file, as bat file is just a tool making worcking with comandline easier.
However that CXXFLAGS="-fno-keep-inlline-dllexport -std=gnu++11" was not in the wiki I read, the exact comandline from that wiki you can see in post #2. So will se if adding that stuff to that comandline will solve the problem.

BlueHazzard:
Ok, one last time:
In post #6:

--- Quote ---Here the path:

but it can´t be the problem, because wrong path would show an error mesage just after this dialog.
My options look like that:

Just for fun have tried all posible combinations, but always got exactlly the same error.

The lib folder looks like that:
and the gcc_lib:

Posibly some .a files are mising?

--- End quote ---
you posted a image with the files:

--- Code: ---libwxexpat.a
libwxjpeg.a
libwxpng.a
libwxregexu.a
libwxsintilla.a
libwxtiff.a
libwxzlib.a

--- End code ---
Now we told you like 1000 times that your wxWidgets build failed and for this you are missing some libraries:

--- Quote ---There are two missing libraries, libwxmsw30u.a and libwxmsw30u_gl.a.

You should call again the compilation command and look for compilation errors (one frequent error with monolithic builds is related to memory starvation in ld).
--- End quote ---
after this nothing productive happened... You whined about how complicated all this is, we whined how you can not simply post the error messages you get. After this we thought you have successfully build wxWidgets and so we asked if you can post the filenames again, but you told us that you have posted them in #6 and we told you that this is not the case and so on and so on... BlaBlaBlaBla...

Simply follow the steps from the other link and if you hit a error post a screenshot of the error here....

gtafan:
Problem solved, it was all because of wrong comandline, the corect one is:

mingw32-make -f makefile.gcc BUILD=release MONOLITHIC=1 UNICODE=1 SHARED=0 CXXFLAGS="-std=gnu++11 -fno-keep-inline-dllexport"

Navigation

[0] Message Index

[#] Next page

[*] Previous page