Tags: michaelchen0426/osrm-backend
Tags
gain a pretty big release with more than 150 commits: - modernized code base to use C++11 language features - decluttered the code base touching virtually every line of code - cut down on static analyzer warnings - much better linking performance on GCC 4.9 - fixed extraction on 32 bit systems (while officially unsupported)
This is again a pretty big release with more than 170 commits (adding… … about 1500 LOCs). And it is the first release in a series to bring major improvements in memory usage. Depending on the size and location of the extract, you can expect 25--45% improvements. This is the shortened change log: - compress all road geometries (49% on the planet for cars) - make all error messages JSON - activated link time optimizations by default - more test scenarios (25+) - use forward decl's to cut compile times - ongoing effort to make code more legible - several lints fixed that were detected by facebooks flint - several lints fixed that were detected by Coveritys static analyzer - several lints fixed that were detected by OCLint - remove remnants of C-Style - add clang-format style file
The release is the result of hard work of all contributors and comes … …at a hefty count of 278 commits. The shortened changelog is this: - Fix performance regression in JSON generation - Update and enhance test suite - Activate link time optimizations - Update speed profiles to be more realistic - CMake now adds RPATH info to executables - Refactored some code for better readability - Removed pesky function ptr from CRC32 computation - Enhanced feedback on command line options - Escape characters in JSON instead of HTML-entetizing - Decode URI-encoded requests - Fix a possible path quality regression - General support for non-X86(-64) targets, e.g. Raspberry Pi - Remove remaining C-style function calls - Fix minor GPX export issue - Fix resource leak, coverity issue #1121924 - Generate pkgconfig file - Compile and install libOSRM as static lib - Lint removal in CMakeLists.txt - Refactor perpendicular projection to nearest location - Untangling includes to cut down compile time - More precise line generalizations - Make nearest neighbor queries more efficient - And many, many more smaller and bigger changes