-
Notifications
You must be signed in to change notification settings - Fork 75
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
Remove boost as install dependency #1081
Comments
Hm, you could only search for Boost with the I rather vote to get rid of Boost for variants of Alpaka that do not depend on Boost.Fiber: #481 |
Removing boost should be possible for alpaka if we reimplement the compiler detection by our own. As I know this is the only part we require from boost. |
See #481 for removing the boost dependency. There is not much left. |
My intention was that we only need a boost at build time, so it is not necessary to have a boost installation when we run
Sounds good. I don't think we need to support
I thought it was possible to define dependencies in Spack independently of real dependencies, didn't I? I think this should solve the dependency problem in Spack, but keep freedom for other building systems. |
Some projects (PIConGPU, cupla) use alpaka in this way I believe. CC @psychocoderHPC |
|
Okay, then we need to take care of this. |
btw: If we remove boost in alpaka we need to handle all the boost workarounds in our user code 😢 |
Couldn't we do compiler detection in CMake? Or are there other parts of Boost that we are using? |
Open parts are listed in #481.
We can not move compiler detection to CMake because we need to handle the |
Not sure what you exactly mean, but I think those are less then you fear :) If we don't use boost we also do not need the work-around for internal boost quirks anymore ;) Yes, if PMacc/PIConGPU continues to use Boost then there we have to keep the quirks. But they are already controlled from CMake anyway, so we just move them back. (And at some point those code bases might become boost-free too... ;-) ) |
I ran into this again today because I tried to switch LLAMA to vcpkg manifests, so Boost will be setup for LLAMA, but not for alpaka, which I install as a separate step in the CI. Would be great to be able to run |
If you install alpaka via
make install
, boost should not be a dependency. Boost should only be a dependency when compiling an application with alpaka. It should not be a problem because nothing is compiled when you install alpaka. Without a boost dependency, it is much easier to deploy a Spack and Conda package.Related to: #962 and #1019
The text was updated successfully, but these errors were encountered: