[prev in list] [next in list] [prev in thread] [next in thread]
List: cairo
Subject: Re: [cairo] Dev setup for cairo - containers ?
From: Tim-Philipp =?ISO-8859-1?Q?M=FCller?= <t.i.m () zen ! co ! uk>
Date: 2022-09-16 13:20:13
Message-ID: 889dce336d5cbfd8620470a57ae0cc69fd36e37f.camel () zen ! co ! uk
[Download RAW message or body]
On Fri, 2022-09-16 at 11:12 +0000, Stuart Axon wrote:
Hi Stuart,
> Dev env sounds useful (I'm used to python which has something that
> seems analogous).
>
> I'm very new to meson, I noticed there are .wrap files.
>
> Is it possible to have a .wrap file to have cairo as a dependency and
> change some config, e.g. to enable a non-default cairo back-end ?
That's right, that should be possible. You can make a 'subproject()'
call in your superproject meson.build to always force use of it as a
subproject so it never tries the system dependency.
You also don't necessarily need a devenv then - on Linux at least any
binaries in the build directory built as part of the meson build should
be using rpath as far as I know, so should pick up the libcairo from
the in-build-tree subproject build then.
Cheers
Tim
[Attachment #3 (text/html)]
<html><head></head><body><div>On Fri, 2022-09-16 at 11:12 +0000, Stuart Axon \
wrote:</div><div><br></div><div>Hi Stuart,</div><div><br></div><blockquote \
type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf \
solid;padding-left:1ex"><div class="ydpb3d12c79yahoo-style-wrap" \
style="font-family:Helvetica Neue, Helvetica, Arial, \
sans-serif;font-size:13px;"><div><div dir="ltr" data-setdir="false">Dev env sounds \
useful (I'm used to python which has something that seems analogous).</div><div \
dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">I'm very \
new to meson, I noticed there are .wrap files.</div><div dir="ltr" \
data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Is it possible to \
have a .wrap file to have cairo as a dependency and change some config, e.g. to \
enable a non-default cairo back-end \
?<br></div></div></div></blockquote><div><br></div><div>That's right, that should be \
possible. You can make a 'subproject()' call in your superproject meson.build to \
always force use of it as a subproject so it never tries the system \
dependency.</div><div><br></div><div>You also don't necessarily need a devenv then - \
on Linux at least any binaries in the build directory built as part of the meson \
build should be using rpath as far as I know, so should pick up the libcairo from the \
in-build-tree subproject build \
then.</div><div><br></div><div>Cheers</div><div> Tim</div><div><br></div><div><span></span></div></body></html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic