OGRE-Next
4.0.0unstable
Object-Oriented Graphics Rendering Engine
|
In Ogre-Next 3.0 we performed multiple changes that affected nearly the entire code base in subtle ways:
override
and final
keywords)SharedPtr
was replaced with std::shared_ptr
and lots of its code was deprecatedUsers who run a forked/customized version of Ogre-Next may found rebasing to the latest version a near impossible job due to the sheer amount of minor merge conflicts.
To perform this task more easily, we recommend the following:
master
branch (or 3.0 when it appears)your code
Now you have your changes applied on top of Ogre-Next 3.0!
We're using clang-format-13
A common issue is that auto-merging will skip either an opening or closing brace (i.e. missing {
or }
)
If you know what to look for, you can spot this quite easily thanks to clang format. Let say the following code:
Got merged with but now a }
is missing:
After applying Clang format, everything that follows will indent (and likely the code will not compile) which make much easier to spot where the problem went wrong:
If you find after merging and applying clang format that there is massive indentation being added (or removed); start from the top and find the first occurrence of this change and start looking for the missing brace.
The following bash script will run clang-format on all files with the right extensions in the current folder and recursively in its sub-directories.
You can also look at our python script in .github/workflows/run_clang_format.py if you prefer Python instead.