From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arek Marud <a.marud@post.pl>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] I have a problem adding new package
Date: Sun, 30 Jan 2022 23:48:00 +0100 [thread overview]
Message-ID: <20220130234800.14da56ca@windsurf> (raw)
In-Reply-To: <YfcMrhsNq6LnkKzP@leo>
Hello Arek,
On Sun, 30 Jan 2022 23:09:50 +0100
Arek Marud <a.marud@post.pl> wrote:
> I'm trying to add new package to Buildroot. I follow Buildroot tutorial
> for autotools package. But I got an error message, and i have no idea
> what is the problem.
>
> https://gist.github.com/arekmd/c33a3a487ec73d8847c3c115f8fa3299
libonvif: installs files in /home/myname/workbench/resources/development/myproj/buildroot/buildroot/output/host/aarch64-myproj-linux-gnu/sysroot//home/myname/workbench/resources/development/myproj/buildroot/buildroot/output
Look at this path: it contains two times
/home/myname/workbench/resources/development/myproj/buildroot/buildroot/output,
and that's clearly bogus, and that's why Buildroot complains.
> ################################################################################
> #
> # libonvif
> ################################################################################
> LIBONVIF_VERSION = 1.1.1
> LIBONVIF_SOURCE = v$(LIBONVIF_VERSION).tar.gz
> LIBONVIF_SITE = https://github.com/sr99622/libonvif/archive/refs/tags
> LIBONVIF_INSTALL_STAGING = YES
> LIBONVIF_INSTALL_TARGET = YES
> LIBONVIF_CONF_OPTS = --with-libxml2 --includedir="$(STAGING_DIR)/usr/include/libxml2"
This includedir is wrong, and is perhaps the reason for the failure.
includedir is the location where libonvif will install its headers, not
where the libxml2 headers will be found. And setting
$(STAGING_DIR)/usr/include/libxml2 for includedir is incorrect, because
then at install time we pass DESTDIR=$(TARGET_DIR) (for target
installation) or DESTDIR=$(STAGING_DIR) (for staging installation).
This means that the libonvif headers will get installed in:
$(TARGET_DIR)/$(STAGING_DIR)/usr/include/libxml2
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this is the value you passed to includedir
and
$(STAGING_DIR)/$(STAGING_DIR)/usr/include/libxml2
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this is the value you passed to includedir
Hope this helps,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-30 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 22:09 [Buildroot] I have a problem adding new package Arek Marud
2022-01-30 22:48 ` Thomas Petazzoni via buildroot [this message]
2022-02-04 10:22 ` Arek Marud
2022-02-06 11:31 ` Arnout Vandecappelle
2022-02-10 6:23 ` Arek Marud
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220130234800.14da56ca@windsurf \
--to=buildroot@buildroot.org \
--cc=a.marud@post.pl \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox