-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Figure out the project source entry #129
Labels
enhancement
New feature or request
Comments
I think |
It was fixed in nightly a couple of weeks ago |
May you link the commit or the PR |
That is the commit that fixes the issue on builder https://gitlab.gnome.org/GNOME/gnome-builder/-/commit/dabde58 |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you clone ashpd and open it with vscode, it will properly find the ashpd-demo manifest but won't build because the meson.build won't be found in this case as it is in ashpd-demo subdirectory.
I think we should look at the last module, if it is of type path, get the absolute path based on that + the path of the manifest. If it is not, we need to come up with a different approach.
The text was updated successfully, but these errors were encountered: