From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Seiderer Date: Thu, 14 Nov 2019 21:14:23 +0100 Subject: [Buildroot] [PATCH, next 1/1] package/libglib2: bump to version 2.62.2 In-Reply-To: References: <20191111210251.2216431-1-aduskett@gmail.com> <20191112215341.28f7b1aa@windsurf> <20191113204552.5198d038@windsurf> Message-ID: <20191114211423.555413ad@gmx.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello Adam, Thomas, On Thu, 14 Nov 2019 08:12:47 -0800, Adam Duskett wrote: > I believe it's triggered due to the `needs_exe_wrapper = true` in > package/meson/cross-compilation.conf > > On Wed, Nov 13, 2019 at 11:45 AM Thomas Petazzoni > wrote: > > > > On Wed, 13 Nov 2019 11:19:50 -0800 > > Adam Duskett wrote: > > > > > > > + # Don?t build the tests unless we can run them (either natively, in an exe wrapper, or by installing them for later use) > > > > > +-build_tests = not meson.is_cross_build() or (meson.is_cross_build() and meson.has_exe_wrapper()) or installed_tests_enabled > > > > > ++build_tests = installed_tests_enabled > > > > > > > > Why do we need to change this ? Is meson.has_exe_wrapper() true in our case ? No, for the host build it is the 'not meson.is_cross_build()' case... Regards, Peter > > > > > > > I believe so. Without the change, the tests are triggered to build. > > > I'm not sure where we are triggering has_exe_wrapper, > > > but it is indeed being triggered. > > > > It would be good to understand what is this has_exe_wrapper thing, and > > why we are triggering it. > > > > Thanks, > > > > Thomas > > -- > > Thomas Petazzoni, CTO, Bootlin > > Embedded Linux and Kernel engineering > > https://bootlin.com > _______________________________________________ > buildroot mailing list > buildroot at busybox.net > http://lists.busybox.net/mailman/listinfo/buildroot