Alexander Broekhuis created CELIX-43:
----------------------------------------
Summary: Update bundle creation and deployment
Key: CELIX-43
URL: https://issues.apache.org/jira/browse/CELIX-43
Project: Celix
Issue Type: Bug
Reporter: Alexander Broekhuis
Currently the build of Celix builds the library and the bundle (zip) file in
one go, but the library is located in its own subdirectory, while the bundles
are created in the (build_root)/bundles directory.
This will be changed so that the bundles are also left in their own directory,
next to the library. The same would also apply for the "development packages"
(bundle + header files in one zip file).
This can easily be done, but making a deployment becomes a little bit
different. Currently the deploy target assumes a bundle exists in the
(build_root)/bundles directory. Wether this is the case or not is not checked.
If the bundle is placed next to the library, the build must determine the path
to the bundle, since this path depends on the directory of the sub-project.
This has a side effect that if a target is not yet processed by CMake, CMake
doesn't know this path, so the deployment can't be determined.
A simple fix for this is to remove all the deploy calls from the CMake files
and place them in an own file which is only processed after all other
sub-projects are handled. For me this also makes more sense, since deployment
implies that all needed bundles are build.
These changes also make it possible to use a concurrent build (make -j).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
