Buildsystem TODO

• Restructure big meson.build in root folder into smaller meson.build files in subfolders
• Meson 0.48: Require Meson 0.48 or higher once it is released
• Meson 0.48: Use gnu_symbol_visibility instead of setting -fvisibility=hidden for the whole project

Additionally investigate if there is need to use __declspec(dllimport) on Windows, does not seem to be required.

changed the description

added buildsystem label

meson from debian stretch (0.37) is too old, would be nice if there were a version check and not meson 0.37 failing over the option syntax. build expeccts x86, see !9 (merged)

There is a version check, we explicitly require a meson version newer or equal to 0.47 right now.

See https://code.videolan.org/videolan/dav1d/blob/master/meson.build#L28

This is what I get with meson 0.37 from debian stretch:

The Meson build system Version: 0.37.1 Source dir: /home/jannegrunau/src/dav1d Build dir: /home/jannegrunau/src/dav1d/meson_0.37 Build type: native build

Meson encountered an error in file meson_options.txt, line 3, column 0: Unknown type array.

Nothing we can do about that. Thats really a very old version.

Probably happens because meson first evaluates the meson_options.txt and then the meson.build file. I am not aware of any way to prevent this error and have a better, more helpful error instead.

mentioned in issue #16 (closed)

mentioned in merge request !20 (merged)

I'd say, this is a high priority, because the massive build file is not elegant :)

Yes I plan to do that after !23 (merged) is merged to not conflict with that.

I just merged it.

And we need comments in the buildsystem files, to avoid people adding mess all around, because they don't know meson yet.

Yes, I agree. It is already a little mess at the moment.

We should wait for meson 0.48.1 to be released, due to regressions in 0.48.0, before we start requiring >= 0.48.0

marked the checklist item Restructure big meson.build in root folder into smaller meson.build files in subfolders as completed

Big build system restructuring is done now. Bumping to 0.48 will be postponed.

closed

mentioned in issue #61 (closed)

mentioned in issue #87 (closed)

mentioned in issue #142 (closed)

mentioned in issue #173 (closed)