Originally posted by illwieckz
View Post
Anyway, no one pull request from anyone got merged in your tree after January of 2017. There is no code change since this date. All commits since January of 2017 in your tree are readme and license tweaks. The Unity tree is based on the latest version of your code (the only missing commits are some about readme rewriting and license wording).
Because my concern is to make and keep Crunch usable and to prevent fragmentation, the Dæmon repository hosts five special branches:
- https://github.com/DaemonEngine/crunch/tree/googlecode
The original tree that was hosted on Google Code, - https://github.com/DaemonEngine/crunch/tree/binomialllc
Your actual tree on Github, - https://github.com/DaemonEngine/crun...e/unvanquished
The original tree previously used by Unvanquished/Daemon with patches sitting on top of a now old version of your tree, - https://github.com/DaemonEngine/crunch/tree/unity
The Unity tree, - https://github.com/DaemonEngine/crunch/tree/master
The current tree maintained by Unvanquished/Daemon with patches rebased on Unity tree.
The Crunch tree maintained by Unvanquished/Daemon provides:
- Your own tree up to the latest code-related commits you made,
- Unity patches above your own commits (making the code faster and producing smaller files),
- Linux 64bit compilation fixes (make crunch and software embedding crnlib to compile on this system and architecture),
- Fix for malloc in crn_decomp on macOS and FreeBSD (make software embedding crnlib to compile on those systems),
- Support for user-supplied definition of CRND_ASSERT to be used in (make crnlib easier to embed in an software),
- CMake support (make software embedding crnlib easier to integrate crnlib in the toolchain, also install crunch the File Hierarchy Standard way),
- Makefile fixes (to make compilation working again for those who may still rely in it),
- Option for top mip-level renormalization (a special option for normal maps to make Z reconstruction easier when using DXT5/BC3),
- A first class embedding in other software when used as a git submodule.
Also, if what you call RDO is not a format but some decision optimization techniques (maybe the ones used by the -bitrate option I've never seen used?), 90% of my previous comment is still fully relevant because as I said, mistakes I would say about what is RDO is not a concern: my concern is to keep Crunch being alive, being usable and fits the need of users.
Today the Unvanquished/Damon tree of Crunch is probably the only one making it possible to compile and run the Crunch tool outside of Windows and to embed crnlib in software with neat submodule integration and toolchain integration with compilation supported on four operating systems.
Originally posted by richgel999
View Post
Leave a comment: