Add include() function

[BeChris]

Hello, here's a proposal to add an include() function in order to be able to parse other build files.

included file must be valid meson file.

It's like subdir() except that:

• It is not limited to relative path
• included file can have any name (not mandatory to be meson.build)

[tp-m]

Nice! This fixes issue #375 for what it's worth. Does it already include detection to make sure the same (actual) file can't be included multiple times? If not, that may be required.

[xclaesse]

I guess it could be accepted if a file can be included only once, otherwise it would be equivalent to having functions, which is explicitly rejected by meson design. If I understand correctly.

[amitdo]

+1 for adding this feature to meson.

To what directory will the object files go?

[BeChris]

It includes cyclic dependency detection but doesn't forbid including in a meson.build file the same include file several times. Le jeu. 10 mai 2018 à 00:09, Tim-Philipp Müller <notifications@github.com> a écrit :

…

Nice! This fixes issue #375 <#375> for what it's worth. Does it already include detection to make sure the same (actual) file can't be included multiple times? If not, that may be required. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3557 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQ3p5vlieBCZG3LHttOhOJ60IAs2jOplks5tw2kSgaJpZM4T5DY_> .

[BeChris]

Object files destination directory is based on the directory of meson.build file which did the inclusion. Le jeu. 10 mai 2018 à 16:19, Amit D. <notifications@github.com> a écrit :

…

+1 for adding this feature to meson. To what directory will the object files go? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3557 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQ3p5tckF72_HvuVDS0S0zfo69IxdEOkks5txExcgaJpZM4T5DY_> .

[leio]

Please have it require a prefix of meson.build. or at least meson, or a specific extension, preferably .build or maybe .meson. It's a pain to monitor changes across version bumps downstream if these files could theoretically be anywhere with any names. With prefix they are at least together in a tool like meld, or with suffix extension can at least filter by something concrete. If dependency and their minimum requirements can start to go in randomly named files, it's very inconvenient to be able to notice the fact when doing version bumps.
Disclaimer: I'm just saying this as a downstream packager worried his work becomes more complicated without this kind of limitations; not speaking for the meson project whatsoever.

[TheQwertiest]

IMO, the included filename should have a limit imposed, e.g. FILENAME.meson or meson.FILENAME, for the ease of tracking such includes (imagine include('my_logic.cpp')).
This would be also consistent with other meson logic, like restricting extensions of source files for specific language (e.g. .c for C and .cpp for C++).

[EDIT] @leio was faster :D