The only reason I know so much about the issues you are hitting is that I have seen them and had to work my way through them.
There are a bunch of things that need to be aware of when updating the files to wxWidgets as you are new to it and will as you are aware hit bumps along the way and sometimes have to revert changes if they do not work out. Some of the issues you will hit with updating the existing build files:
- Some of the project files are hard coded for the "default" wxWidgets for the OS. 3.1 for Windows and 3.0 for Linux. These are mainly the batch and script files called from the existing CBP files. These are a pain to update as there are IMHO way too many of them.
- Some of the scripts in the src directory also have hard coded paths based on the file.
- The big one is that you need to change all references in all the CBP files to change the wxWidget you are building against/for. One mistake and you get into allot of trouble (aka errors).
With wxWidgets 3.2.0 please make sure you manually incorporate the following change otherwise you will have issues with dialogs opening off screen at some point:
If you want to create a Windows installer that the quickest way is to grab the
https://github.com/acotty/CodeBlocks_Unofficial_Testing/tree/master/windows_installer directory and put it in the same sub directory in your source tree and run the appropriate bat file in the windows_installer. Please read the start of one of the *.nsi for what you need to install to get the NSIS script to work. I have not checked it works against the stock SF source tree for 2 or 3 months. If it does not work can you create an issue in the Github repo for me.
I have solved all of the project file quirks that I am aware of in the
https://github.com/acotty/CodeBlocks_Unofficial_Testing repo. If you get stuck compare the *.cbp and *.bat files as I have moved all of the zip creation into the CBP files and the src bat files do not create any zip files anymore, but they still copy the compiler DLL files. If you get stuck with any of these or want to know why or what or any feedback on these updated/changes files create a discussion in the github repo so I can answer you as these files are not official C::B files.
If/when you get to building on Linux or Mac drop me a DM and I will give you some more pointers, but if you want a head start then have a read of one of the readme files in the repo root directory, but be aware that these are not 100% polished so if you can help out with fixing/updating/polishing them I would be very much appreciated as they need to be reviewed and checked.