Re: Meson build updates
От | Andres Freund |
---|---|
Тема | Re: Meson build updates |
Дата | |
Msg-id | 20230629190242.kgnimiizjbvmdfni@awork3.anarazel.de обсуждение исходный текст |
Ответ на | Re: Meson build updates ("Tristan Partin" <tristan@neon.tech>) |
Ответы |
Re: Meson build updates
|
Список | pgsql-hackers |
Hi, On 2023-06-13 14:56:36 -0500, Tristan Partin wrote: > I was thinking today. When you initially wrote the build, did you try > using the src/bin/meson.build file as the place where all the binaries > were built? As you say, most of the src/bin/xxx/meson.build files are > extrememly reptitive. > We had a similar-ish issue in my last project which I solved like: > > https://github.com/hse-project/hse/blob/master/tools/meson.build#L20-L405 > > This is a pattern I used quite frequently in that project. One benefit > of this approach is that the binaries all end up next to each other in > the build tree which is eventually how they'll be laid out in the > install destination. The other benefit is of course reducing reptitive > code. I think the build directory and the source code directory not matching in structure would have made it considerably harder sell for people to migrate. I.e. I considered it, but due to meson's "no outputs outside of the current directory" rule, it didn't (and sadly still doesn't) really seem viable. Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: