I've updated liquidmaya (mesh branch) on SourceForge to version 2.4.0, according to last version of duran-duboi branch . Stéphane Deverly did a great job for enhancing liquidmaya in last time. I've merged almost all new features from his sources, but our branches are not fully identical. As I'm using cmake for code building, I've decided to rearrange a bit location of source files for sake of simplifying configuration in CMakeLists.txt files.
In ${LIQUIDHOME}/build are located shell scripts for building:
build_drivers
build_librib
build_liquid
.cmd version for Windows and .sh for Linux and OSX.
As well, here are msvc folder for MS VisualStudio projects, and xcode for OSX (10.7).
In ${LIQUIDHOME}/src are located just few files:
CMakeLists.txt
liquid.version
liquidBin.cpp
liquidPlug.cpp
Rest files are in ${LIQUIDHOME}/src/common and ${LIQUIDHOME}/src/displayDrivers
This helps to keep directory structure more logical (imho).
Files from BOOST library were removed from include folder, because it's supposed that most current version of BOOST is already installed in system. It is not too difficult to download it from http://www.boost.org/
${LIQUIDHOME}/ribLib
The lex.var.cpp renamed to lex.var.c, because it is easer to describe compiling sources for cmake in CMakeLists.txt as whildcard *.cpp e.g. :
file(GLOB src RELATIVE "${CMAKE_CURRENT_SOURCE_DIR}" "${CMAKE_CURRENT_SOURCE_DIR}/*.cpp")
But lex.var.cpp supposed to be included in source by preprocessor directive #include in variable.y and variable.cpp.
Linked riblib library placed to ribLib/lib/${os_name} and named as librib${ARCH}.lib
e.g. librib-x64.lib for x64 architecture
On windows, I'm using zlib 1.2.5 (zlibwapi.lib, zlibwapi.dll), compiled from sources http://zlib.net/
libRibTranslator.cpp has the biggest size in the whole project... and this class need to be refactoring somehow, but this task have to be done extra thoroughly... so I've decided just to split it, for begining, on two logical parts:
libRibTranslatorArgs.cpp
libRibTranslatorGlobals.cpp
Other changes, I'm going to describe in next posts...
No comments:
Post a Comment