Building current sources

[KeyWorksRW]

The stable branch is the code used for building whatever the last release version is. However, if you want to build the most current branch, then you'll be wanting to build from the main branch. The posts in this category are designed to provide information about building the current non-release code. Take a look at the changes.md file if you want to know what's in the current build that's not yet available in the official release version.

Building wxUiEditor version 1.0.0 required a C++17 compliant compiler. The current build now requires a C++20 compliant compiler. That will be the minimal requirement for several years -- I'm seeing nothing in the C++23 specs that would be useful for building wxUiEditor, so this compiler requirement should last at least until 2027.

The current version of CMakeLists.txt allows you to specify building wxWidgets as a shared library. That's useful if you are creating a Debug build as start up time for the debugger is greatly reduced. However, I'm still building a static library for release builds since it allows for profile-guided optimization of both the wxUiEditor and wxWidgets code. That may change before the official release, but for now, I can't promise a shared build will work for a Release build.

[KeyWorksRW]

Work has started on generating Python, Lua and PHP code. I doubt any of the generated code is viable just yet, it's just there to get all the underlying UI and functions hooked up to support the additional languages. So if you are building wxUiEditor yourself, and look at the output in those tabs, don't be surprised if virtually nothing in them looks correct...

The good news is that I've been able to get Windows binaries for wxPython, wxLua and wxPHP so I now have a way to test the generated code. The bad news is that the binaries I found for wxLua and wxPHP are not current with their repositories. That's going to be a major problem for wxPHP as the binary is built using a decade-old version of wxWidgets. I don't even generate C++ code for a version that old, so I'm not too happy that a more current binary isn't available. The wxLua binary is good enough to start with, and I'll continue to see if I can't find some way to get their current repository to build. I haven't tried building the wxPHP binaries yet.

[KeyWorksRW]

All of the code generation is being refactored to allow for a single path for generating either C++ or Python code (XRC generation has it's own path). While this refactoring is going on, the formatting of C++ code is changing quite a bit due to the new line-breaking code, and some temporary indentation issues. This should not affect compiling the code, or it's functionality, but if you are using SCM (e.g., git) to compare the output code, you're probably going to be seeing a lot of code differences between now and the 1.0.9 beta.