-
-
Notifications
You must be signed in to change notification settings - Fork 636
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
meson include directory #792
Comments
This is basically just #670 but from the other direction. When I opened the other ticket, I based it on the assumption that the directions in the tutorial and throughout the documentation -- which say to use |
I would support |
Just to add another argument: Installing doctest on Gentoo leads to these files:
Using
(I tried TL;DR: |
As discussed in #670 , I'm in favor of the solution proposed by @jwidauer , if this only has as a side effect that it changes the include path by downstream projects. Not being a Meson though, so any Meson people please verify the approach. |
Regardless of which include style is preferred, I would say that changing the |
I agree with that as well, and that is an important point. Let's think about non-breaking workarounds. One is to change the statement to The breaking change could be introduced in a 3.xx release. |
Description
Hi there!
I've been using doctest for quite a while using CMake and Conan and have been loving it!
I was now trying to use it directly as a meson subproject.
While doing so, I noticed that in the current
meson.build
file, it declares the dependency to directly include thedoctest
directory.It's specifically this line:
This means that, to be able to use doctest from a meson project, one would have to include it like this:
Instead of the way that is shown in the examples and done for all the other build systems:
Is this intended?
If not, I would assume the above line in the
meson.build
file to be:Steps to reproduce
Try and use doctest as a subproject in a project using meson as the build system.
The text was updated successfully, but these errors were encountered: