Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Modified & Improved wxWidgets Project Wizard
Biplab:
--- Quote from: marlo_nl on February 04, 2007, 09:55:58 pm ---Forgot to mention that I did manage to set up a project where Release Target and Build Target use different library types.
The project uses a shared library for the Debug Target and a static library for the Release Target.
The project was created the wxWidgets wizard with the "Use wxWidgets DLL" check box checked.
I changed the following "Project build options" manually:
a) In the Compiler tab moved #define WXUSINGDLL from "Project" (settings used for both Debug and Release Target) to "Debug"
b) Release Target - Linker tab
added Link libraries: libwxmsw28u.a, comctl32, gdi32, ole32, oleaut32 and uuid
c) Release Target - Directories tab
Compiler tab: change <path>\wxWidgets-2.8.0\lib\gcc_dll\mswud to
<path>\wxWidgets-2.8.0\lib\gcc_lib\mswu
Linker tab: change <path>\wxWidgets-2.8.0\lib\gcc_dll to
<path>\wxWidgets-2.8.0\lib\gcc_lib
Resource compiler tab: change <path>\wxWidgets-2.8.0\lib\gcc_dll\mswud to
<path>\wxWidgets-2.8.0\lib\gcc_lib\mswu
With these changes the Debug Target and the Release Target build succesfully.
I'll also check your suggestion to see which "trick" is easiest to use.
--- End quote ---
That's great. :D I gave you alternate suggestion so that you do not need to add them manually. Please post your feedback after testing the workspace feature.
--- Quote from: marlo_nl on February 04, 2007, 09:55:58 pm ---A short remark for other newbies who might think "why would you like different library types in the first place?"
For Release Targets I prefer to have an executable that doesn't depend on DLL files, hence the static library.
For the Debug Target I could use a static wxWidgets debug library. But the static wxWidgets library has a big disadvantage (when compiled with MinGW GCC) if you are short on HDD space: it is huge, about 360 MByte. The shared wxWidgets library "only consumes" about 75 MByte.
--- End quote ---
I realised your problem and that's why I didn't ask you that question. ;) I follow similar principle for my project. While developing I use DLL for quick compilation and while distributing exe I recompile it with static wx lib and with gcc.
In my 2 PCs wxWidgets libs take almost 4 GB+ of space. Majority of these libs are used to test this wizard for any issues in Linux and Windows with different configurations. Fortunately the space is not problem for me. ;)
--- Quote from: saddam le pion on February 04, 2007, 10:01:19 pm ---Isn't CB able to compile a program AND its librairies?
--- End quote ---
If you don't want to compile wxWidgets on your own, then download wxPack.
ascxaxsvcbsxbbqvcxqsbcvxs:
--- Quote from: Biplab on February 05, 2007, 03:54:11 am ---If you don't want to compile wxWidgets on your own, then download wxPack.
--- End quote ---
thanks, i will try.
ascxaxsvcbsxbbqvcxqsbcvxs:
--- Quote from: Biplab on February 02, 2007, 03:03:50 pm ---
--- Quote from: ascxaxsvcbsxbbqvcxqsbcvxs on February 02, 2007, 02:38:14 pm ---I downloaded CB revision 3558, and installed it in a new directory, with the two extra dlls.
I downloaded wxWidgets version 2.8.0 then 2.6.3
I used the wizard to create lots of different non-empty projects. For each one, I compiled the project immediately, with the standard compiler, without modifying anything. I created some of them with 2.8.0, others with 2.6.3.
Some projects with or without unicode, with or without debug, or with release, ... I tried lot of the options available.
All projects generated more than 50 errors.
Most of them are in chkconf.h.
The first is usually "wxUSE_EXCEPTIONS must be defined."
then lots of wxUSE_ constants seem not defined.
--- End quote ---
Did you compile wxWidgets?? You have downloaded the source of wxWidgets which needs to be compiled. It seems that compiler can't find setup.h.
Also post more details.
--- End quote ---
I finally managed to compile wxWidgets OK (no errors, no warnings) with mingw on XP.
In the config.gcc there is the line
BUILD = debug
so in you wizard i checked "Debug". But i got the message "A matching Debug configuration cannot be found in the wxWidgets directory you specified."
I'am confused.
Biplab:
Wizard checks with the combination of options you've selected. The major parameters are Static/Dynamic-Ansi/Unicode-Non-monolithic/Monolithic. So BUILD=debug ensures a debug lib but it also depends upon three more variables namely SHARED=0/1 UNICODE=0/1 and MONOLITHIC=0/1. Check the values of these variables in the makefile and then select appropriate options. Wizard will not generate that warning.
ascxaxsvcbsxbbqvcxqsbcvxs:
OK, thanks, it worked.
You should group these 4 major parameters in the same panel, and make this obvious. For example, gray the options that do not correspond to the compiled wxWidgets, if not too complex to do.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version