Update wxWidgets project wizard

[PB]

Proposed changes for updating wxWidgets project wizard:
* Drop support for outdated wxWidgets 3.0 and 3.1. These versions are outdated and unsupported so it makes no sense to use them in a new project. Removing them allowed to simplify the wizard code.
* Do not allow using non-Unicode configuration for wxWidgets 3.3 and newer, where Unicode is the only text encoding supported.
* On Windows, link to Winsock2 unconditionally. wxWidgets older than 3.2 used older Winsock version so we needed to provide a choice.
* On Windows, link to gdiplus and msimg32 for wxWidgets 3.3 and newer, as required there.  wxWidgets 3.2 and older load functions from these libraries at run-time from DLLs.
* Do not link to wxAdvanced, the library does not exist in wxWidgets 3.2 and newer.

Unfortunately, I do not know how to create an SVN patch, but the changes can be previewed here: https://github.com/arnholm/codeblocks_sfmirror/commit/707654a6754fee7ef9147a639196eaa6284ccdac

[MichaelAgarkov]

I actually use wxWidgets 3.0.5.

[MichaelAgarkov]

Also if we remove support for old wxWidgets version will people be forced to update old projects that use them? What if they're targeting Win95 (supports only wxWidgets 3.0.x and older)?

[Miguel Gimenez]

Wx3.0 is still supported on Linux, 3.2 is not included in most distributions. The changes for MSW look OK.

Old projects are not affected, this is only the wizard for new projects.

[PB]

As for Windows:
TBH, I think people starting new wxWidgets project in year 2025 or later, who target OSes from the previous millennium, must deal with it. Whether you like it or not, starting a new project using a severally outdated wxWidgets version is a very bad idea.

Of course, one is still allowed to use whichever wxWidgets in a C::B project, one cannot just use a wizard to create one. I honestly don't think it is unreasonable and I am not exactly a youngster who likes to throw away everything slightly old.

And as for Linux, by the time new C::B version is out in the wild, it will be about 3 years since wxWidgets 3.2 release. If 3.2 is still not supported, then there must be something wrong. Anyway, the "why start a project using outdated and unsupported library version" argument still stands. Moreover, AFAIK, the trend has been to move away from linking the system libraries and pack their own with a project instead.

Either way, I am not going to argue (any further), I let the devs decide if they are interested and what they want to take.

[Miguel Gimenez]

Applied changes for wxWidgets >= 3.3 in 13595, thank you.

Dropping support for wx3.0 and wx3.1 is desirable but premature. I have saved your changes for a future commit.

[PB]

Applied changes for wxWidgets >= 3.3 in 13595, thank you.

Dropping support for wx3.0 and wx3.1 is desirable but premature. I have saved your changes for a future commit.

OK.