| Age | Commit message (Collapse) | Author |
|---|
|
cpan-base.bbclass, and then update the cpan modules to no longer manually
specify this. Also remove references to the new removed .packlist files.
|
|
cpan-base class and update cpan_build to work with the new perl layout that
was added with perl 5.8.8.
|
|
|
|
configuration from hanging bitbake. They expect you to press y to indicate
that you are ok with the configuration. For some reason there was no problem
in bitbake 1.6 but this caused hangs in do_configure with bitbake 1.8.
|
|
perl-native. They are built with perl-native but use the
configuration information from perl. This issue wasn't showing up
with bitbake 1.6 but is with 1.8.2 where perl is configured and
compiled perl but not staged prior to moving on.
|
|
and 'e1f2e3537870e6d4a997727168dd4b5fc7824f14'
|
|
* Modify perl to install a copy of it's configuration during staging. This
will allow us to get at the perl settings for the target when building
cpan modules.
* Modify perl-native to allow selection of the host or target configuration
based on an environment variable. This will allow the cpan class to select
the appropriate configuration based on if we are building the native
package or not.
* Modify cpan.bbclass to set the environment variable to an appropriate
value to tell perl native to select the appropriate settings based on if
we are building native or target modules.
This change fixes some modules that were compiled for the host instead of
the target (libversion-perl for example) and fixes up some of cpan modules
that include additional subdirectories with their own makefiles.
|
|
Still needs work, especially uclibc part
|
|
native packages break because <buildarch>-gcc doesn't exist, just gcc. CCLD
gets us the correct CC to be used for linking in both cases, so we use that.
|
|
files for perl modules built using cpan will end up in different places
depending on which version of perl they are being built with. Modules that
explicitly set various FILES_ values were using the paths that are only
valid for the older versions of perl. Calculate and set the correct path in
cpan.bbclass and use that in the FILES_ variables so that it'll be correct
for all versions of perl.
|
|
occurences.
|
|
|
|
the file path.
|
|
|
|
and '6a5c817d2f11720452c0b470075091121ce6ab96'
|
|
and '72018d16d4bf3617a2f7efda54bde7f5b784e01a'
|
|
|
|
fixes in the shared library handling.
|
|
|
|
seems to fix #2133
|
|
This uses the installed perl configuration to determine if we are building
for the old or the new perl layout. Currently this just changes the
installation paths and always uses gcc to link, but more changes will be
added later to make the perl module building process a lot more reliable.
|
|
|
|
|
|
"localdata") as proposed by bug reporter
|
|
correct operation with bitbake 1.8.x. Old behaviour is maintained in a special legacy anonymous function in base.bbclass. The patch is an improved version of the one discussed on the mailing list.
|
|
* formally added (experimental, ARM-based) mtx-3a hardware platform used by nylon
|
|
|
|
|
|
handling as per RFC which is more compatible with bitbake 1.8+
|
|
instead of kernel-image. This allows machines to specify that the kernel-image shouldn't be included in a default rootfs, without needing kernel-image to be empty. Set RDEPENDS_kernel-base_MACHINE = for machines that need this as per a discussion on the mailing list.
|
|
Added support for building dsmg600 and nas100d images back into the nslu2 machine configuration.
|
|
gcc-cross-sdk)
|
|
dependencies for bitbake 1.8
|
|
classes/base.bbclass: Make sure shasum-native does not depend on quilt
classes/sanity.bbclass: No need to require sha256sum as we use oe_sha256sum
packages/shasum: Change the name, make the -native version not have any deps
|
|
|
|
|
|
|
|
|
|
[ftp://ftp.trolltech.com/qt/source/qtopia-core-4.3.0beta.tar.gz] is good enough
src_uri as section/groups are unique enough as well. Most of the time
(almost always) scoping PN (or PN+PV) is not necessary and in this case
the SRC_URI is good enough. Richard thank you for saying the obvious
|
|
targets.
Thanks to Jamie Lenahan for the help
|
|
|
|
conf/checksums.ini: Provide an example on how this can be used
|
|
This code uses the checksum.py from contrib/qa/checksum to verify
md5sum and sha256 on do_fetch task. This code would even allow to checksum
certain local patches.
|
|
within Import
non existing patches raised a IOError by the md5sum method which was not
catched at all and lead bitbake to exit due an unhandled exception. This
is bad for all autobuilders.
|
|
and 'e7e5983b231f05cb82978173bc4562e70543fd6a'
|
|
bootstrap libraries use them. Also, to not neat-pick which files go into
FILES_${PN}, just change default order of packages.
|
|
|
|
|
|
and 'c3806da7db88d5cd14b6cc7ed62c575f1269f6d4'
|
|
|
Jamie Lenehan
Marcin Juszkiewicz
Stelios Koroneos
Leon Woestenberg
Koen Kooi
Thomas Kunze
Martin Dietze
Richard Purdie
Rodrigo Vivi
Rod Whitby
Holger Freyther
Michael Lauer
Philipp Zabel
Paul Sokolovsky
Oyvind Repvik