Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
H
Hamburg LOFAR Toolkit Installation Script
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
hpc
Hamburg LOFAR Toolkit Installation Script
Commits
73fd6866
Commit
73fd6866
authored
Mar 27, 2020
by
Orgis, Dr. Thomas
Browse files
Options
Downloads
Patches
Plain Diff
final words
parent
a68ed81a
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
build_lofar.sh
+18
-8
18 additions, 8 deletions
build_lofar.sh
with
18 additions
and
8 deletions
build_lofar.sh
+
18
−
8
View file @
73fd6866
#!/bin/bash
# A heavily changed LOFAR build script based on the one Francesco gave me.
# I put my changes into the public domain, hoping that they are useful.
# -- Dr. Thomas Orgis <thomas.orgis@uni-hamburg.de>
# TODO:
# - some syntax cleanup, "$var" instead of $var, most of the times
# - maybe more structre to reduce the repetitive identical
# fetch/patch/build code
mandatory_vars
=
"
\
lofar_prefix Installation prefix to use. Packages are put into sub-directories of that.
casacore_version Version of CASAcore.
...
...
@@ -647,22 +656,23 @@ echo "$(date) done with packages"
echo
echo
"Installation directory contents:"
ls
${
INSTALLDIR
}
ls
"
$lofar_prefix
"
# Use the same environment used to building.
print_init
()
{
cat
<<
EOT
# LOFAR Tools built by
$USER
\
@
$(
hostname
)
on
$(
date
)
# LOFAR Tools built by
$USER
@
$(
hostname
)
on
$(
date
)
#
# Sourcing this script shall re-create the build environment and
# add things from the LOFAR prefix to appropriate path variables.
# It does _not_ set LD_LIBRARY_PATH, as a proper build should use
# RPATH in the binaries. But there is LD_RUN_PATH / LIBRARY_PATH
# set for link-time usage. You can set LD_LIBRARY_PATH=
\$
LD_RUN_PATH
# as a hack if some binary fails to find its libs. But this would
# be a bug in the build script that should be fixed properly.
# It does _not_ set LD_LIBRARY_PATH (unless the build environment
# does), as a proper build should use RPATH in the binaries.
# But there is LD_RUN_PATH / LIBRARY_PATH set for link-time usage.
# You can set LD_LIBRARY_PATH=
\$
LD_RUN_PATH as a hack if some binary
# fails to find its libs. But this would be a bug in the build
# script that should be fixed properly.
#
# Step 1: The build config with all variables used.
#
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment