diff options
| -rw-r--r-- | .templateconf | 2 | ||||
| -rw-r--r-- | meta/conf/bblayers.conf.sample | 15 | ||||
| -rw-r--r-- | meta/conf/local.conf.sample | 209 | ||||
| -rw-r--r-- | meta/conf/local.conf.sample.extended | 374 | ||||
| -rw-r--r-- | meta/conf/site.conf.sample | 31 | ||||
| -rw-r--r-- | tizen-common-init-build-env | 52 | ||||
| -rw-r--r-- | tizen-ivi-init-build-env | 52 |
7 files changed, 734 insertions, 1 deletions
diff --git a/.templateconf b/.templateconf index 0650a46625..0bf5ecf1e5 100644 --- a/.templateconf +++ b/.templateconf @@ -1,2 +1,2 @@ # Template settings -TEMPLATECONF=${TEMPLATECONF:-meta-yocto/conf} +TEMPLATECONF=${TEMPLATECONF:-meta/conf} diff --git a/meta/conf/bblayers.conf.sample b/meta/conf/bblayers.conf.sample new file mode 100644 index 0000000000..518da7402c --- /dev/null +++ b/meta/conf/bblayers.conf.sample @@ -0,0 +1,15 @@ +# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf +# changes incompatibly +LCONF_VERSION = "5" + +BBPATH = "${TOPDIR}" +BBFILES ?= "" + +BBLAYERS ?= " \ + ##OEROOT##/meta \ + " + +BBLAYERS_NON_REMOVABLE ?= " \ + ##OEROOT##/meta \ + " + diff --git a/meta/conf/local.conf.sample b/meta/conf/local.conf.sample new file mode 100644 index 0000000000..6b5250a50f --- /dev/null +++ b/meta/conf/local.conf.sample @@ -0,0 +1,209 @@ +# +# This file is your local configuration file and is where all local user settings +# are placed. The comments in this file give some guide to the options a new user +# to the system might want to change but pretty much any configuration option can +# be set in this file. More adventurous users can look at local.conf.extended +# which contains other examples of configuration which can be placed in this file +# but new users likely won't need any of them initially. +# +# Lines starting with the '#' character are commented out and in some cases the +# default values are provided as comments to show people example syntax. Enabling +# the option is a question of removing the # character and making any change to the +# variable as required. + +# +# Machine Selection +# +# You need to select a specific machine to target the build with. There are a selection +# of emulated machines available which can boot and run in the QEMU emulator: +# +#MACHINE ?= "qemuarm" +#MACHINE ?= "qemumips" +#MACHINE ?= "qemuppc" +#MACHINE ?= "qemux86" +#MACHINE ?= "qemux86-64" +# +# This sets the default machine to be qemux86 if no other machine is selected: +MACHINE ??= "qemux86" + +# +# Where to place downloads +# +# During a first build the system will download many different source code tarballs +# from various upstream projects. This can take a while, particularly if your network +# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you +# can preserve this directory to speed up this part of subsequent builds. This directory +# is safe to share between multiple builds on the same machine too. +# +# The default is a downloads directory under TOPDIR which is the build directory. +# +#DL_DIR ?= "${TOPDIR}/downloads" + +# +# Where to place shared-state files +# +# BitBake has the capability to accelerate builds based on previously built output. +# This is done using "shared state" files which can be thought of as cache objects +# and this option determines where those files are placed. +# +# You can wipe out TMPDIR leaving this directory intact and the build would regenerate +# from these files if no changes were made to the configuration. If changes were made +# to the configuration, only shared state files where the state was still valid would +# be used (done using checksums). +# +# The default is a sstate-cache directory under TOPDIR. +# +#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" + +# +# Where to place the build output +# +# This option specifies where the bulk of the building work should be done and +# where BitBake should place its temporary files and output. Keep in mind that +# this includes the extraction and compilation of many applications and the toolchain +# which can use Gigabytes of hard disk space. +# +# The default is a tmp directory under TOPDIR. +# +#TMPDIR = "${TOPDIR}/tmp" + + +# +# Package Management configuration +# +# This variable lists which packaging formats to enable. Multiple package backends +# can be enabled at once and the first item listed in the variable will be used +# to generate the root filesystems. +# Options are: +# - 'package_deb' for debian style deb files +# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) +# - 'package_rpm' for rpm style packages +# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" +# We default to ipk: +PACKAGE_CLASSES ?= "package_ipk" + +# +# SDK/ADT target architecture +# +# This variable specifies the architecture to build SDK/ADT items for and means +# you can build the SDK packages for architectures other than the machine you are +# running the build on (i.e. building i686 packages on an x86_64 host). +# Supported values are i686 and x86_64 +#SDKMACHINE ?= "i686" + +# +# Extra image configuration defaults +# +# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated +# images. Some of these options are added to certain image types automatically. The +# variable can contain the following options: +# "dbg-pkgs" - add -dbg packages for all installed packages +# (adds symbol information for debugging/profiling) +# "dev-pkgs" - add -dev packages for all installed packages +# (useful if you want to develop against libs in the image) +# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages +# (useful if you want to run the package test suites) +# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) +# "tools-debug" - add debugging tools (gdb, strace) +# "eclipse-debug" - add Eclipse remote debugging support +# "tools-profile" - add profiling tools (oprofile, exmap, lttng, valgrind) +# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) +# "debug-tweaks" - make an image suitable for development +# e.g. ssh root access has a blank password +# There are other application targets that can be used here too, see +# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. +# We default to enabling the debugging tweaks. +EXTRA_IMAGE_FEATURES = "debug-tweaks" + +# +# Additional image features +# +# The following is a list of additional classes to use when building images which +# enable extra features. Some available options which can be included in this variable +# are: +# - 'buildstats' collect build statistics +# - 'image-mklibs' to reduce shared library files size for an image +# - 'image-prelink' in order to prelink the filesystem image +# - 'image-swab' to perform host system intrusion detection +# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink +# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended +USER_CLASSES ?= "buildstats image-mklibs image-prelink" + + +# +# Runtime testing of images +# +# The build system can test booting virtual machine images under qemu (an emulator) +# after any root filesystems are created and run tests against those images. To +# enable this uncomment this line. See classes/testimage(-auto).bbclass for +# further details. +#TEST_IMAGE = "1" +# +# Interactive shell configuration +# +# Under certain circumstances the system may need input from you and to do this it +# can launch an interactive shell. It needs to do this since the build is +# multithreaded and needs to be able to handle the case where more than one parallel +# process may require the user's attention. The default is iterate over the available +# terminal types to find one that works. +# +# Examples of the occasions this may happen are when resolving patches which cannot +# be applied, to use the devshell or the kernel menuconfig +# +# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none +# Note: currently, Konsole support only works for KDE 3.x due to the way +# newer Konsole versions behave +#OE_TERMINAL = "auto" +# By default disable interactive patch resolution (tasks will just fail instead): +PATCHRESOLVE = "noop" + +# +# Disk Space Monitoring during the build +# +# Monitor the disk space during the build. If there is less that 1GB of space or less +# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully +# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort +# of the build. The reason for this is that running completely out of space can corrupt +# files and damages the build in ways which may not be easily recoverable. +BB_DISKMON_DIRS = "\ + STOPTASKS,${TMPDIR},1G,100K \ + STOPTASKS,${DL_DIR},1G,100K \ + STOPTASKS,${SSTATE_DIR},1G,100K \ + ABORT,${TMPDIR},100M,1K \ + ABORT,${DL_DIR},100M,1K \ + ABORT,${SSTATE_DIR},100M,1K" + +# +# Shared-state files from other locations +# +# As mentioned above, shared state files are prebuilt cache data objects which can +# used to accelerate build time. This variable can be used to configure the system +# to search other mirror locations for these objects before it builds the data itself. +# +# This can be a filesystem directory, or a remote url such as http or ftp. These +# would contain the sstate-cache results from previous builds (possibly from other +# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the +# cache locations to check for the shared objects. +# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH +# at the end as shown in the examples below. This will be substituted with the +# correct path within the directory structure. +#SSTATE_MIRRORS ?= "\ +#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ +#file://.* file:///some/local/dir/sstate/PATH" + + +# +# Qemu configuration +# +# By default qemu will build with a builtin VNC server where graphical output can be +# seen. The two lines below enable the SDL backend too. This assumes there is a +# libsdl library available on your build system. +PACKAGECONFIG_append_pn-qemu-native = " sdl" +PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" +ASSUME_PROVIDED += "libsdl-native" + + +# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to +# track the version of this file when it was generated. This can safely be ignored if +# this doesn't mean anything to you. +CONF_VERSION = "1" diff --git a/meta/conf/local.conf.sample.extended b/meta/conf/local.conf.sample.extended new file mode 100644 index 0000000000..1995732619 --- /dev/null +++ b/meta/conf/local.conf.sample.extended @@ -0,0 +1,374 @@ +# BBMASK is a regular expression that can be used to tell BitBake to ignore +# certain recipes. +#BBMASK = "" + +# +# Parallelism Options +# +# These two options control how much parallelism BitBake should use. The first +# option determines how many tasks bitbake should run in parallel: +# +#BB_NUMBER_THREADS ?= "4" +# +# Default to setting automatically based on cpu count +#BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}" +# +# The second option controls how many processes make should run in parallel when +# running compile tasks: +# +#PARALLEL_MAKE ?= "-j 4" +# +# Default to setting automatically based on cpu count +#PARALLEL_MAKE ?= "-j ${@oe.utils.cpu_count()}" +# +# For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would +# be appropriate for example. + + +# glibc configurability is used to reduce minimal image's size. +# the all supported glibc options are listed in DISTRO_FEATURES_LIBC +# and disabled by default. Uncomment and copy the DISTRO_FEATURES_LIBC +# and DISTRO_FEATURES definitions to local.conf to enable the options. +#DISTRO_FEATURES_LIBC = "ipv6 libc-backtrace libc-big-macros libc-bsd libc-cxx-tests libc-catgets libc-charsets libc-crypt \ +# libc-crypt-ufc libc-db-aliases libc-envz libc-fcvt libc-fmtmsg libc-fstab libc-ftraverse \ +# libc-getlogin libc-idn libc-inet libc-inet-anl libc-libm libc-locales libc-locale-code \ +# libc-memusage libc-nis libc-nsswitch libc-rcmd libc-rtld-debug libc-spawn libc-streams libc-sunrpc \ +# libc-utmp libc-utmpx libc-wordexp libc-posix-clang-wchar libc-posix-regexp libc-posix-regexp-glibc \ +# libc-posix-wchar-io" + +#DISTRO_FEATURES = "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi nfs zeroconf pci ${DISTRO_FEATURES_LIBC}" + +# If you want to get an image based on directfb without x11, Please copy this variable to build/conf/local.conf +#DISTRO_FEATURES = "alsa argp bluetooth ext2 irda largefile pcmcia usbgadget usbhost wifi xattr nfs zeroconf pci 3g directfb ${DISTRO_FEATURES_LIBC}" + +# ENABLE_BINARY_LOCALE_GENERATION controls the generation of binary locale +# packages at build time using qemu-native. Disabling it (by setting it to 0) +# will save some build time at the expense of breaking i18n on devices with +# less than 128MB RAM. +#ENABLE_BINARY_LOCALE_GENERATION = "1" + +# Set GLIBC_GENERATE_LOCALES to the locales you wish to generate should you not +# wish to perform the time-consuming step of generating all LIBC locales. +# NOTE: If removing en_US.UTF-8 you will also need to uncomment, and set +# appropriate value for IMAGE_LINGUAS. +# WARNING: this may break localisation! +#GLIBC_GENERATE_LOCALES = "en_GB.UTF-8 en_US.UTF-8" +#IMAGE_LINGUAS ?= "en-gb" + +# The following are used to control options related to debugging. +# +# Uncomment this to change the optimization to make debugging easer, at the +# possible cost of performance. +# DEBUG_BUILD = "1" +# +# Uncomment this to disable the stripping of the installed binaries +# INHIBIT_PACKAGE_STRIP = "1" +# +# Uncomment this to disable the split of the debug information into -dbg files +# INHIBIT_PACKAGE_DEBUG_SPLIT = "1" +# +# When splitting debug information, the following controls the results of the +# file splitting. +# +# .debug (default): +# When splitting the debug information will be placed into +# a .debug directory in the same dirname of the binary produced: +# /bin/foo -> /bin/.debug/foo +# +# debug-file-directory: +# When splitting the debug information will be placed into +# a central debug-file-directory, /usr/lib/debug: +# /bin/foo -> /usr/lib/debug/bin/foo.debug +# +# Any source code referenced in the debug symbols will be copied +# and made available within the /usr/src/debug directory +# +#PACKAGE_DEBUG_SPLIT_STYLE = '.debug' +# PACKAGE_DEBUG_SPLIT_STYLE = 'debug-file-directory' + +# Uncomment these to build a package such that you can use gprof to profile it. +# NOTE: This will only work with 'linux' targets, not +# 'linux-uclibc', as uClibc doesn't provide the necessary +# object files. Also, don't build glibc itself with these +# flags, or it'll fail to build. +# +# PROFILE_OPTIMIZATION = "-pg" +# SELECTED_OPTIMIZATION = "${PROFILE_OPTIMIZATION}" +# LDFLAGS =+ "-pg" + +# TCMODE controls the characteristics of the generated packages/images by +# telling poky which toolchain 'profile' to use. +# +# The default is "default" which uses the internal toolchain. With +# additional layers, it is possible to set this to use a precompiled +# external toolchain. One example is the Sourcery G++ Toolchain, support +# for which is now in the separate meta-sourcery layer: +# +# http://github.com/MentorEmbedded/meta-sourcery/ +# +# meta-sourcery can be used as a template for adding support for other +# external toolchains. See the link above for further details. +# +# TCMODE points the system to a file in conf/distro/include/tcmode-${TCMODE}.inc, +# so for meta-sourcery which has conf/distro/include/tcmode-external-sourcery.inc +# you would set it as follows: +# +# TCMODE ?= "external-sourcery" + +# mklibs library size optimization is more useful to smaller images, +# and less useful for bigger images. Also mklibs library optimization +# can break the ABI compatibility, so should not be applied to the +# images which are to be extended or upgraded later. +#This enabled mklibs library size optimization just for the specified image. +#MKLIBS_OPTIMIZED_IMAGES ?= "core-image-minimal" +#This enable mklibs library size optimization will be for all the images. +#MKLIBS_OPTIMIZED_IMAGES ?= "all" + +# Uncomment this if your host distribution provides the help2man tool. +#ASSUME_PROVIDED += "help2man-native" + +# This value is currently used by pseudo to determine if the recipe should +# build both the 32-bit and 64-bit wrapper libraries on a 64-bit build system. +# +# Pseudo will attempt to determine if a 32-bit wrapper is necessary, but +# it doesn't always guess properly. If you have 32-bit executables on +# your 64-bit build system, you likely want to set this to "0", +# otherwise you could end up with incorrect file attributes on the +# target filesystem. +# +# Default is to not build 32 bit libs on 64 bit systems, uncomment this +# if you need the 32 bits libs +#NO32LIBS = "0" + +# Uncomment the following lines to enable multilib builds +#require conf/multilib.conf +#MULTILIBS = "multilib:lib32" +#DEFAULTTUNE_virtclass-multilib-lib32 = "x86" + +# Set RPM_PREFER_COLOR to configure preferred ABI when using rpm packaging +# backend to generate a rootfs, choices are: +# 1: ELF32 wins +# 2: ELF64 wins +# 3: ELF64 N32 wins (for mips64 or mips64el only) +#RPM_PREFER_COLOR ?= "2" + +# The network based PR service host and port +# Uncomment the following lines to enable PRservice. +# Set PRSERV_HOST to 'localhost:0' to automatically +# start local PRService. +# Set to other values to use remote PRService. +#PRSERV_HOST = "localhost:0" + +# Additional image generation features +# +# The following is a list of classes to import to use in the generation of images +# currently an example class is image_types_uboot +# IMAGE_CLASSES = " image_types_uboot" + +# Incremental rpm image generation, the rootfs would be totally removed +# and re-created in the second generation by default, but with +# INC_RPM_IMAGE_GEN = "1", the rpm based rootfs would be kept, and will +# do update(remove/add some pkgs) on it. NOTE: This is not suggested +# when you want to create a productive rootfs +#INC_RPM_IMAGE_GEN = "1" + +# This is a list of packages that require a commercial license to ship +# product. If shipped as part of an image these packages may have +# implications so they are disabled by default. To enable them, +# un-comment the below as appropriate. +#LICENSE_FLAGS_WHITELIST = "commercial_gst-fluendo-mp3 \ +# commercial_gst-openmax \ +# commercial_gst-plugins-ugly \ +# commercial_lame \ +# commercial_libmad \ +# commercial_libomxil \ +# commercial_mpeg2dec \ +# commercial_qmmp" + + +# +# Disk space monitor, take action when the disk space or the amount of +# inode is running low, it is enabled when BB_DISKMON_DIRS is set. +# +# Set the directory for the monitor, the format is: +# "action,directory,minimum_space,minimum_free_inode" +# +# The "action" must be set and should be one of: +# ABORT: Immediately abort +# STOPTASKS: The new tasks can't be executed any more, will stop the build +# when the running tasks have been done. +# WARN: show warnings (see BB_DISKMON_WARNINTERVAL for more information) +# +# The "directory" must be set, any directory is OK. +# +# Either "minimum_space" or "minimum_free_inode" (or both of them) +# should be set, otherwise the monitor would not be enabled, +# the unit can be G, M, K or none, but do NOT use GB, MB or KB +# (B is not needed). +#BB_DISKMON_DIRS = "STOPTASKS,${TMPDIR},1G,100K WARN,${SSTATE_DIR},1G,100K" +# +# Set disk space and inode interval (only works when the action is "WARN", +# the unit can be G, M, or K, but do NOT use the GB, MB or KB +# (B is not needed), the format is: +# "disk_space_interval,disk_inode_interval", the default value is +# "50M,5K" which means that it would warn when the free space is +# lower than the minimum space(or inode), and would repeat the warning +# when the disk space reduces 50M (or the amount of inode reduces 5k). +#BB_DISKMON_WARNINTERVAL = "50M,5K" + +# Archive the source and put them to ${DEPLOY_DIR}/sources/. +# +#INHERIT += "archiver" +# +# The tarball for the patched source will be created by default, and you +# can configure the archiver as follow: +# +# Create archive for: +# 1) original (or unpacked) source: +#ARCHIVER_MODE[src] = "original" +# 2) patched source: (default) +#ARCHIVER_MODE[src] = "patched" +# 3) configured source: +#ARCHIVER_MODE[src] = "configured" +# +# 4) the patches between do_unpack and do_patch: +#ARCHIVER_MODE[diff] = "1" +# set the files that you'd like to exclude from the diff: +#ARCHIVER_MODE[diff-exclude] ?= ".pc autom4te.cache patches" +# +# 5) the environment data, similar to 'bitbake -e recipe': +#ARCHIVER_MODE[dumpdata] = "1" +# +# 6) the recipe (.bb and .inc): +#ARCHIVER_MODE[recipe] = "1" +# +# 7) Whether output the .src.rpm package: +#ARCHIVER_MODE[srpm] = "1" +# +# 8) Filter the license, the recipe whose license in +# COPYLEFT_LICENSE_INCLUDE will be included, and in +# COPYLEFT_LICENSE_EXCLUDE will be excluded. +#COPYLEFT_LICENSE_INCLUDE = 'GPL* LGPL*' +#COPYLEFT_LICENSE_EXCLUDE = 'CLOSED Proprietary' +# +# 9) Config the recipe type that will be archived, the type can be +# target, native, nativesdk, cross, crosssdk and cross-canadian, +# you can set one or more types. Archive all types by default. +#COPYLEFT_RECIPE_TYPES = 'target' +# + +# Remove the old image before the new one generated to save disk space +#RM_OLD_IMAGE = "1" + +# +# GCC/LD FLAGS to enable more secure code generation +# +# By including the security_flags include file you enable flags +# to the compiler and linker that cause them to generate more secure +# code, this is enabled by default in the poky-lsb distro. +# This does affect compile speed slightly. +# +# Use the following line to enable the security compiler and linker flags to your build +#require conf/distro/include/security_flags.inc + +# Image level user/group configuration. +# Inherit extrausers to make the setting of EXTRA_USERS_PARAMS effective. +#INHERIT += "extrausers" +# User / group settings +# The settings are sperated by the ; character. +# Each setting is actually a command. The supported commands are useradd, +# groupadd, userdel, groupdel, usermod and groupmod. +#EXTRA_USERS_PARAMS = "\ +#useradd -p '' tester; \ +#groupadd developers; \ +#userdel nobody; \ +#groupdel video; \ +#groupmod -g 1020 developers; \ +#usermod -s /bin/sh tester; \ +#" + +# Various packages dynamically add users and groups to the system at package +# install time. For programs that do not care what the uid/gid is of the +# resulting users/groups, the order of the install will determine the final +# uid/gid. This can lead to non-deterministic uid/gid values from one build +# to another. Use the following settings to specify that all user/group adds +# should be created based on a static passwd/group file. +# +# Note, if you enable or disable the useradd-staticids in a configured system, +# the TMPDIR may contain incorrect uid/gid values. Clearing the TMPDIR +# will correct this condition. +# +# By default the system looks in the BBPATH for files/passwd and files/group +# the default can be overriden by spefying USERADD_UID/GID_TABLES. +# +#USERADDEXTENSION = "useradd-staticids" +#USERADD_UID_TABLES = "files/passwd" +#USERADD_GID_TABLES = "files/group" +# +# In order to prevent generating a system where a dynamicly assigned uid/gid +# can exist, you should enable the following setting. This will force the +# system to error out if the user/group name is not defined in the +# files/passwd or files/group (or specified replacements.) +#USERADD_ERROR_DYNAMIC = "1" + +# Enabling FORTRAN +# Note this is not officially supported and is just illustrated here to +# show an example of how it can be done +# You'll also need your fortran recipe to depend on libgfortran +#FORTRAN_forcevariable = ",fortran" +#RUNTIMETARGET_append_pn-gcc-runtime = " libquadmath" + +# +# Kernel image features +# +# The INITRAMFS_IMAGE image variable will cause an additional recipe to +# be built as a dependency to the what ever rootfs recipe you might be +# using such as core-image-sato. The initramfs might be needed for +# the initial boot of of the target system such as to load kernel +# modules prior to mounting the root file system. +# +# INITRAMFS_IMAGE_BUNDLE variable controls if the image recipe +# specified by the INITRAMFS_IMAGE will be run through an extra pass +# through the kernel compilation in order to build a single binary +# which contains both the kernel image and the initramfs. The +# combined binary will be deposited into the tmp/deploy directory. +# NOTE: You can set INITRAMFS_IMAGE in an image recipe, but +# INITRAMFS_IMAGE_BUNDLE can only be set in a conf file. +# +#INITRAMFS_IMAGE = "core-image-minimal-initramfs" +#INITRAMFS_IMAGE_BUNDLE = "1" + +# +# IPK Hierarchical feed +# +# In some cases it may be desirable not to have all package files in the same +# directory. An example would be when package feeds are to be uploaded to a +# shared webhosting service or transferred to a Windows machine which may have +# problems with directories containing multiple thousands of files. +# +# If the IPK_HIERARCHICAL_FEED variable is set to "1", packages will be split +# between subdirectories in a similar way to how Debian package feeds are +# organised. In the hierarchical feed, package files are written to +# <outdir>/<arch>/<pkg_prefix>/<pkg_subdir>, where pkg_prefix is the first +# letter of the package file name for non-lib packages or "lib" plus the 4th +# letter of the package file name for lib packages (eg, 'l' for less, 'libc' for +# libc6). pkg_subdir is the root of the package file name, discarding the +# version and architecture parts and the common suffixes '-dbg', '-dev', '-doc', +# '-staticdev', '-locale' and '-locale-*' which are listed in +# meta/conf/bitbake.conf. +# +# If IPK_HIERARCHICAL_FEED is unset or set to any other value, the traditional +# feed layout is used where package files are placed in <outdir>/<arch>/. +# +#IPK_HIERARCHICAL_FEED = "1" +# + +# Using RPM4 +# +# Currently the rootfs_rpm code has a hard depends on rpmresolve:do_populate_sysroot, +# when using rpm4 the rpmresolve code will not compile due to a missing header file. +# That dependency needs to be removed when using RPM4, also the PREFRRED_VERSION needs +# to be set. This example shows how to enable rpm4 +# PREFERRED_VERSION_rpm = "4.11.2" +# PREFERRED_VERSION_rpm-native = "4.11.2" +# RPMROOTFSDEPENDS_remove = "rpmresolve-native:do_populate_sysroot" diff --git a/meta/conf/site.conf.sample b/meta/conf/site.conf.sample new file mode 100644 index 0000000000..c551e8fb0c --- /dev/null +++ b/meta/conf/site.conf.sample @@ -0,0 +1,31 @@ +# +# local.conf covers user settings, site.conf covers site specific information +# such as proxy server addresses and optionally any shared download location +# +# SITE_CONF_VERSION is increased each time build/conf/site.conf +# changes incompatibly +SCONF_VERSION = "1" + +# Uncomment to cause CVS to use the proxy host specified +#CVS_PROXY_HOST = "proxy.example.com" +#CVS_PROXY_PORT = "81" + +# For svn, you need to create ~/.subversion/servers containing: +#[global] +#http-proxy-host = proxy.example.com +#http-proxy-port = 81 +# + +# To use git with a proxy, you must use an external git proxy command, such as +# the one provided by scripts/oe-git-proxy.sh. To use this script, copy it to +# your PATH and uncomment the following: +#GIT_PROXY_COMMAND ?= "oe-git-proxy" +#ALL_PROXY ?= "socks://socks.example.com:1080" +#or +#ALL_PROXY ?= "https://proxy.example.com:8080" +# If you wish to use certain hosts without the proxy, specify them in NO_PROXY. +# See the script for details on syntax. + +# Uncomment this to use a shared download directory +#DL_DIR = "/some/shared/download/directory/" + diff --git a/tizen-common-init-build-env b/tizen-common-init-build-env new file mode 100644 index 0000000000..10b63a023f --- /dev/null +++ b/tizen-common-init-build-env @@ -0,0 +1,52 @@ +#!/bin/sh + +# OE Build Environment Setup Script +# +# Copyright (C) 2006-2011 Linux Foundation +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; if not, write to the Free Software +# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + +# +# Normally this is called as '. ./oe-init-build-env builddir' +# +# This works in most shells (not dash), but not all of them pass arg1 when +# being sourced. To workaround the shell limitation use "set arg1" prior +# to sourcing this script. +# + +export TEMPLATECONF="meta-tizen/meta-tizen-common-base/conf" + +if [ -n "$BASH_SOURCE" ]; then + OEROOT="`dirname $BASH_SOURCE`" +elif [ -n "$ZSH_NAME" ]; then + OEROOT="`dirname $0`" +else + OEROOT="`pwd`" +fi +if [ -n "$BBSERVER" ]; then + unset BBSERVER +fi +THIS_SCRIPT=$OEROOT/oe-init-build-env + +if [ -z "$ZSH_NAME" ] && [ "$0" = "$THIS_SCRIPT" ]; then + echo "Error: This script needs to be sourced. Please run as '. $THIS_SCRIPT'" + exit 1 +fi + +OEROOT=`readlink -f "$OEROOT"` +. $OEROOT/oe-init-build-env +unset OEROOT +unset BBPATH +unset THIS_SCRIPT
\ No newline at end of file diff --git a/tizen-ivi-init-build-env b/tizen-ivi-init-build-env new file mode 100644 index 0000000000..236f259210 --- /dev/null +++ b/tizen-ivi-init-build-env @@ -0,0 +1,52 @@ +#!/bin/sh + +# OE Build Environment Setup Script +# +# Copyright (C) 2006-2011 Linux Foundation +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; if not, write to the Free Software +# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + +# +# Normally this is called as '. ./oe-init-build-env builddir' +# +# This works in most shells (not dash), but not all of them pass arg1 when +# being sourced. To workaround the shell limitation use "set arg1" prior +# to sourcing this script. +# + +export TEMPLATECONF="meta-tizen/meta-tizen-ivi/conf/" + +if [ -n "$BASH_SOURCE" ]; then + OEROOT="`dirname $BASH_SOURCE`" +elif [ -n "$ZSH_NAME" ]; then + OEROOT="`dirname $0`" +else + OEROOT="`pwd`" +fi +if [ -n "$BBSERVER" ]; then + unset BBSERVER +fi +THIS_SCRIPT=$OEROOT/oe-init-build-env + +if [ -z "$ZSH_NAME" ] && [ "$0" = "$THIS_SCRIPT" ]; then + echo "Error: This script needs to be sourced. Please run as '. $THIS_SCRIPT'" + exit 1 +fi + +OEROOT=`readlink -f "$OEROOT"` +. $OEROOT/oe-init-build-env +unset OEROOT +unset BBPATH +unset THIS_SCRIPT
\ No newline at end of file |