Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] axfsutils: add new package
Date: Fri, 2 Oct 2015 22:57:37 +0100	[thread overview]
Message-ID: <20151002215737.GA4284@free.fr> (raw)
In-Reply-To: <1443796641-16056-2-git-send-email-ariel@vanguardiasur.com.ar>

Ariel, All,

On 2015-10-02 11:37 -0300, Ariel D'Alessandro spake thusly:
> Tools for building AXFS Filesystem.
> 
> The Advanced XIP File System is a Linux kernel filesystem driver that enables
> files to be executed directly from flash or ROM memory rather than being copied
> into RAM.
> 
> Source:
> 	https://github.com/jaredeh/axfs
> 
> Signed-off-by: Ariel D'Alessandro <ariel@vanguardiasur.com.ar>
> ---
>  package/axfsutils/axfsutils.mk | 21 +++++++++++++++++++++
>  1 file changed, 21 insertions(+)
>  create mode 100644 package/axfsutils/axfsutils.mk
> 
> diff --git a/package/axfsutils/axfsutils.mk b/package/axfsutils/axfsutils.mk
> new file mode 100644
> index 0000000..ef8d471
> --- /dev/null
> +++ b/package/axfsutils/axfsutils.mk
> @@ -0,0 +1,21 @@
> +################################################################################
> +#
> +# axfsutils
> +#
> +################################################################################
> +
> +AXFSUTILS_VERSION = f26ae785e33df76f658b71ef2cfbc7f511ff875d
> +AXFSUTILS_SITE = $(call github,jaredeh,axfs,$(AXFSUTILS_VERSION))
> +AXFSUTILS_LICENSE = GPLv2
> +AXFSUTILS_LICENSE_FILES = COPYING
> +
> +define HOST_AXFSUTILS_BUILD_CMDS
> +	$(HOST_MAKE_ENV) $(MAKE) -C $(@D)/mkfs.axfs-legacy
> +endef
> +
> +define HOST_AXFSUTILS_INSTALL_CMDS
> +	cp $(@D)/mkfs.axfs-legacy/mkfs.axfs $(HOST_DIR)/usr/bin/
> +endef
> +
> +$(eval $(generic-package))

Since you do not add a Config.in that provides the corresponding option
BR2_PACKAGE_AXFSUTILS for this package, it will never be buildable for
the target.

So, either you provide a Config.in that adds BR2_PACKAGE_AXFSUTILS (like
is done for e2fsprogs, for example), or you do not add a call to $(generic-package)

Regards,
Yann E. MORIN.

> +$(eval $(host-generic-package))
> -- 
> 1.9.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-10-02 21:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 14:37 [Buildroot] [PATCH 0/2] Add support for AXFS filesystem type Ariel D'Alessandro
2015-10-02 14:37 ` [Buildroot] [PATCH 1/2] axfsutils: add new package Ariel D'Alessandro
2015-10-02 21:57   ` Yann E. MORIN [this message]
2015-10-05 11:03     ` Ariel D'Alessandro
2015-10-02 14:37 ` [Buildroot] [PATCH 2/2] axfs: add new filesystem type Ariel D'Alessandro

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=20151002215737.GA4284@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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