Age | Commit message (Collapse) | Author | Files |
|
|
|
python () {} and python __anonymous () {} are as the same
says functions without a name. They get executed when the
main bb file is completely parsed. This is used to set
information like FILESDIR.
This is a python method so it gets evaled which means compiled
and executed a lot of times. By moving the code of the anonfunc
into a proper method this is only compiled once. The result is
is the 10% speed up when parsing.
Reindent anonfuncs and new defs without tabs and four spaces
|
|
|
|
|
|
|
|
files can be created. Add a new class to handle this. Based on the work of Jamie Lenehan, with changes from me. This commit creates a common x86 file and the arm configs are merged but much work still remains.
|
|
RRECOMMENDS, from Poky
* poky rev 823: 'package.bbclass: depchains: don't -destructively- set the pkg's RRECOMMENDS.'
* poky rev 824: 'base.bbclass: depchains: don't -destructively- set the pkg's RRECOMMENDS.'
|
|
|
|
then package_write which actually generates the packages. The two stage approach allows us to avoid circular dependency issues from classes like debian.bbclass. As the data being emitted into pkgdata/ changed, you need to either wipe tmp or rerun the do_package tasks (wipe the do_package stamps). Everything will repackage anyway due to the new task.
|
|
functional changes (from poky)
|
|
|
|
and all its dependencies (requires bitbake trunk)
|
|
format
|
|
|
|
inside ${D}
|
|
the task reordering
|
|
other packages.
|
|
suffixed with version properly.
* Sometimes soname of a shlib is overriden to contain extra version. If
it's build by libtool, .la still has basename w/o suffix. This fix recognizes
such case, and handles shlib installation properly (via libtool).
* Example of this is smpeg_0.4.4+0.4.5cvs20040311 which builds libsmpeg-0.4,
while still being linked as -lsmpeg.
Fixes #1389.
|
|
|
|
Rework the way patches are handled. There are now two abstract base classes,
initialized in patch.bbclass. One for patchset operations on a directory, and
another for patch failure resolution. Currently includes 'patch' and 'quilt'
concrete PatchSet classes, and a 'user' resolver class, which simply drops you
into a shell in the source tree to fix the rejects.
|
|
for the new task-machine code (from poky)
|
|
to. Should be backwards compatible.
|
|
package if we want
|
|
|
|
* this will force a full rebuild, so have some coffee + cookies ready
|
|
multithreading version of bitbake. Also, set BB_DEFAULT_TASK to specify the default task (build) rather than hardcode into bitbake.
|
|
Make the find invocation portable (BSD) by specifying '.'
as the to be searched directory.
The error on libtool-native was:
find: illegal option -- n
find: illegal option -- a
find: illegal option -- m
find: illegal option -- e
|
|
* Fix an issue with file:// urls in SRC_URI which reside in WORKDIR. With
this issue fixed, patches within tarballs can be successfully applied to
${S}.
|
|
|
|
|
|
|
|
Add CTAN mirror. A German/Berlin, Japan and an
Australian one.
|
|
(import bb.manifest)
|
|
Add two european and one north american mirror
for gnupg.
|
|
|
|
- SRC_URI = "file//something.patch;patch=1;mindate=20050312;maxdate=20060302
means that patch should be applied if SRCDATE > 20050312 and SRCDATE < 20060302
|
|
|
|
get the position of the MT directory
|
|
* it isn't a mandatory var, but very usefull for debugging user problems
|
|
- attach 'g' to the s/${WORKDIR}/${STAGING_LIBDIR}/ sed rule
to fix up multiple references to yet unstaged .la files
|
|
compatible with. Update documentation.conf accordingly.
|
|
is not present
This is necessary due to the new RDEPENDS handling. I don't feel 100% comfortable with it,
but until we rework the complete staging-shouldn't-contain-dependency-information, this is
our way.
|
|
|
|
|
|
x.x.x+cvsYYYYMMDD format and some includes some minor whitespace cleanup.
|
|
oe_libinstall and install aclocal macros, too
|
|
- when using oe_libinstall to install a libtool library (.la file
- present) into the staging directory (${STAGING_LIBDIR}) fix up the
- installed .lai file so that it contains 'installed=no' - this
- prevents libtool from subsequently using a copy of the build system
- library if it exists in the final (target) installation directory
- on the build machine (typically /usr/lib). Remove the patches from
- pcre_4.4.bb to match (it now seems to work without them), add
- cherokee to the openslug (etc) build (it was failing because of this
- problem.)
|
|
update our descriptions to work with any version of cp. Patches that include
cp -a are not changed. They seem to work and I'm too scared busybox cp
is more like GNU cp than BSD cp. (e.g do not know about P)
|
|
valid MT repository) in OE Build Configuration
|
|
Change oe_libinstall (watch carefully):
If the user requires the installation of a static library and it
does not exist we want the user to notice and fail. I assume this
was then intended purpose for the requirestatic variable.
The matter for the dotlai (.lai) is a bit different. The system
automatically detects the .la file and assumes it is libtool generated
and wants to install the .lai file even if it does not exist. I think
this is wrong and I change it to do the following:
If it decides it has libtool it installs the .lai if it is present.
(change the -o to -a)
At least Qt Version 3 has a .la but no .lai in its library directory
and oe_libinstall fails to install.
|