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
Want to build HPX without dynamic libraries #934
Comments
Erik,
to load in components dynamically. I don't think this would be possible without On 2013.10.07 10.15, Erik Schnetter wrote:
Bryce Adelstein-Lelbach aka wash STE||AR Group, Center for Computation and Technology, LSU225-317-3866 - iPhone 225-578-6182 - Work (no voicemail)stellar.cct.lsu.edu cppnow.org |
Eric, I think this can be done. How urgent is this? |
Am 07.10.2013 19:32 schrieb "Hartmut Kaiser" notifications@github.com:
I second this request. Switching to static libraries would also speed up
|
This is one of these "either very soon (week-ish), or not necessary any more" things. If this is more complex, then we'll have to fall back to building some libraries required by Cactus dynamically. (Maybe this is is just Boost?) I'm not sure this will work everywhere, and if not, we would have to stay away from these systems with HPX. |
It's definitely nothing I can do in a week. |
FWIW, I was able to make HPX work on BG/Q with dynamic library loading. |
Moving this to 1.0.0 as it doesn't seem to be that time critical |
In the Cactus framework, we recently moved away from using dynamic libraries since these are generally much more difficult to configure and build, and would not give any obvious advantage at run time. (For example, current operating system's demand page loading means that unused parts of the executable will not be loaded into memory.)
Life for me would be simplified if HPX could be built without requiring dynamic libraries.
I tried using a statically-built version of Boost, and then receive the following build errors from HPX:
The text was updated successfully, but these errors were encountered: