Raphael Kubo da Costa <[email protected]> writes:

> It's clear that we have to address a few things soon:
>
> * Maintaining gyp_xwalk as it is is not scaling well in this period
>   where there are so many GN changes happening upstream.
> * The make gyp generator is already in life-support mode upstream and we
>   should not count on it for long. Now that we do not need to care about
>   Tizen 2 anymore, we should consider creating a Tizen RPM for ninja and
>   start experimenting with it (it will cause problems with incremental
>   Tizen builds, though, due to ninja expecting the build directory to be
>   out/).
> * We will have to work with upstream so that we're able to remove the
>   Tizen workarounds from gyp_xwalk; namely, someone needs to investigate
>   how to make GN stop considering that a Linux build requires GTK+ and
>   friends and also find a way to stop importing find_depot_tools
>   unconditionally (we should not need depot_tools in the Tizen chroot, I
>   think).
>
> I will create JIRA tickets for those items tomorrow.

I have created XWALK-1024 and XWALK-1025 for those.
_______________________________________________
Crosswalk-dev mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev

Reply via email to