mesonbuild/meson

inconsistency in output during installation

Open

#1,237 opened on Dec 19, 2016

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Python (1,465 forks)batch import
good first issue

Repository metrics

Stars
 (4,978 stars)
PR merge metrics
 (Avg merge 139d 13h) (51 merged PRs in 30d)

Description

Installing src/cpp/libxmlrpc_client++.so.8.47 to /home/brain/tmp//usr/local/lib64/libxmlrpc_client++.so.8.47
Installing openssl_thread.h to /home/brain/tmp//usr/local/include/xmlrpc-c
Installing /home/brain/git/upstream/xmlrpc-c/tools/xml-rpc-api2cpp/xml-rpc-api2cpp.1 to /home/brain/tmp//usr/local/share/man/man1.

There are 3 kind of outputs:

  1. Installation by keyword from library(), perfectly fine, shows subdir and location where is installing
  2. Installation by install_headers(), missing subdir and destination filename
  3. Installation by install_man()/install_data()/pkgconfig.generate(..., install:true), shows full path, doesn't show destination filename and fullstop at the end

Contributor guide

Research direction
Investigate the installation output code in Meson's build system to standardize the format of install messages across different functions (library, install headers, install man, etc.).
Tech stack
python
Domain
build system
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75