Hi All,
I just can agree - I think that's quite a nice idea. But ,aybe this
could also include the export of all the according public/include
header-files? At the moment not all bundles export their header-files by
default (e.g. rsa), which makes it difficult to setup a
build-infrastructure next to celix.
Regards,
Bjoern
Am 2013-09-20 18:45, schrieb Alexander Broekhuis:
This is exactly the reason why I do like to change this. Your opinion
is
the list you supplied, someone else his opinion might be completely
different. Eg for a lot people a deployment admin and rsa isn't
needed.
So instead of catering everyone's special needs I think one common
solution
makes more sense. With my proposed changes the following flow will be
done
by a user/developer:
* Run ccmake and select all parts you want to build and install then
run
configure and generate
* Run make to build everything
* Run make install-bundles to install the bundles
* Run make install-framework to install the framework and
dependencies
* Or run make install-all to install everything
Note: Everything in this sense means everything the user enabled in
the
configuration.
Note: I left out a make deploy, because a user of Celix will have his
own
deployment.
Hope this makes it a bit clearer!