Following up from
TIMOB-24282. We need better way to integrate 3rd party libraries with module other than "dealing with CMake manually".
In order to package 3rd party libraries with your module, dealing with CMakeLists.txt in your module project is needed to make sure the module includes required libraries since our build system is based on CMake. This will need some CMake commands like target_link_libraries, target_include_directories and so on. After updating CMakeList.txt, you can re-create Visual Studio project files by using --run-cmake option (See
So CMake is very flexible tool but I guess the real problem there is that dealing with CMake is generally pain for the most of Titanium developers maybe? We might want to add simple commands or something to deal with those common tasks like this.
After some consideration about having easier way to package 3rd party library other than "dealing with CMake manually", I'm planning to come up with following packaging ideas just like what Titanium Android module does for use of 3rd party JARs.
- Every *.lib, *.dll and *.winmd files in lib folder will be packaged into module and also copied/linked during Ti app build.
- Every files in platform folder are packaged into module and copied into Ti app so module can overwrite files during Ti app build.
For the test case, refer to the first comment below