[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] RFC on providing a more meaningful error message for swig-py

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Fri, 04 Jan 2019 14:45:59 +0000

Branko Čibej wrote on Fri, 04 Jan 2019 08:11 +0100:
> On 04.01.2019 04:33, Troy Curtis Jr wrote:
> > $ make swig-py

> > swig error : Unrecognized option none

> > So instead with the attached patch you get something like:
> >
> > $ make swig-py
> > SWIG Python bindings not configured, py3c library not found
> > make: *** [Makefile:924: verify-swig-py] Error 1

> > 1) Whether I should bother
>
>
> Please do! I know I've been bitten by the same helpful message, and I
> know my way around the build scripts better than the average user.
>

+1, those "none: command not found" errors are unhelpful and a bug.

We already handle this for the «@SWIG@ = none» case (see
build/generator/templates/build-outputs.mk.ezt:87) but it would be nice to
handle other cases as well.
Received on 2019-01-04 15:46:08 CET

This is an archived mail posted to the Subversion Dev mailing list.