-
Notifications
You must be signed in to change notification settings - Fork 15
Make healpix+smoc compilation optional #19
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
Comments
Yeah, I could really use this, I think. Our main database server is still RHEL 6.x, and I don't think there's a libhealpix for it. I'm not seeing a package for it at least. I'm getting compilation errors when trying to compile the current master branch of this repo:
etc. Any short-term workarounds that I can employ? |
I hacked away at the Makefile using #13 as a guideline and managed to get it to compile, install, and crushtest OK. Whew! |
@esabol I did that PR but I had a talk with our colleagues from ivoa (I guess). They wanted to make some changes in Makefile till the end of June. I've postponed my changes to avoid conflicts. I will ask them again at the beginning of next week and proceed with it. |
Oh, I was going to submit a PR for this, but I'll defer to yours. |
Dear @msdemlei, @df7cb. We spoke about some cleanup in Makefile. It was told that there are some changes are planning from your side in Makefile stuff (#8 (comment)). It least I've understood so. How is your progress going? I would like to continue with optional healpix but I'm still waiting some changes from your side to avoid potential conflicts. I would also propose to create a new Issue for Makefile cleanup task to be able to discuss some changes. |
Hi, we aren't ready with that yet, so please just go ahead with your changes and we'll cope afterwards. Thanks! |
@esabol If you are already have a prepared patch, please, create a PR (may be after PARALLEL SAFE). Otherwise, I will plan to do it. Thank you! |
[ISSUE #19] Make HEALPix/MOC support optional
The issue is done. @esabol Thank you very much! |
No description provided.
The text was updated successfully, but these errors were encountered: