| 1 |
Ühel kenal päeval, N, 04.05.2017 kell 18:48, kirjutas William Hubbs: |
| 2 |
> if tc-is-cross-compiler; then |
| 3 |
> _meson_create_cross_file || die "unable to write |
| 4 |
> meson cross file" |
| 5 |
> mesonargs+=( |
| 6 |
> --cross-file "${T}"/meson.crossfile |
| 7 |
> ) |
| 8 |
> fi |
| 9 |
|
| 10 |
I'm not sure we should bother with such code in the eclass when the |
| 11 |
_meson_create_cross_file doesn't do anything useful yet. |
| 12 |
Of course once that functionality is added, we can see in this draft |
| 13 |
how it'd be hooked up, but I don't see a reason to put it into the tree |
| 14 |
with this near no-op. |
| 15 |
And until this is no-op and not really functional when put into the |
| 16 |
tree, we shouldn't encourage porting non-9999 versions to use meson |
| 17 |
instead of an old build system (if still present), if the old one does |
| 18 |
support more seamless cross-compilation via e.g crossdev. This is |
| 19 |
important for things like udev probably, but less so for end-user |
| 20 |
applications in the GNOME stack for example and many of those could |
| 21 |
probably start using meson.eclass without the cross-file functionality |
| 22 |
hooked in yet (or design a new iteration of gnome2.eclass on top of |
| 23 |
it). |
| 24 |
|
| 25 |
|
| 26 |
Mart |
Archives