User forums > General (but related to Code::Blocks)

Request: Add Icon for single file compile

<< < (2/2)

grv575:

--- Quote from: doscott on September 21, 2005, 09:22:02 pm ---The only thing I don't like, and maybe you can explain why, is the requirement for a dynamic wxWidgets build with unicode, instead of allowing a static build with or without unicode. It's all easy enough to get around in Windows, but I haven't figured out how in Linux to accomodate both, and debugging with unicode is a pain.

--- End quote ---

There's no reason that a static build shouldn't work (I don't think.  I believe the wxDockit and other stuff supports both dynamic & static builds).  It's just easier to support a recommended way of doing things.  If you want to do it a different way, then by all means, however realize that it may be more difficult for people using the current wxWidgets configuration to pinpoint difficulties, etc if you are having trouble compiling something using a different configuration.  That said, it ansi (non unicode) builds definately work.  On the linux side, have you tried passing different ./configure flags for the wxWidgets compile?  (./configure --help for a list).  It might be ./configure --enable-unicode=no or ./configure --disable-unicode

Codeblocks uses wx-config to find libs and headers under linux, so any build you use of wxWidgets should be detected if wx-config points to the proper build and so it should just work (given proper wx-config setup or configuration selection... try wx-config --list if you have more than one configuration compiled).

doscott:
I guess I must have misread the requirements for a unicode build for Code::Blocks. I will eventually have to go that way, so now I'm just getting a head start  :D

Personally, I prefer static builds. Disk space is cheap and when you ship your app you know thats someone with a different set of flags and the same library name is not going to clobber you.

grv575:
Yeah but what if you use wxWidgets extensively...
and have a couple of apps that you wish to offer.

Then a library that the user must install makes sense
(MFC runtimes could have not been that much of a hassle at least in theory).

It looks much better to the customer to dl a 4M wx library plus 3-4 1-2M apps rather than making them waste bandwidth on 3-4M apps (from a man this stuff sure is bloated / must be a resource hog perspective even...)

Navigation

[0] Message Index

[*] Previous page