| Age | Commit message (Collapse) | Author | Files |
|---|
|
Adds a base_path_out convenience function, which prepares a full path for
display to the user. The initial implementation just makes it relative to
${TOPDIR}. This function is then used for some messages outputted to the
user (packaged-staging, patch application, clean, unpack tasks).
Signed-off-by: Chris Larson <clarson@mvista.com>
|
|
OpenEmbedded outputs a lot of messages that the user is likely to never
care about. We should only output something when it reflects upon their
recipe (i.e. unpacking their sources, applying their patches), or is quite
significant or unusual.
Signed-off-by: Chris Larson <clarson@mvista.com>
|
|
|
|
Comment on what this function is used for primarily. The default
gcc3-native that we build is called 'gcc-3.4.6' so look for that one
first.
|
|
Gives us guaranteed sane GNU coreutils on any host. Should greatly ease
support for various non-GNU host systems and allow to safely remove some other
native packages like 'install-native'.
Acked-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
This makes it possible for overlays to have checksum.ini.
Signed-off-by: Petri Lehtinen <petri.lehtinen@inoi.fi>
Acked-by: Khem Raj <raj.khem@gmail.com>
Acked-by: Denys Dmytriyenko <denis@denix.org>
Acked-by: Chris Larson <clarson@kergoth.com>
Acked-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Signed-off-by: Chris Larson <clarson@mvista.com>
|
|
the url.
Signed-off-by: Chris Larson <clarson@mvista.com>
|
|
Signed-off-by: Chris Larson <clarson@kergoth.com>
|
|
removed.
Also added a deprecation message to it.
Signed-off-by: Chris Larson <clarson@kergoth.com>
|
|
base_path_relative returns a relative path from src to dest.
Examples:
>>> base_path_relative("/usr/bin", "/tmp/foo/bar")
../../tmp/foo/bar
>>> base_path_relative("/usr/bin", "/usr/lib")
../lib
>>> base_path_relative("/tmp", "/tmp/foo/bar")
foo/bar
Signed-off-by: Chris Larson <clarson@mvista.com>
|
|
here.
Now a distro or machine can add their own variables to display.
Signed-off-by: Chris Larson <clarson@mvista.com>
|
|
Signed-off-by: Chris Larson <clarson@mvista.com>
|
|
Currently, if the first item in BBFILES isn't in the main OE repository,
the build fails entirely due to a ValueError. This isn't optimal. Rather
than searching through BBFILES to find it, which could be slow when
BBFILES contains thousands of files, let's just find base.bbclass and use
that repository.
Also, use better methods to find the git revision and branch, and identify
the scm based on the existance of .svn/.git/_MTN to avoid calling out
subprocesses unnecessarily.
Signed-off-by: Chris Larson <clarson@mvista.com>
|
|
Now that bitbake operates at a task level, not a package level, the
package messages are, at best, useless, and at worst, confusing for the
user.
Signed-off-by: Chris Larson <clarson@mvista.com>
|
|
Rework FILESPATH generation to be done in bitbake.conf, avoiding the
confusion about it being in multiple places. Adds FILESPATHBASE and
FILESPATHPKG which can be manipulated rather than manipulating FILESPATH
directly.
One usage possibility:
FILESPATHBASE =. "${TOPDIR}/files:"
Which would let me provide a custom busybox config for this build by
copying the defconfig from the openembedded metadata into my
build/files/busybox-1.0/ directory, for example.
Signed-off-by: Chris Larson <clarson@mvista.com>
|
|
git-svn-id: https://svn.o-hand.com/repos/poky@5389 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
to packages/ while parsing BBFILES
Signed-off-by: Denys Dmytriyenko <denis@denix.org>
Acked-by: Mike Westerhof <mwester@dls.net>
Acked-by: Philip Balister <philip@balister.org>
Acked-by: Khem Raj <raj.khem@gmail.com>
Acked-by: Marcin Juszkiewicz <hrw@openembedded.org>
Acked-by: Koen Kooi <koen@openembedded.org>
Acked-by: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
|
|
before (with BitBake trunk):
NOTE: package linux-2.6.28-r4: task do_compile: started
NOTE: package linux-2.6.28-r4: task do_compile: Started
after:
NOTE: package linux-2.6.28-r4: task do_compile: Started
|
|
is set * we want to error out on non-matching sums, missing ones are less bad
* People can now set OE_STRICT_CHECKSUMS = "" in local.conf to make a missing checksum a warning, but checksum errors are still fatal, as it should
|
|
|
|
|
|
My python is rusty :)
|
|
|
|
|
|
|
|
base.bbclass: Added base_package_name python function.
java-library.bbclass: Removed java_back_package_name function.
bitbake.conf: Set BP/BPN and use it in FILESPATH and S
|
|
|
|
|
|
|
|
and 'aa5ca25b387398015df6ff4983a31df9f74a3dff'
|
|
|
|
* tested on beagleboard, dht-walnut, efika, c7x0 and om-gta01
* python, perl, gtk and qt4-x11 build and work
* console-image, x11-image and beagleboard-demo-image build and work as well
* see http://lists.linuxtogo.org/pipermail/openembedded-devel/2008-July/005819.html
|
|
discussed on the mailing list. Anyone wanting the previous layout can INHERIT the new singlemachine class
|
|
|
|
so easier to add git/hg (from Poky)
|
|
unique. Acked by RP
|
|
|
|
|
|
recent bitbake versions and improving interaction with packaged staging. WARNING: The result of this commit on existing builds is they will effectively rebuild from scratch.
|
|
Broke rebuilds when disabled.
|
|
base.bbclass and add shell version
|
|
|
|
|
|
|
|
bitbake. Bitbake 1.8.10 users should be unaffected, bitbake 1.8.11 users will need the latest svn stable branch bitbake. Only the rebuild task is affected by the changes
|
|
|
|
|
|
|
|
* applies only to kernel later than 2.6.17
* added base_version_less_or_equal function to base.bbclass (thanks, zecke and mickey!)
to do the comparison. This does not change existing functionality. Skipped RFC.
|
