Cheers for that:
1) We use GlobalVars also, always have.
2) We don't see any "\" vs. "/" issues arising here.
3) We have now tried MANY different approaches, none of which seems workable. As noted, I had thought of three different possible solutions in my previous post.
Before I speak to those, I should mention again that we actually have two completely independent MinGW installations: one is an MSys2 based install, and the other is what we refer to as an "Ingar MinGW", since it built using the steps outlined by "Ingar" here (
http://ingar.satgnu.net/devenv/mingw32/index.html).
The Ingar MingW is our "core" approach to MingW matters. It is basically a "DIY from scratch" approach. It is extremely tedious, but it gives us full control over what is installed, and how. By contrast, with MSys2 you get what ever is in the Repository (e.g. this can be crucial since some of what we do is explicitly GTK2 dependent, and keeping GTK2/GTK3 bits, or any critically version dependent items, separate in MSys2 is not easy, etc etc).
We have found that if we install wxW 3.02 either in MSys2 or in IngarMingW, we get pretty much the same thing, in pretty much the same "equivalent" places. So in this respect, purely for wxSmith/CB testing, there appears to be no difference between the two MinGW's.
HOWEVER, neither of those wx installs is compatible with CB's internal requirements as far as we can tell. Amongst other things:
a) Neither produces a monolithic
b) BOTH have "extra" Dirs, for example, while CB is looking for /include/wx, both MingW's have /include/wx-3/wx instead, see also below.
c) Neither MingW has setup.h etc, which appears to be needed by CB.
4) Using the CB instructions produces a completely different Dir structure compared to any normal MinGW install, e.g. there is not the usual /bin, /include, /lib, etc Dirs. Moreover, none of the CB specific installed files end up in the MingW structure, but rather produce Dir's with .h's, dll's, etc directly in the "build or source" dir, with an unusual dir structure. Out tests have made no progress at all with the CB instructions based install.
5) Some experiments: we tried several different set-ups, with various permutations,
(i) some with MSys2 wx,
(ii) some with IngarMingW wx.
(iii) some with the CB instructions based wx install.
(iv) some with creating a special Dir structure that follows the "normal" /include, /bin, etc etc structure, and copying all the files created by the CB specific installation creation in that weird "in build/source" dir's, to these "normal looking" Dir structures.
a) Attempting to use any of the MingW installs can be "started", by editing the Wizard to test for wx.h in wx-3.0/wx/ ... regardless of whether global vars have been set.
That allows the project to be "started". However, all throughout the CB internal files, there are things like #include "wx/...". Every single one of those must be changed "wx-3.0/wx/....".
b) There is not a setup.h in any of the MingW installs. Even with the CB instructions, the wx dir has a setup_inc.h, while "setup.h" files are in further sub dirs, so all of the CB internal files looking for include "include/setup.h" must also be edited ... though we have idea what that edit should be.
c) Even if we all those edits were performed, which we have NOT (it just started to seem too iffy to us), we can't be sure what CB would would then even see the monolithic dll's.
As a final note, the only experiment where we actually got to the wxSmith screens ... i.e. actually seeing the wx editor, related code, etc, was the test where we edited the wizard, and used the either the MSys2 or IngarMingw's standard wx install (i.e. requiring editing all the CB files as well, and no guarantee that the non-monolithic would work, if we ever got that far).
We have absolutely no idea how to proceed from here, short of re-writing all the CB internal files ... and quite frankly we would wish to avoid that, even if we knew how.
Also, it is our strong preference to work with Ingar MinGW, since there we have absolutely full control over building everything from scratch (as tedious as that may be), whereas MSys2 is restricted to whatever they supply, in whatever form they supply it in ... but will work with MSys2 if that makes it easier for you.
If you have a template for us to test, we would be happy to do ... though we are struggling somewhat.
Moreover, we are wondering if an alternate version of the CB specific install instructions should be considered, so that it at leasts produces a workable dir structure, even if it is isolated from the normal MingW dir's. That is, the CB instructions should produce a dir structure etc that is consistent with what CB is expecting, even if it is not usable in any other normal way by other apps etc requiring wx.