Re: meson or generic ninja support?
Kevin Funk <[email protected]>
| Newsgroups | gmane.comp.kde.users.kdevelop |
|---|---|
| Message-ID | <2781854.haeZEXNrrJ@kerberos> |
On Sunday, 6 August 2017 08:45:06 CEST René J.V. Bertin wrote: > On Saturday August 05 2017 01:18:20 Aleix Pol wrote: > >Of course not. You should start a meson plugin, not refactor the cmake one. > > Frankly, I don't know (and don't have much incentive to find out) what's > better/easier, strip the unneeded parts from the cmake plugin or start > something completely from scratch. The compile_command.json parser should be factored out. The file format is build system agnostic. A couple of different build systems actually support generating these files (CMake, QBS, <a couple of hand-written scripts>, ...). For the rest, you'd still need a new plugin for Meson though. Regards, Kevin > I've seen only 1 aspect for now where meson is very different from both > configure and cmake: you cannot reinvoke it in an already configured build > tree. Instead, you have to use the mesonconf executable, which doesn't have > exactly the same calling signature. -- Kevin Funk | [email protected] | http://kfunk.org
signature.asc
(application/pgp-signature, 163 B)
-----BEGIN PGP SIGNATURE----- iEYEABECAAYFAlmIHfEACgkQxkz1axPKzl3FEQCgocqUKxdQz2PAvcHfVGgr486F PP0An2dQQoFElBIqai5p1voQgWaWBrQY =1kir -----END PGP SIGNATURE-----