mesonbuild/meson

Improve error message while importing subproject

Open

#2,098 opened on Jul 21, 2017

View on GitHubContributor guide
 (1 comment) (1 reaction) (0 assignees)Python (1,465 forks)batch import
bughelp wantedparser/interpreter

Repository metrics

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

Description

If you import a wrapped project with errors in its build definition will produce an error: Also couldn't find a fallback subproject in subprojects/<project_name> for the dependency <dep_name>

While the error could just be a wrong spelled source file in subprojects/<project_name>/*/meson.build. We expect it to say that the project has errors not that the project doesn't exist.

As sample: This project imports the subproject without error except that it doesn't build(not completed yet..). This project shows the error while I just added a wrong source file in the subproject build definition.

Contributor guide

Research direction
Find the source code that generates the error message about fallback subproject not found. Then update the message to differentiate between a missing project and a project with build errors.
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.
Mostly clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75