pnoltes commented on issue #442:
URL: https://github.com/apache/celix/issues/442#issuecomment-1502101250
I think it would be good to reintroduce FRAMEWORK_EXPORT using new set of
marcros and some documentation.
For marcro, I was thinking about:
```C
//celix_export.h (part of celix_utils lib)
#define CELIX_EXPORT __attribute__((visibility ("default")))
#define CELIX_LOCAL __attribute__((visibility ("hidden")))
```
And applying the marcros to all C/C++ utils, dfi and framework headers.
To be honest I am not sure how this needs to be applied to bundle libraries.
With the linking script example, only the bundle activator symbols are
global and I think this is default what we want for bundles.
@PengZheng Does this means that all C++ - note header only - methods needs
to be declared as "CELIX_LOCAL" , with an exception for the C++ exceptions?
Is an other option to let the `add_celix_bundle` cmake function default
produce a linker script, so that only the bundle activator functions are global?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@celix.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
