Howto configure wxWidgets to suit the wxWidgets project wizard?

[bnilsson]

How should my installed wxWidgets be configured to be accepted by the wxWidgets Project Wizard on WinXP?
I am using CB3888, wxWidgets-2.6.3 and/or wxWidgets-2.8.3, WinXP SP2
I built wxWidgets using msys:
./configure --enable-unicode --enable-debug --enable-monolithic --disable-shared
make

(Here the "*" means my two alternate installations, 2.6.3 and 2.8.3, I have the same problem for both.)
I built wx directly in C:\wxWidgets-2.*.3, not in a build subdirectory since "make install" does not work, at least not for me. And I guess the libs should be in C:\wxWidgets-2.*.3\lib, not in C:\wxWidgets-2.*.3\build\lib?

wxWidgets Project Wizard says
"A matching Debug configuration cannot be found..." and the same for Release.
The name of my wx library is C:\wxWidgets-2.*.3\lib\libwx_mswud-2.*.a

What is wrong?

(Note that my signature indicates Mac, this is not true in this case)

[TDragon]

I built wxWidgets using msys
...
What is wrong?

The C::B wxWidgets wizard expects to find the version of wxWidgets built with mingw32-make from the command line. For further details, see "Using makefiles directly" under the Cygwin/MinGW section in INSTALL-MSW.txt in your wxWidgets folder.

[yesidh]

Hi, I was having that same problem, so here what I did.

First, you should know that C::B uses FindwxWidgets, that's is like a script, but it only look for the libs generates using the makefile that comes with wxWidgets in the build\msw dir. To use this you can use MinGW but not MSYS, so I got it working by this way.

You can see my comments with the wizard developer: http://biplab.wordpress.com/2007/01/31/its-official-now/

The other way is just to create the project manually, without the wizard and link it with the libs generated by the process (./configure). So you will have to set the compile options for the project and say it where are the libs.

Hope this worked, bye.

[Biplab]

Hmm... A lot of people are facing this problem.

I'll try to update it to work with MSYS, too (if possible ).

Regards,

Biplab

[bnilsson]

After I used (in the black command window, not msys)

build/msw/mingw32-make -f makefile.gcc BUILD=debug MONOLITHIC=1 UNICODE=1

and

build/msw/mingw32-make -f makefile.gcc BUILD=release MONOLITHIC=1 UNICODE=1

CB wxWidgets wxWizard accepted both debug and release targets, thanks.

But it was NOT obvious. I now see that this method is prescribed when building CB from source, but that is a different story.
I guess I was biased by the fact than my normal environment  is MacOS (= Darwin unix) so I tried msys / configure first.
Maybe a line or two about this in the general CB install on the wiki pages would be appropriate? I would expect it is fairly common to develop wx apps using CB, and the install instructions in the wxWidgets distro covers lots of compilers but nothing about the CB develpment environment specifically.

[Biplab]

I've never used MSYS+CB wizard together. So it would take some time before I jump onto that.

For Windows, I would recommend not to use MSYS for wxWidgets projects.

BTW, I'll update the wizard, may be on today or tomorrow. But only GUI will be updated.

[Sensei]

HI all,

I reply to this old thread because I had the same problem like bnilsson described initially.
Now I recompiled wxWidgets2.8.6 like described above and it seems that the release and debug config can be found but I got another errordialog displayd here:



What can I do to solve this problem?

Thanks in advance

Frank

[Biplab]

I reply to this old thread because I had the same problem like bnilsson described initially.
Now I recompiled wxWidgets2.8.6 like described above and it seems that the release and debug config can be found but I got another errordialog displayd here:

This has been fixed in 4516. Use a version which is greater than that and that would solve your problem.

[Sensei]

Hi,

thanks for the fast help.
ahh what a bummer I use 4515 so I will upgrade to the newest build.

Greetings

Frank