Help needed to get started - probably easy but I can't find the solution anywhere

[Didou09]

Hi,

I'm trying to transition my project from setuptools to meson because it uses cython.

It is a much more complicated journey than I had anticipated.

I've just set up a pyproject.toml and a meson.build and although it did manage to make it work locally (I can ), I can't find a way to make it work in Github Actions.

I keep getting this very cryptic error message that there is an error on the very first line of the meson.build:

The error message does not give lots of clues, so I've iteratively removed virtually all options from the project() function down to the bone and I'm still getting the error, I have no idea what to try next...

Any help will be very much appreciated

[dcbaker]

It's complaining that -Doption doesn't correspond to an option in your options file. Do you happen to have a meson.options or meson_options.txt file in your local working directory that isn't committed to git?

[Didou09]

Hi @dcbaker thanks a lot !

so it means it's actually not complaining about that line in the meson.build as the error msg suggests, but instead about an option defined on the pyproject.toml correct ?

If so, is there any ongoing plan to make the error messages more explicit to get the users to self-debug faster ?

So I do not have a meson.options file yet, and I copy-pasted that section in the pyproject.toml from another project,

ok, so I think I understand from here that these options are not generic compiler options from meson but instead custom options defined by the developers of the particular library from which I copy-pasted this ?

Meaning that without a meson.options none of these defined in my pyproject.toml make any sense ?

If I understand correctly I can still pass some default options like -Doptimization=3 ?

What's the difference between setting the options in the pyproject.toml and passing them as arguments in the meson.build's project() ? Which one takes over in case of conflict ?

Thanks again ! sorry I'm just getting started with meson

[dcbaker]

Ahhh. Okay. I think you probably don't want any of the setup keys set. Those are all passed to meson setup, and only -Doptimization is a "meson" key, the others are all kind of user defined options that go in the meson.options file, and are just examples. for a new project I would set my pyproject.toml up as:

[tool.meson-python.args]
dist = ['--include-subprojects']

And not worry about the rest until I actually needed to set those things.

[Didou09]

Thanks @dcbaker, with your help I now have a project that properly:

• compiles
• build (sdist and bdist)
• installs

But, when i try to install from the local sdist or bdist, although the installation process goes smooth, something is clearly still off.

Latest branch version is here: https://github.com/ToFuProject/tofu/tree/Issue1032_uvPyprojectt

Indeed, trying to open a python console and import the library shows it does not have a __file__ attribute, or a __version__.

Upon inspecting the content of the sdist tar.gz, it seems as the build process did not include / exclude the proper files in the archive.

How do I specify which files to exclude from the dist ?
Aka: what's the meson-python equivalent of the MANIFEST.in ?
How can I include data files too ?
And exclude some files ?

But, perhaps more importantly, it looks like the meson-built dist hasn't really identified which directories were packages despite the __init__.py being included.

Any idea why ?

Steps to reproduce:

• download the tar.gz archive created with meson from https://we.tl/t-ywuw9tUQ2g

# Create a virtual env
uv venv venv_test --python 3.11

# activate
source venv_test/bin/activate

# install the sdist
uv pip install <path-to-archive.tar.gz>

# open a python console
python

# check content of tofu => almost nothing, none of the subpackages like tf.data or tf.geom
>>> import tofu as tf
>>> tf.__file__
>>> tf.__version__
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: module 'tofu' has no attribute '__version__'
>>> dir(tf)
['__doc__', '__file__', '__loader__', '__name__', '__package__', '__path__', '__spec__']

I feel it has to do with the way the build happens and includes / excludes some files, but not sure how to fix it....

Help greatly appreciated !
Cheers