Re: [Mesa-dev] Few issues with Meson

[Dylan Baker]

This is my cross file (Arch doesn't have a pkg-config for x86, so I have a shell
wrapper that sets PKG_CONFIG_PATH), you'll probably need to adjust some paths

```
[binaries]
c = '/usr/bin/gcc'
cpp = '/usr/bin/g++'
ar = '/usr/bin/ar'
strip = '/usr/bin/strip'
pkgconfig = '/home/dylan/.local/bin/pkg-config-lib32'
llvm-config = '/usr/bin/llvm-config32'

[properties]
c_args = ['-m32']
c_link_args = ['-m32']
cpp_args = ['-m32']
cpp_link_args = ['-m32']

[host_machine]
system = 'linux'
cpu_family = 'x86'
cpu = 'i686'
endian = 'little'

# vim: ft=dosini
```

meson build-x66 --cross-file   should give you a working
mesa for your arch.

There's some upstream discussion on how to choose llvm-config for non-cross
compilation cases, but that hasn't moved a whole lot recently.

Dylan

Quoting Mike Lothian (2018-03-12 10:57:01)
> Hi Dylan
> 
> Do you have the link to patch on patchwork? I'll give it a go
> 
> I'm using meson 0.45 however the cross-file requires more than just defining
> llvm-config, everything else is normally picked up from what portage is 
> setting
> in the build environment - though strangely not if clang is used - I'll look
> into that sometime
> 
> Regards
> 
> Mike
> 
> On Fri, 9 Mar 2018 at 16:37 Dylan Baker  wrote:
> 
> Quoting Mike Lothian (2018-03-06 05:07:34)
> > Hi
> >
> > When compiling wine I also noticed that the d3d.pc files didn't have
> moduledir
> > set, so wine couldn't find it
> >
> > configure: error: pkg-config couldn't find Gallium Nine module
> 
> I've sent a patch for this.
> 
> >
> > Regards
> >
> > Mike
> >
> > On Tue, 6 Mar 2018 at 02:17 Mike Lothian  wrote:
> >
> >     Hi
> >
> >     I've been trying to get a Gentoo ebuild ready for meson
> >
> >     I've had to fudge the llvm-config for cross compiling a 32bit mesa 
> on
> >     a 64bit machine
> 
> If you're using a new enough meson (0.45) you can specify the llvm-config
> you
> want to use in the cross file.
> 
> >
> >     I notice that -Dvulkan-drivers= doesn't accept intel,radeon like
> >     autotools used to, it also seems as long as one value is correct the
> >     other is ignored
> 
> we're using amd instead of radeon. After 18.0 branches I want to bump the
> meson
> requirement so we can use meson's list argument type, which will check for
> such
> problems.
> 
> >
> >     Also -Dva-libs-path= doesn't play well with absolute paths, or 
> rather
> >     install_megadrivers.py is doing something strange - normally gentoo
> >     installs everything to a temporary image path then puts those files
> >     into the live system. It seems install_megadrivers.py doesn't do 
> this
> >     and installs directly to the live system - I worked around it by
> >     dropping the /usr
> 
> There's a patch from someone in FreeBSD that might fix this (the way we do
> symlinking in install_megadrivers is wrong).
> 
> Sorry it took me so long to find this email, notmuch applied some odd tags
> to
> it.
> 
> Dylan
> 


signature.asc
Description: signature
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Few issues with Meson

[Mike Lothian]

Hi Dylan

Do you have the link to patch on patchwork? I'll give it a go

I'm using meson 0.45 however the cross-file requires more than just
defining llvm-config, everything else is normally picked up from what
portage is setting in the build environment - though strangely not if clang
is used - I'll look into that sometime

Regards

Mike

On Fri, 9 Mar 2018 at 16:37 Dylan Baker  wrote:

