-
Notifications
You must be signed in to change notification settings - Fork 100
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
Could AFNI be compiled and installed through the source code? #395
Comments
Hi @Wenmj201582 . See src/other_builds/OS_notes.linux_centos_7.txt for system setup.
To initialize an 'abin' with atlases, into which you could rsync the build output directory linux_centos_7_64 (from above), consider:
|
Th chime in here: I am currently working on an EasyConfig file, so once that is merged, you can install the software via EasyBuild. |
I have not used EasyBuild. Would there be just a single .eb file then, or would there need to be one per version snapshot? |
Well, we usually don't do one EasyConfig file for every release as that could be simply too much. So per toolchain (compiler, MPI etc) there is usually only one version around, normally the one a user requested to be installed on the HPC cluster we are maintaining. That said: nobody stops you to use that as a template and just bump the version up. So for example, if we got say version AFNI_23.0.00 merged in EasyBuild, a user who is interested in building the latest bugfix, i.e. AFNI_23.0.xy, could use that EasyConfig file as a template, bump up the version and update the checksum. Unless there are drastic changes, which should not be as it is only a bug-fix release, that should work.
I hope that helps a bit. |
Could AFNI be compiled and installed through the source code?
I want to compile and install the source code of AFNI on CentOS or Euler.
Please give me instructions.
Thank you
The text was updated successfully, but these errors were encountered: