Build Environment Effort/Status And Next Steps

Build Environment Effort
Quick Navigation Customers Build Performance Elimination of Non-Pro Dependencies Module Problems Split Build Scalability HID List New Build System Requirements External Source Tarballs ToDo Build System Analysis Zen of gbuild Gbuild Bootstrapping Module Migration Module Migration Tips Build System Analysis:capstone2013 windows build Capstone 2013 Client Requirements Document Capstone 2013 Technology Review & Implementation Document
About this template

Integration of first milestone of the new build system in DEV300 m96

New features

With the integration of the CWS gnumake2 we got support for the following target types in our new build system:

• compiling and linking C, C++, Objective-C files into
  • shared libraries
  • non-GUI executables
• compiling src files into resources including localization
• copying a bunch of files ("package") into solver

For cxx compilation we also support some sub-targets:

• compilation of sdi files
• delivery of header files into solver
• processing of component files for UNO service libraries
• support for precompiled headers (currently used only with MSVC++)

Converted Modules

Along with the new features we converted the following modules to use the new build system:

• tools
• svl
• svtools
• xmloff
• framework
• toolkit
• sfx2
• sw

Detected problems, caveats and known issues

• Compiling with ENABLE_PCH=TRUE and DEBUG=T with MSVC creates dlls that contain debug information only for the symbols of the library; all debug symbols for linked libraries are missing
  • root cause: PCH object needs to be linked into DLL to let mspdbserv find the necessary debug information
  • fix time line: cws gnumake3
  • workaround: call "unset ENABLE_PCH" when compiling with debug until the bug is fixed