Date: Sun, 24 Apr 2016 13:05:10 +0300 From: abi <abi@abinet.ru> To: freebsd-ports@freebsd.org Subject: Re: Making a port - debugging cmake check_include_file Message-ID: <571C9A56.4060505@abinet.ru> In-Reply-To: <20160424095902.GW83618@over-yonder.net> References: <571BE034.9070200@abinet.ru> <20160423215530.GP83618@over-yonder.net> <571BF713.4040607@abinet.ru> <20160424071351.GQ83618@over-yonder.net> <571C876F.3040000@abinet.ru> <20160424090004.GT83618@over-yonder.net> <571C8D61.6010200@abinet.ru> <20160424094344.GV83618@over-yonder.net> <571C968A.9060505@abinet.ru> <20160424095902.GW83618@over-yonder.net>
next in thread | previous in thread | raw e-mail | index | archive | help
You mean that the checks are passed, but actual support of V4L - is not?
V4L is the optional feature, so lack of it is not a critical error. From
what I see in cmake files is that header files are detected and several
knobs are set.
Should I check that these headers somehow used ? I don't have local or
analog video cameras :(
Or, assuming that if header files are detected and included, failure to
include them in compilation phase will lead to fatal error, I shouldn't
bother?
On 24.04.2016 12:59, Matthew D. Fuller wrote:
> On Sun, Apr 24, 2016 at 12:48:58PM +0300 I heard the voice of
> abi, and lo! it spake thus:
>> I passed -DCMAKE_REQUIRED_INCLUDES:STRING="${LOCALBASE}/include" from
>> port Makefile.
>> Looks like the best solution - no need to poke upstream or make patch.
> Interesting. It's not clear from the docs that
> CMAKE_REQUIRED_INCLUDES affects the actual build of the program (or
> anything except the check_include_file() from a look around,
> actually). Well, if it works...
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?571C9A56.4060505>