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

(re-) upload the pre-compiled binaries #26

Closed
dev-zero opened this issue Oct 8, 2018 · 6 comments
Closed

(re-) upload the pre-compiled binaries #26

dev-zero opened this issue Oct 8, 2018 · 6 comments
Assignees
Milestone

Comments

@dev-zero
Copy link
Contributor

dev-zero commented Oct 8, 2018

maybe put them all into one cp2k-6.1.0-bin.tar.gz?

@dev-zero dev-zero added this to the Git migration milestone Oct 8, 2018
@dev-zero dev-zero self-assigned this Oct 8, 2018
@dev-zero dev-zero changed the title (re-) upload the pre-compiled binaries again (re-) upload the pre-compiled binaries Oct 8, 2018
@mkrack
Copy link
Member

mkrack commented Oct 9, 2018

Hi Tiziano, I have uploaded the precompiled binaries for v6.1.0

@dev-zero
Copy link
Contributor Author

dev-zero commented Oct 9, 2018

@mkrack thank you very much! Do you think it would make sense to either compress the binaries (with xz and default settings the size is reduced to 1/4 of the original) and/or strip the debug symbols (reduction of ~40%)? Should we also rebuild and upload binaries for older versions?

Since I plan to setup an automated build and upload via Continuous Integration after adding a tag, reducing the number of manual steps required for doing a release: What is the required environment to build them, respectively how do you currently build them? Is the arch-file for those builds in arch/?

@mkrack
Copy link
Member

mkrack commented Oct 9, 2018

An automated build and upload of verified CP2K binaries would be great. The svn release process was quite cumbersome and time consuming. The pre-compiled CP2K binaries were generated with the Linux-x86-64-gfortran.s* arch files. I will commit soon updated versions of these arch files.
For an automated build, however, it would be perhaps better to use a toolchain sopt version with static linking.

@oschuett
Copy link
Member

oschuett commented Oct 9, 2018

Sounds like a good match for Docker...
I'm regularly building a toolchain image - in case you're interested.

@mkrack
Copy link
Member

mkrack commented Oct 9, 2018

@oschuett thanks for the suggestion. I will have a look at Docker.

@oschuett
Copy link
Member

Yes, as you know I already run a bunch of Docker-Jobs for every pull request. Hence, it'd be very easy to also run your container on each tag push.

I'll publish the cp2k-ci code within the next few weeks so that others can modify it too.

@oschuett oschuett closed this as completed Jul 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants