Author Topic: Scripted Wizard: Adding feature to wxWidgets wizard (testing steps)  (Read 113 times)

Online stahta01

  • Lives here!
  • ****
  • Posts: 5772
    • My Best Post
Anyone already have a list of things to test after modifying wxWidgets wizard?

I have created a patch that adds these project variables and now I need to test for problem(s).
Code: [Select]
      WX_COMPILER example value is "gcc".

This is part one of my planned changes to get the CB wxWidgets wizard to work with the binaries provided by the team. The next part requires editing the xrc and it was a sticking point the last time I tried this type of change.

But, I re-wrote the changes from scratch this time and I think I made the changes much smaller in size.

The xrc will have a box above or below the "configure:" to enter an compiler name which will default to the correct value most of the time. Example values will be "gcc", "vc", or "bcc". To do this right I will have to do major changes to the OnLeave_WxConf to allow the entering of the prebuilt binaries value like "gcc471TDM" to work.

Edit1: My current test plans are
1. Check with missing default.conf (to confirm it works with default created config)
2A.Check on win32 with at least two compilers ( gcc wx3.1.x, bcc wx3.0.2, and openwatcom wx2.8.12)
2B.Check on win64 with at least two compilers ( gcc wx3.1.x and MSVC wx3.0.2)
3A. Check on win32 with two downloaded binaries ( wxMSW-3.0.3_gcc510TDM_Dev.7z and wxMSW-3.0.3_gcc492TDM_Dev.7z )
3B. Check on win64 with two downloaded binaries ( gcc510TDM_x64 and vc???_x64 )
4. Check with release and debug self built binaries in one project
5. Check that add wxWidgets target works

I have no idea if I can figure out how to build wxWidgets using bcc and openwatcom.

Edit2: Created patch

Tim S.

« Last Edit: May 17, 2017, 05:39:58 pm by stahta01 »
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Testing, compiling CB Trunk against wxWidgets 3.0.2.
When in doubt, read the CB WiKi FAQ.