Hi Hans,
On Fri, Sep 23, 2022 at 12:54:34PM +0200, Hans Verkuil wrote:
> On 09/09/2022 15:44, Laurent Pinchart wrote:
> > Hello everybody,
> >
> > This series is the latest (and greatest) attempt to switch v4l-utils
> > from autotools to meson.
> >
> > Compared to v6, the first noticeable change is that fixups have been
> > squashed into their corresponding commit. Detailed changelogs are now
> > included in individual patches.
> >
> > The second big change is that the last patch from v6 ("Makefile.am:
> > Distribute meson related files") got replaced by 5/5 which drops
> > autotools support, completing the switch from autotools to meson.
> >
> > A branch that includes this series can be found at
> >
> > git://linuxtv.org/pinchartl/v4l-utils.git meson
>
> I'm trying to use this new build system in our internal cross compilation
> environment, and I am running into problems.
>
> What we did with the autotools setup is to configure everything, but just
> build a select set of utilities from the utils directory, without needing to
> link to anything in lib. So basically: cd utils/v4l2-ctl; make; make install
>
> Trying to cross compile in lib fails with strange errors, but I don't really
> want to build anything in lib anyway, I don't need it at all.
>
> Is there a way to tell ninja to build just one utility? Or are you forced to
> build everything?
You can build targets individually, for instance
ninja utils/v4l2-ctl/v4l2-ctl
--
Regards,
Laurent Pinchart
