mesonbuild/meson

Improve error message while importing subproject

Open

#2098 opened on Jul 21, 2017

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Python (4,978 stars) (1,465 forks)batch import
bughelp wantedparser/interpreter

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

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.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Locate the error message in the source code, likely in the subproject handling module. The error message is generated when a project with errors is imported. Search for the string 'couldn't find a fallback subproject' in the codebase. Modify the logic to detect if the subproject exists but has errors, and provide a more specific error message. Check linked sample projects for reproduction.