> Quoting Mike Lothian (2018-03-06 05:07:34)
> > Hi
> >
> > When compiling wine I also noticed that the d3d.pc files didn't have
> moduledir
> > set, so wine couldn't find it
> >
> > configure: error: pkg-config couldn't find Gallium Nine module
>
> I've sent a patch for this.
>
> >
> > Regards
> >
> > Mike
> >
> > On Tue, 6 Mar 2018 at 02:17 Mike Lothian  wrote:
> >
> > Hi
> >
> > I've been trying to get a Gentoo ebuild ready for meson
> >
> > I've had to fudge the llvm-config for cross compiling a 32bit mesa on
> > a 64bit machine
>
> If you're using a new enough meson (0.45) you can specify the llvm-config
> you
> want to use in the cross file.
>
> >
> > I notice that -Dvulkan-drivers= doesn't accept intel,radeon like
> > autotools used to, it also seems as long as one value is correct the
> > other is ignored
>
> we're using amd instead of radeon. After 18.0 branches I want to bump the
> meson
> requirement so we can use meson's list argument type, which will check for
> such
> problems.
>
> >
> > Also -Dva-libs-path= doesn't play well with absolute paths, or rather
> > install_megadrivers.py is doing something strange - normally gentoo
> > installs everything to a temporary image path then puts those files
> > into the live system. It seems install_megadrivers.py doesn't do this
> > and installs directly to the live system - I worked around it by
> > dropping the /usr
>
> There's a patch from someone in FreeBSD that might fix this (the way we do
> symlinking in install_megadrivers is wrong).
>
> Sorry it took me so long to find this email, notmuch applied some odd tags
> to
> it.
>
> Dylan
>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Few issues with Meson

[Dylan Baker]

Quoting Mike Lothian (2018-03-06 05:07:34)
> Hi
> 
> When compiling wine I also noticed that the d3d.pc files didn't have moduledir
> set, so wine couldn't find it
> 
> configure: error: pkg-config couldn't find Gallium Nine module

I've sent a patch for this.

> 
> Regards
> 
> Mike
> 
> On Tue, 6 Mar 2018 at 02:17 Mike Lothian  wrote:
> 
> Hi
> 
> I've been trying to get a Gentoo ebuild ready for meson
> 
> I've had to fudge the llvm-config for cross compiling a 32bit mesa on
> a 64bit machine

If you're using a new enough meson (0.45) you can specify the llvm-config you
want to use in the cross file.

> 
> I notice that -Dvulkan-drivers= doesn't accept intel,radeon like
> autotools used to, it also seems as long as one value is correct the
> other is ignored

we're using amd instead of radeon. After 18.0 branches I want to bump the meson
requirement so we can use meson's list argument type, which will check for such
problems.

> 
> Also -Dva-libs-path= doesn't play well with absolute paths, or rather
> install_megadrivers.py is doing something strange - normally gentoo
> installs everything to a temporary image path then puts those files
> into the live system. It seems install_megadrivers.py doesn't do this
> and installs directly to the live system - I worked around it by
> dropping the /usr

There's a patch from someone in FreeBSD that might fix this (the way we do
symlinking in install_megadrivers is wrong).

Sorry it took me so long to find this email, notmuch applied some odd tags to
it.

Dylan


signature.asc
Description: signature
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Few issues with Meson

[Mike Lothian]

Hi

When compiling wine I also noticed that the d3d.pc files didn't have
moduledir set, so wine couldn't find it

configure: error: pkg-config couldn't find Gallium Nine module

Regards

Mike

On Tue, 6 Mar 2018 at 02:17 Mike Lothian  wrote:

> Hi
>
> I've been trying to get a Gentoo ebuild ready for meson
>
> I've had to fudge the llvm-config for cross compiling a 32bit mesa on
> a 64bit machine
>
> I notice that -Dvulkan-drivers= doesn't accept intel,radeon like
> autotools used to, it also seems as long as one value is correct the
> other is ignored
>
> Also -Dva-libs-path= doesn't play well with absolute paths, or rather
> install_megadrivers.py is doing something strange - normally gentoo
> installs everything to a temporary image path then puts those files
> into the live system. It seems install_megadrivers.py doesn't do this
> and installs directly to the live system - I worked around it by
> dropping the /usr
>
> The inital ebuild is in the FireBurn overlay
> (
> https://github.com/FireBurn/Overlay/blob/master/media-libs/mesa/mesa-.ebuild
> )
>
> Regards
>
> Mike
>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] Few issues with Meson

[Mike Lothian]

Hi

I've been trying to get a Gentoo ebuild ready for meson

I've had to fudge the llvm-config for cross compiling a 32bit mesa on
a 64bit machine

I notice that -Dvulkan-drivers= doesn't accept intel,radeon like
autotools used to, it also seems as long as one value is correct the
other is ignored

Also -Dva-libs-path= doesn't play well with absolute paths, or rather
install_megadrivers.py is doing something strange - normally gentoo
installs everything to a temporary image path then puts those files
into the live system. It seems install_megadrivers.py doesn't do this
and installs directly to the live system - I worked around it by
dropping the /usr

The inital ebuild is in the FireBurn overlay
(https://github.com/FireBurn/Overlay/blob/master/media-libs/mesa/mesa-.ebuild)

Regards

Mike
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev