User forums > Using Code::Blocks

Problems with configuration wxWidgets in C::B

<< < (2/2)

stahta01:

--- Code: ---mingw32-g++.exe -LD:\CPP\IDE\wxWidgets\lib\gcc_lib  -o bin\Release\P.exe obj\Release\PMain.o obj\Release\PApp.o  obj\Release\resource.res  -s -mthreads  -lwxmsw28u_core -lwxbase28u -lwxpng -lwxzlib -lkernel32 -luser32 -lgdi32 -lwinspool -lcomdlg32 -ladvapi32 -lshell32 -lole32 -loleaut32 -luuid -lcomctl32 -lwsock32 -lodbc32  -mwindows

--- End code ---

The above is the Link Command; The compile command(s) was not in your post.
I suggest doing a re-build of your project and posting the full compiler log of the complete build.

I also suggest linking the libraries needed.
If you do NOT wish to use the "jpeg" library for a real reason then ask how to do so at wxforum.
Else, link it to get rid of some of the linker errors.

NOTE: The libraries can fail to work if they are in the wrong order!

Tim S.

stahta01:
I suggest going to wxForum http://forums.wxwidgets.org/ and asking your question there because so far I see nothing that looks to be a Code::Blocks issue.

NOTE: Without the full compiler build log I can not be sure!

Tim S.

Tkachov:
Something has changed and now it don`t gives these errors. Few more words down there, but I don`t sure I`ve solved this problem already.


--- Quote from: stahta01 on January 22, 2012, 07:18:52 pm ---The above is the Link Command; The compile command(s) was not in your post.
I suggest doing a re-build of your project and posting the full compiler log of the complete build.
--- End quote ---

Yes, link command is the only thing that have appeared in compiler log. And this log you can see above (full in attachment, pieces in my post) is a compiler log of the complete rebuild... Wait. Really, I`ve forgotten few lines...


--- Quote from: stahta01 on January 22, 2012, 07:18:52 pm ---I also suggest linking the libraries needed.
If you do NOT wish to use the "jpeg" library for a real reason then ask how to do so at wxforum.
Else, link it to get rid of some of the linker errors.
--- End quote ---

There are no reason not to use jpeg and tiff libraries except increasing executable size. I mean, these libraries shouldn`t be used in the project, but compiler wants it to be there and so executable becomes larger.
But I`ll try to link it and rebuild project.


--- Quote from: stahta01 on January 22, 2012, 07:18:52 pm ---NOTE: The libraries can fail to work if they are in the wrong order!
--- End quote ---

In that article on wxWidgets wiki this is the reason of undefined references, but it takes no effect - same errors even if I change the order.

Also, I`ll ask about this issue on wxForum (actually, I`ve asked it in the international discussion forum - that`s why I`ve compiled wxWidgets library myself and got new problem with compiling a project using static libraries instead first one with DLLs).

______________________________________

Forget anything I`ve told. I don`t know, what have changed, but today I`ve got 21 new errors instead of 650 errors yesterday. And these errors are not about undefined references with strange names, but... I just will try to solve these by myself.

If I`ll got something about this problem again (for example, if the old ones appear again when I`ll solve new errors) - I`ll post here. And if not - I`ll post, that problem is solved.

(Also, default project still asks libwxjpeg and libwxtiff. That project I haven`t changed don`t even asks for it now.)

Guess why it don`t show old errors - these new errors are about compiling cpp-file into o-file (nothing in file has changed, but now it don`t want to be compiled =) and not about compiling executable. May be if I`ll solve these errors, I`ll got old ones again, so I`ll create this project again (it`s small enough to be recreated in few hours or even in one hour) and may be it would be allright. If not... I`ll ask about it on wxForum first =)

stahta01:
You need to learn the difference between "build" and "re-build".
This is not exactly true; but, I do NOT have time to teach basic programming and it is off topic on this site.

Build: Start where it failed last time and also do all the files that have dates newer than last time.
Re-Build: Start at the beginning and compile all the files not just ones that were modified.

It is always recommended to do a re-build after changing any project options like search directory!

Tim S.  

Tkachov:
Thanks, but I know the difference, and I`ve re-builded project every time I made some changes in project options (just I`ve copied only part with executable build log).
And, of course, I`m usually using building to apply a changes I`ve made in code.

Again, I don`t really know what happen - re-building yesterday was allright on cpp- and rc-files, but failed on compiling executable. Now there are few errors about cpp-file.

But thank you anyway.

Navigation

[0] Message Index

[*] Previous page