Matching debug/ release configuration cannot be found ... Topic is solved

[nji]

I was searching for an alternative to MSVS and found C:B/ WxWidgets.
Being on Win7, I installed the newest C:B (gcc), and then WxWidgets (3.0.3)
as binaries (include and lib).
Trying to build my first wxwidget project (with no default settings changed)
there arose two (common?) problems:
"A matching Debug configuration cannot be found in the wxwidget directory ..."
(release the same). No matter what "wxwidget library settings" I try.
And - after ignoring that - compiling, there comes
"wx/setup.h not found in platform.h"
I found several threads heading for these, but all seem very specific and complex.
Is it really necessary to "dig as deep" just to get it running?
Well, I'm a newbie to all that ... are there simple steps?
Thank you!

[doublemax]

I wish C:B would provide a better step-by-step documentation, these question comes so often...

The key issue here is that the settings you make in C:B must match the ones you used when you built the wxWidgets libraries.

Maybe this helps:
viewtopic.php?p=169501#p169501

[nji]

Yes, I agree with you ... it points that the documentation/ the default configuration is not too well.

Concerning building the wxWidget libraries:
I didn't build them at all - but took the the pre-built binaries (for TDM-GCC 4.9)
But then building in C:B, none of the choices (monolithic, unicode etc.) does the job.
And then still, there remains the "wx/setup.h-thing".
Quite high hurdles for newbies ...

[xaviou]

Hi.

I installed the newest C:B (gcc), and then WxWidgets (3.0.3)
as binaries (include and lib).

I assume you've downloaded the official binaries.

So, in your wxWidgets's installation dir, you should have , in the "lib" folder, a sub-directory named "gccxxxTDM[_x64]_dll". (the 'xxx' part correspond to the compiler's version, the 'x64' is here if you've downloaded the 64 bits version of the libs).

You can rename this folder to "gcc_dll" and the C::B wizard should work.

If you don't want to proceed like this, just ignore the wizard's warning, and adjust the project build options when it will be created (you'll have to modify the "search directories" entries to correspond to the folder in its original form).

Regards
Xav'

[xaviou]

But then building in C:B, none of the choices (monolithic, unicode etc.) does the job.

The official binaries are "non-monolithic unicode dll" builds.

Regards
Xav'

[nji]

Thank you!
Both ways did it.
What - of both alternatives (renaming the wx-dir or changing the build options) - is the "better" way?
Being able to switch between 32- and 64-bit target WITHIN C:B,
wouldn't it be better to change the pointing to the wx-libs withing C:B too?
Regards

[xaviou]

Hi

Thank you!
Both ways did it.
What - of both alternatives (renaming the wx-dir or changing the build options) - is the "better" way?
Being able to switch between 32- and 64-bit target WITHIN C:B,
wouldn't it be better to change the pointing to the wx-libs withing C:B too?
Regards

Both solutions have their advantages and their disavantages :

• Renaming the folder will allow you to use the C::B wizard "as-is", but you'll have to do it each time you re-install a new version of the libs
• Modifying the directories within C::B is a little bit difficult, and you'll have to do it for each new project, but it will allow you to use the libs without modifying anything you've installed

If you want to install both 32 and 64 bits versions of the libs, I think it is better to use the second solution (if you use the first, you'll have to rename the folder each time you will need to switch from an architecture to another).

Regards
Xav'