From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] fmc: new package
Date: Tue, 10 Jun 2014 22:21:48 +0200 [thread overview]
Message-ID: <20140610222148.3ad9a8e7@free-electrons.com> (raw)
In-Reply-To: <1402412526-24844-4-git-send-email-matthew.weber@rockwellcollins.com>
Dear Matt Weber,
On Tue, 10 Jun 2014 08:02:06 -0700, Matt Weber wrote:
> diff --git a/package/fmc/Config.in b/package/fmc/Config.in
> new file mode 100644
> index 0000000..9530756
> --- /dev/null
> +++ b/package/fmc/Config.in
> @@ -0,0 +1,14 @@
> +config BR2_PACKAGE_FMC
> + bool "fmc"
> + depends on BR2_powerpc_e500mc
> + select BR2_PACKAGE_TCLAP
Propagate the C++ dependency of tclap here.
> + select BR2_PACKAGE_LIBXML2
> + select BR2_PACKAGE_FMLIB
> + help
> + The Frame Manager Configuration tool is a software package whose primary
> + purpose is converting Parse-Classify-Police-Distribute (PCD) descriptions of
> + network packets flow into hardware configuration. The tool provides an
> + abstraction layer between the end customer's vision of the PCD task
> + definition and real hardware implementation.
Length of lines too long. It would be good to mention that it's
specific to Freescale PowerPC machines at the beginning of the
description.
> +
> + http://cache.freescale.com/files/32bit/doc/app_note/AN4760.pdf
> diff --git a/package/fmc/fmc.mk b/package/fmc/fmc.mk
> new file mode 100644
> index 0000000..513a8ef
> --- /dev/null
> +++ b/package/fmc/fmc.mk
> @@ -0,0 +1,31 @@
> +###############################################################################
> +#
> +# fmc
> +#
> +###############################################################################
> +
> +FMC_VERSION = fsl-sdk-v1.5-rc3
> +FMC_SITE = git://git.freescale.com/ppc/sdk/fmc.git
> +FMC_LICENSE = MIT
> +FMC_LICENSE_FILES = COPYING
> +FMC_DEPENDENCIES = libxml2 tclap fmlib
> +
> +FMC_MAKE_OPTS = \
> + CC="$(TARGET_CC)" \
> + CXX="$(TARGET_CXX)" \
> + FMD_USPACE_HEADER_PATH="$(STAGING_DIR)/usr/include/fmd" \
> + FMD_USPACE_LIB_PATH="$(STAGING_DIR)/usr/lib" \
> + LIBXML2_HEADER_PATH="$(STAGING_DIR)/usr/include/libxml2" \
> + TCLAP_HEADER_PATH="$(STAGING_DIR)/usr/include"
> +
> +define FMC_BUILD_CMDS
> + # The linking step has dependency issues so using MAKE1
> + $(TARGET_MAKE_ENV) $(MAKE1) $(FMC_MAKE_OPTS) -C $(@D)/source
> +endef
> +
> +define FMC_INSTALL_TARGET_CMDS
> + $(INSTALL) -D -m 0755 $(@D)/source/fmc $(TARGET_DIR)/usr/sbin/fmc
> + cp -dr --no-preserve=ownership $(@D)/etc/fmc $(TARGET_DIR)/etc/
Do we need this --no-preserve=ownership here? We usually use:
cp -dpfr
in Buildroot.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-10 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 15:02 [Buildroot] [PATCH 0/3] Support for the Freescale frame manager utility Matt Weber
2014-06-10 15:02 ` [Buildroot] [PATCH 1/3] fmlib: new package Matt Weber
2014-06-10 20:01 ` Thomas Petazzoni
2014-06-11 2:06 ` Matthew Weber
2014-06-10 15:02 ` [Buildroot] [PATCH 2/3] tclap: " Matt Weber
2014-06-10 20:11 ` Thomas Petazzoni
2014-06-11 2:03 ` Matthew Weber
2014-06-10 15:02 ` [Buildroot] [PATCH 3/3] fmc: " Matt Weber
2014-06-10 20:21 ` Thomas Petazzoni [this message]
2014-06-11 2:00 ` Matthew Weber
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=20140610222148.3ad9a8e7@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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