On 28 August 2013 06:55, Gary Thomas g...@mlbassoc.com wrote:
Hopefully
someone will document all of this in great detail some day. (in fact I filed
a
bug to this end many years ago...)
It would appear that
https://bugzilla.yoctoproject.org/show_bug.cgi?id=1088 can now be
closed as a result
On 2013-10-02 10:37, Trevor Woerner wrote:
On 28 August 2013 06:55, Gary Thomas g...@mlbassoc.com wrote:
Hopefully
someone will document all of this in great detail some day. (in fact I filed
a
bug to this end many years ago...)
It would appear that
On Thu, Sep 5, 2013 at 1:50 AM, Paul D. DeRocco pdero...@ix.netcom.comwrote:
From: Samuel Stirtzel
If you change:
COMPRESS_CMD_gz = gzip -f -9 -c ${IMAGE_NAME}.rootfs.${type}
${IMAGE_NAME}.rootfs.${type}.gz
COMPRESS_CMD_bz2 = bzip2 -f -k ${IMAGE_NAME}.rootfs.${type}
in
From: Samuel Stirtzel
If you change:
COMPRESS_CMD_gz = gzip -f -9 -c ${IMAGE_NAME}.rootfs.${type}
${IMAGE_NAME}.rootfs.${type}.gz
COMPRESS_CMD_bz2 = bzip2 -f -k ${IMAGE_NAME}.rootfs.${type}
in [...]/meta/classes/image_types.bbclass, then can try
pbzip2 / pigz.
This raises a
On 28 August 2013 11:55, Gary Thomas g...@mlbassoc.com wrote:
In the case of 'ipk' packages, you'll need to set up the board to make use
of
the exported package sets. There are a number of ways to do this, but in
the
case of 'ipk' you can do it all in a single file. Here's an example on my
On Tue, Aug 27, 2013 at 05:10:42PM -0700, Paul D. DeRocco wrote:
From: Gary Thomas
As far as I understand, the 'do_rootfs' step in building an
image is basically
equivalent to running ${PKG_MGR} install
all_required_packages, where PKG_MGR
is your package management method of
From: Martin Jansa
Are you sure that you're not building some unnecessary IMAGE_FSTYPES?
No, I'm not sure.
Last time someone asked my why it takes so long I've added some debug
output to do_rootfs and found out that only half of the time was opkg
installing packages and the rest was
2013/8/28 Paul D. DeRocco pdero...@ix.netcom.com:
From: Martin Jansa
Are you sure that you're not building some unnecessary IMAGE_FSTYPES?
No, I'm not sure.
Last time someone asked my why it takes so long I've added some debug
output to do_rootfs and found out that only half of the time
On 2013-08-27 18:10, Paul D. DeRocco wrote:
From: Gary Thomas
As far as I understand, the 'do_rootfs' step in building an
image is basically
equivalent to running ${PKG_MGR} install
all_required_packages, where PKG_MGR
is your package management method of choice - ipk or rpm.
This seems to me
On 28 August 2013 11:55, Gary Thomas g...@mlbassoc.com wrote:
Not quite - you build the packages (recipes) on your build host, but manage
them directly on your target hardware. Of course, this assumes that your
build host and target hardware are network connected.
I threw together a minimal
I got really tired of waiting for builds on my lowly dual-core Atom
machine, so I went out and bought a nice fast machine with an i7-4770K and
a Samsung SSD. Full builds are now screechingly fast, over 10x compared to
the Atom.
But when making a tiny change, I still have to wait for do_rootfs.
On 2013-08-27 16:27, Paul D. DeRocco wrote:
I got really tired of waiting for builds on my lowly dual-core Atom
machine, so I went out and bought a nice fast machine with an i7-4770K and
a Samsung SSD. Full builds are now screechingly fast, over 10x compared to
the Atom.
But when making a tiny
From: Gary Thomas
As far as I understand, the 'do_rootfs' step in building an
image is basically
equivalent to running ${PKG_MGR} install
all_required_packages, where PKG_MGR
is your package management method of choice - ipk or rpm.
This seems to me to
be a very single-threaded
13 matches
Mail list logo
