From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add syslinux installer host package
Date: Sun, 11 Nov 2018 22:03:10 -0200 (BRST) [thread overview]
Message-ID: <1370627641.1453046.1541980990981.JavaMail.zimbra@datacom.com.br> (raw)
In-Reply-To: <20181111213316.18f86c81@windsurf.home>
> From: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
> To: "Alexander Sverdlin" <alexander.sverdlin@gmail.com>
> Cc: "buildroot" <buildroot@buildroot.org>, "Carlos Santos" <casantos@datacom.ind.br>
> Sent: Domingo, 11 de novembro de 2018 18:33:16
> Subject: Re: [Buildroot] [PATCH] Add syslinux installer host package
> Hello,
>
> Thanks for this contribution! I'm adding Carlos Santos, who also uses
> syslinux.
>
> On Sun, 11 Nov 2018 16:06:47 +0100, Alexander Sverdlin wrote:
>> Add host installer for syslinux bootloader which allows to pre-install
>> syslinux in the generated firmware images. BR2_ROOTFS_POST_IMAGE_SCRIPT
>> can do something like this:
>>
>> ${HOST_DIR}/usr/bin/syslinux -d /syslinux/ -i ${IMGFILE}
>>
>> if the rest of syslinux is installed under /syslinux inside the firmware
>> image.
>>
>> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@gmail.com>
>> ---
>> package/Config.in.host | 1 +
>> package/syslinux-installer/Config.in.host | 7 +++++++
>> package/syslinux-installer/syslinux.mk | 25 +++++++++++++++++++++++
>
> Instead of making a separate package for this, what about adding a host
> variant of the existing syslinux package ?
host-sylinux makes sense. The package would not build syslinux for the
host, just the installer, but this would not be a real problem, since
host packages are meant to be tools used to generate the target system.
--
Carlos Santos (Casantos) - DATACOM, P&D
?Marched towards the enemy, spear upright, armed with the certainty
that only the ignorant can have.? ? Epitaph of a volunteer
next prev parent reply other threads:[~2018-11-12 0:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 15:06 [Buildroot] [PATCH] libtool: Make libltdl a separate package Alexander Sverdlin
2018-11-11 15:06 ` [Buildroot] [PATCH] Add syslinux installer host package Alexander Sverdlin
2018-11-11 20:33 ` Thomas Petazzoni
2018-11-12 0:03 ` Carlos Santos [this message]
2018-11-11 15:06 ` [Buildroot] [PATCH] linux-tools: Add liblockdep Alexander Sverdlin
2018-11-11 21:53 ` Thomas Petazzoni
2018-11-11 15:06 ` [Buildroot] [PATCH] Add mini-snmpd package Alexander Sverdlin
2018-11-13 21:52 ` Thomas Petazzoni
2018-11-22 17:55 ` Alexander Sverdlin
2018-11-11 15:06 ` [Buildroot] [PATCH] acpid: Add systemd service Alexander Sverdlin
2018-11-11 20:46 ` Thomas Petazzoni
2018-11-11 15:06 ` [Buildroot] [PATCH] acpid: Make bundled event files optional Alexander Sverdlin
2018-11-11 20:50 ` Thomas Petazzoni
2018-11-11 23:36 ` Carlos Santos
2018-11-11 15:06 ` [Buildroot] [PATCH] systemd: Explicitly configure split-usr=false and split-bin=true Alexander Sverdlin
2018-11-11 16:34 ` Yann E. MORIN
2018-11-11 20:55 ` Thomas Petazzoni
2018-11-11 23:41 ` Alexander Sverdlin
2018-11-12 8:08 ` Yann E. MORIN
2018-11-13 22:19 ` Alexander Sverdlin
2018-11-11 21:17 ` [Buildroot] [PATCH] libtool: Make libltdl a separate package Thomas Petazzoni
2018-11-11 22:15 ` Arnout Vandecappelle
2018-11-12 8:06 ` Yann E. MORIN
2018-11-22 19:02 ` Alexander Sverdlin
2018-11-23 8:04 ` Thomas Petazzoni
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=1370627641.1453046.1541980990981.JavaMail.zimbra@datacom.com.br \
--to=casantos@datacom.com.br \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.