Opened 7 years ago
Closed 5 years ago
#834 closed defect (duplicate)
Installation script for WHIZARD
| Reported by: | Juergen Reuter | Owned by: | kilian |
|---|---|---|---|
| Priority: | P3 | Milestone: | v3.0.0 |
| Component: | core | Version: | 2.6.1 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
This should be done using the instant WHIZARD in an automated setup, regarding the external tools. More information is in the Gitlab Issue: https://gitlab.tp.nt.uni-siegen.de/whizard/development/issues/104
Change History (2)
comment:1 Changed 6 years ago by
comment:2 Changed 5 years ago by
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Played back to Gitlab issue. 104.
Note: See
TracTickets for help on using
tickets.
Some additional bit of info - this appears to be the best place to put this:
A current thread in comp.lang.fortran (actually, two) discuss the packaging of modern-Fortran projects in OS repositories. A reasonable conclusion is:
- shared object files in /usr/lib - .mod files in /usr/{lib/lib64}/gcc/x86_64-<name-linux>/<gcc_version>/finclude/The former is obvious. We may also adopt the latter for Whizard. There are some central Whizard installations on systems with multiple compilers, and each installation will work only with that single compiler. The convention above makes that clear, and in principle may allow a Whizard distribution to be shared between different versions, if this is technically possible.