Hi,
just for the record, I just created PR with Ninja and Meson
tools/packages and will be glad for comments
https://github.com/openwrt/openwrt/pull/2312
Jan Pavlinec
Dne 18. 03. 19 v 13:41 Jo-Philipp Wich napsal(a):
> Hi Jan,
>
>> I'm trying to add ninja and meson to packages feed. The reason
On 2019-03-18 14:10, Petr Štetiar wrote:
Daniel Engberg [2019-03-18 13:55:07]:
Hi,
Having a look at https://www.python.org/dev/peps/pep-0537/#lifespan it
seems
like a good idea to stick with 3.7?
it's a PITA to demand versions which are not packaged in current
versions of LTS
Linux distro
On 2019-03-18 14:03, Jo-Philipp Wich wrote:
> Hi,
>
>> I think the cmake.mk-link approach would be a good idea and given
>> previous discussions the plan is afaik to pull in Ninja first and
>> once that's confirmed working via CMake add support for Meson.
>
> fine with me.
>
>> Having a look a
Daniel Engberg [2019-03-18 13:55:07]:
Hi,
> Having a look at https://www.python.org/dev/peps/pep-0537/#lifespan it seems
> like a good idea to stick with 3.7?
it's a PITA to demand versions which are not packaged in current versions of LTS
Linux distros. Since Meson is a build system generator,
Hi,
> I think the cmake.mk-link approach would be a good idea and given
> previous discussions the plan is afaik to pull in Ninja first and
> once that's confirmed working via CMake add support for Meson.
fine with me.
> Having a look at https://www.python.org/dev/peps/pep-0537/#lifespan
> it
Hi,
I think the cmake.mk-link approach would be a good idea and given
previous discussions the plan is afaik to pull in Ninja first and once
that's confirmed working via CMake add support for Meson. Having a look
at https://www.python.org/dev/peps/pep-0537/#lifespan it seems like a
good idea
Hi Jan,
> I'm trying to add ninja and meson to packages feed. The reason for that
> is described here https://github.com/openwrt/openwrt/pull/1871 and
> https://github.com/openwrt/packages/issues/8315 .
great to hear that! I think eventually there should be a
"tools/meson/Makefile" along with an
Hi,
I'm trying to add ninja and meson to packages feed. The reason for that
is described here https://github.com/openwrt/openwrt/pull/1871 and
https://github.com/openwrt/packages/issues/8315 .
If you want to look at that, my test repo is here
https://github.com/ja-pa/meson-turris but it's not read
Hi,
> A number of upstream projects are beginning to use the Meson/Ninja build
> system. OpenWrt's sound/mpc and libs/libmpdclient kludge around this,
> and I would like to update the glib2 package. The latest version of
> glib2 uses Meson/Ninja.
just what the world needed, yet another build syst
On 16.03.2019 19:52, W. Michael Petullo wrote:
A number of upstream projects are beginning to use the Meson/Ninja build
system. OpenWrt's sound/mpc and libs/libmpdclient kludge around this,
and I would like to update the glib2 package. The latest version of
glib2 uses Meson/Ninja.
Is there any p
A number of upstream projects are beginning to use the Meson/Ninja build
system. OpenWrt's sound/mpc and libs/libmpdclient kludge around this,
and I would like to update the glib2 package. The latest version of
glib2 uses Meson/Ninja.
Is there any plan to build the Meson/Ninja environment into the
11 matches
Mail list logo
