34 lines
No EOL
2.3 KiB
Text
34 lines
No EOL
2.3 KiB
Text
************************************************************************************
|
|
* Generating the solutions & building the libraries
|
|
************************************************************************************
|
|
1. Run build_ubiservices script and select whether all the Ubiservices SDK modules are enabled of disabled by default by passing TRUE or FALSE.
|
|
after that the configurations files will be generated in /[PackageRoot]/_configurations/ folder
|
|
2. Edit the following generated files in a text editor to fill missing information
|
|
and customize the build (Compilation flags, files location, etc).
|
|
- /[PackageRoot]/_configurations/productConfiguration.cmake: this file is used
|
|
to configure the settings specific to UbiServices' SDK
|
|
- Activate or deactive the modules that will be part or removed from the Ubiservices SDK solution
|
|
- /[PackageRoot]/_configurations/harbourConfiguration.cmake: this file is used to
|
|
configure the settings common to all Harbour SDKs. E.g. compilation flags.
|
|
- /[PackageRoot]/_configurations/platformsConfiguration: this file is used to
|
|
select the platforms to be built
|
|
|
|
3. Run build_ubiservices a second time to generate the solutions and launch the build.
|
|
|
|
|
|
************************************************************************************
|
|
* Notes
|
|
************************************************************************************
|
|
- build_ubiservices script will return with error if
|
|
the configuration files are not set properly. Therefore configure all settings in each file
|
|
otherwise you will have to relaunch build_ubiservices many times.
|
|
- The generated files won't need to be modified each time you update the SDK. The
|
|
configuration is done once and for all.
|
|
- Note: If you change the state of a module(TRUE or FALSE) you will need to rerun the build_ubiservices script in order for the changes to be applied.
|
|
- Note: If the SDK adds a new module the generated files need to be deleted and regenerated in order
|
|
for the new module to appear inside /[PackageRoot]/_configurations/productConfiguration.cmake.
|
|
Otherwise the new modules will no be part of your SDK solution.
|
|
- harbourConfiguration.cmake can be shared with other Harbour SDKs simply by specifying the
|
|
file's location in each SDK's productConfiguration.cmake.
|
|
|
|
|