Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose "append_decorations" as a dedicated functionality, separately from load #21

Firefly35 opened this Issue Oct 11, 2018 · 1 comment


None yet
2 participants
Copy link

Firefly35 commented Oct 11, 2018

In some cases, I'd expect to be able to compute the complete full path of the shared library as an boost::filesystem::path prior to load the library.
I'd like to have a method (maybe static ?) such as
boost::filesystem::path shared_library::append_decorations(const boost::filesystem::path & path) exposed in shared_library class.


This comment has been minimized.

Copy link

apolukhin commented Oct 26, 2018

I'm afraid this is not possible. append_decorations tries to guess the name, so it may try to open multiple different names, stopping at first success.

If you have some consistent naming of your libraries/plugins then you can use the suffix function

static boost::filesystem::path suffix() {
to get the right extension and form a library name.

@apolukhin apolukhin closed this Oct 26, 2018

@apolukhin apolukhin added the wontfix label Oct 26, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.