osmo-ci.git branch master updated. 69350b67e6e92831efa237f73221b57146a4aa38

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-commitlog@lists.osmocom.org/.

gitosis at osmocom.org gitosis at osmocom.org
Fri Jan 12 19:14:18 UTC 2018


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CI scripts".

The branch, master has been updated
       via  69350b67e6e92831efa237f73221b57146a4aa38 (commit)
      from  971489df4a58b759689c0ad54b6cbaaa1768c65b (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-ci/commit/?id=69350b67e6e92831efa237f73221b57146a4aa38

commit 69350b67e6e92831efa237f73221b57146a4aa38
Author: Alexander Huemer <alexander.huemer at xx.vu>
Date:   Fri May 19 13:32:06 2017 +0200

    Use stow for dependency management
    
    This commit introduces the usage of GNU stow[1] for dependency
    management.
    Stow uses symlinks to make dependencies available in a single directory
    althoguh they were installed in distinct directories.
    Keeping installation directories seperate has the advantage of letting the
    build fail if AM_CFLAGS and LDADD do not contain all dependencies which are
    actually used.
    Installing multiple dependencies into a single directory causes x_CFLAGS
    and x_LIBS variables to magically point where other dependencies are
    found as well, therefore missing entries can be overlooked.
    
    Stow acts as a convenience layer here, making it unnecessary to supply a
    list of locations in LD_LIBRARY_PATH, PKG_CONFIG_PATH and so forth for
    building when dependencies are installed in distinct directories
    manually.
    Stow has to be present on the jenkins build nodes for successful executing of
    osmo-build-dep.sh.
    
    [1] https://www.gnu.org/software/stow/
    
    Change-Id: I8f5012419495a656912b7b71e4f76ce102c6b63a

-----------------------------------------------------------------------

Summary of changes:
 scripts/osmo-build-dep.sh | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)


hooks/post-receive
-- 
CI scripts



More information about the osmocom-commitlog mailing list