User forums > Using Code::Blocks

Get wxWidgets 3.0 to work on C::B, Win7

(1/7) > >>

thor36:
Hello everyone ! It's my first post here, and great to see such a lively community of C::B users.

I am fairly new to programming in C++, and totally new to using 3rd party libraries, so please have patience and don't mind my silly questions  :) Today I have been trying to set up wxWidgets for use with C::B, with no success. I am using Win 7, 64 bit. I downloaded the latest version of C::B ( codeblocks-13.12mingw-setup.exe ), and the latest wxWidgets 3.0 package ( wxMSW-3.0.0_gcc471TDM_x64_ReleaseDLL.7z ) and installed both. I tried to follow the guide on this page : http://wiki.wxwidgets.org/CodeBlocks_Setup_Guide
I followed steps and did what it said, but honestly, I had no idea what was going on, because I have never before compiled a library. Nor do I know what these steps mean and what they do. I ended up with trying to run a basic wxWidget 3.0 project on C::B, but ( surprisingly !  ;D ) it didn't work, because of missing files / headers.

During the process of following the guide, I believe I have messed things up. Therefore, I would like to clean up the mess first. And then, hopefully with your help, set things up and running as they should be. I would greatly appreciate your guidance through the process, and if possible also an explanation of what the single steps are. It would benefit me greatly in my learning process, and probably to others with similar issues as well !  :)
Thank you very much, and keep up the great work with the forum  :)

stahta01:
Read the stuff on this link http://wiki.codeblocks.org/index.php?title=WxWindowsQuickRef

After glancing at that link it will be clear that you need to build wxWidgets or download a pre-built wxWidgets.
(Finding a correct pre-built wxWidgets 3.0 seems to be challenging at this time; found one with no info on which compiler
it is valid for and at 900 MB its to build for me to check.)

Have you decided on the Compiler you are going to be using?

Your prior post implied MinGW GCC; but, it was NOT clear to me if that was a decision on your part.

Tim S.

thor36:
Thank you for your answer.

I will try to follow the instructions of your provided link. But most likely I still won't understand the process, and can repeat same mistakes again. Besides, I am afraid I have already made some "damage" during the setup, that can negatively affect my next attempt.

I didn't make any decision on Compiler. It seems C::B comes with MinGW GCC, so that sounds like a reasonable choice. If there are any big differences or considerations I should take, please don't save words. I have much to learn, and I have just started  :)

stahta01:

--- Quote from: thor36 on February 01, 2014, 01:46:05 am ---Thank you for your answer.

I will try to follow the instructions of your provided link. But most likely I still won't understand the process, and can repeat same mistakes again. Besides, I am afraid I have already made some "damage" during the setup, that can negatively affect my next attempt.

I didn't make any decision on Compiler. It seems C::B comes with MinGW GCC, so that sounds like a reasonable choice. If there are any big differences or considerations I should take, please don't save words. I have much to learn, and I have just started  :)

--- End quote ---

Other than wasting time and hard-disk space I know of no reason not to use "MinGW GCC".
(The waste happens if you decide to change versions or makes of compilers.)

When using Code::Blocks MinGW GCC is the normal choose for Windows users; but, MinGW GCC has many different versions to pick from.

Building wxWidgets on my slow 32 bit computer takes 2 hours and about 2 gigs of hard-drive space.

If you download a pre-built wxWidgets the compiler version needs to be an almost prefect match for it to work with your compiler selection.

Tim S.

thor36:
Can you please point me to location of pre-built wxWidgets ? Is it a shortcut that can save me of the problems I am having with building ?
What procedure do I need to take, if it is different from the one on your link ?

Navigation

[0] Message Index

[#] Next page