Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

[Windows] precompiled wxWidgets in next release

(1/7) > >>

inventore123:
First of all thanks for this great IDE  8)

I think the Windows release is great, but installing wxWidgets is somewhat complicated. The wxPack is good, but *huge*, it takes up more than 2 GBytes... the wxMsw is smaller, but compiling it is a bit difficult and takes time...
It would be great if the next release come with wxWidgets precompiles as well as MinGw.

Therefore I made a precompiled version of wxWidgets (based on wxMsw) that you can download here http://www.webalice.it/fede.tft/codeblocks/wxWidgets-2.8-%28Compiled%29.zip. It has the following advantages:

- It comes with a Readme.txt that explains how it has been compiled, how to install it, and how to test if it has been installed correctly.
- It is *small*, the zip file is less than 10MB, and once extracted it is only 40MB
- It is compiled as static library, so the .exe files don't require any .dll

I have 3 questions:
1) Is there a chance that this or another precompiled version of wx will be included in the next release?
2) (This seems to be a C::B bug) when I try to make a new project, it does not compile because it does not link by default with libwxjpej.a and libwxtiff.a, but after adding those libs to Project>Build Options>Release>Linker Settings>Link Libraries everything works fine.
3) When compiling wxMsw the folder must be in a path without spaces, but in theory oce compiled there should be no problem in moving the folder to a location with spaces (for example C:\Program files\CodeBlocks\  :D ) however it doesn't work. Any idea? is this a bug of wxWidgets or C::B?

killerbot:
we do offer the wx dll though. You can download it from the nightly build, and it is included in the official release. We do however do NOT distribute wxWidgets.

dje:
Well, it is nice BUT
- MinGW is one of the 15 C::B supported compilers
- You provide one of the 16 wxWidgets configurations (BUILD=release/debug SHARED=0/1 MONOLITHIC=0/1 UNICODE=1/1)

I think it is too specific, it is a nice contrib if people use your configuration, you may provide a link to it in the wiki.
Compiling wxWidgets is not so complicated...

Dje

inventore123:

--- Quote ---- MinGW is one of the 15 C::B supported compilers
--- End quote ---
It is true, but there are 2 version of wxwidgets for Windows one with mingw and one without it, just include a precompiled wx only in the mingw release :)

--- Quote ---I think it is too specific
--- End quote ---
You're right about that, maybe i can compile it in those options:
static, non monolithic, unicode (release & debug)
dll, monolithic, unicode (release & debug)

This is a total of 4 builds. Or if you have a better combination, let me know.

Alexis:

--- Quote ---Compiling wxWidgets is not so complicated...
--- End quote ---
It's easy when... you know (as I do). For a newbie, it's difficult. Think about beginners !

Just imagine: you're a beginner and you install a full-bundled Code::Blocks. Then you create a project with the wizard, you compile/link, and your exe starts ! Everything would be so easy and straightforward !
Just look at the number of people in this forum that try to compile wxWidgets, or install C::B and don't know how to link their exe based on wx. Some of them are discouraged and don't go farther.

That's why I think C::B should be released as two "bundles" :
- a single bundle : C::B only (not wuth even MinGW under Windows)
- a full bundle : C::B + MingGW + wxWidgets (the 4 configurations already described)

I think that shipping a full-bundled Code::Blocks would do a lot for promoting wxWidgets and C::B.

Kind regards,

Navigation

[0] Message Index

[#] Next page