nyuuzyou/wikis huggingface dataset:
Relocation Notes

Techniques:
* KDE Applications
** KStandardDirs class
Interesting resources:
* Relocation macros in the Autoconf Macro Archive
** AX_COMPUTE_RELATIVE_PATHS(PATH-LIST)
** AX_COMPUTE_STANDARD_RELATIVE_PATHS
* Autopackage project
** Apbuild / Apgcc
** Guide to Making Relocatable Applications (BinReloc 2.0)
* Gnulib relocation macro(s)
* The nixpkgs project uses a few techniques for working around relocation issues, but the main one appears to be a "wrapper generator" script to create wrappers that set env vars.
* For .NET software using the Mono framework, see http://www.mono-project.com/Guidelines:Application_Deployment#Relocation.
* Producing relocatable packages with the GNU build system
* Tablet Python #1 - Relocatable Software
* Relocatable Wrinkles: Things to Consider
* relocatable packages
* Making relocatable packages with JHBuild - this discusses search/replace hacks, and talks specifically about how nix does it with their /nix/store/...<hash>... paths.
* Using ORIGIN for a dynamic runtime library search path
Required software

= OpenEmbedded's Software Requirements =
This page is the reference of what software is needed. But OEandYourDistro is likely much faster in getting you that software actually installed. A script for Ubuntu is provided.
To use the OE build system the following software is required on your system:
* Python (2.6.x or 2.7.x for latest development version of bitbake)
** Important: Python 3 is not supported. If you are using Python 3 you will need to ensure Python 2 is installed and that /usr/bin/env python invokes python2
** Note that you may also need certain development files for Python e.g. for bitbake's setup.py to work. Depending on the distribution you use you may want to look for a package called "python-dev", "python-devel", or similar.
* Python-ply PLY is an implementation of lex and yacc for
Python
* python-progressbar This library provides a text mode progressbar for python.
* GNU Patch (Version 2.5.9 or later, see ftp://alpha.gnu.org/gnu/diffutils/ . It is a "testing release" and is not mirrored on the GNU mirrors.)
* GNU m4
* GNU make (Version 3.80 or later for hh.org kernels)
* perl (needs newer than 5.0, how much newer? probably at least 5.6.2)
* diffstat
* bitbake
== Tools to download source files ==
* wget 
* curl 
* ftp
* cvs
* subversion
* git
* mercurial (for some recipes)
== Tools to verify integrity of the downloaded sources ==
* md5sum
* sha256sum
== Tools to unpack sources ==
* tar
* bzip2
* gzip
* unzip
== Tools to build the various *-doc packages==
* Jade or OpenJade
** I don't know which of these is preferred
* Docbook DTDs and DSSSL stylesheets
* sgmltools, called "sgmltools-lite" too
* docbook-utils
** docbook-utils download is hard to find; look in ftp://sources.redhat.com/pub/docbook-tools/new-trials/SOURCES
* Texinfo
* texi2html (Perl script that converts Texinfo to HTML)
== Other packages ==
* GNU sed 4.x
* Bison
* bc (binary calculator), if you want to build a Zaurus 2.4 or any of the collie kernels
* glibc headers (libc6-dev in Debian, glibc-devel in RPM based (in PLD also glibc-static is needed))
* pcre headers (Perl 5 Compatible Regular Expression Library, required for e.g. konqueror-embedded)
* SDL headers to build qemu-native (apt-get install libsdl1.2-dev under Ubuntu/Debian)
* mktemp (required by quilt and used in some package patches)
* help2man - Create simple man pages from --help output
* gawk - Text Processing Tool
* chrpath - change the rpath or runpath in binaries 
There is an ongoing effort to accurately document the required software within the OpenEmbedded and ultimately, this will be reflected in the ASSUME_PROVIDED variable.
Category:User
Revert Policy

Reverting someone elses work can be a great source of friction in OE. As such, these need to be handled carefully, preferable on technical grounds rather than personal ones. Some cases are clear, e.g. if the orignal patch author requests a revert then this should generally be accepted.
Now that OE uses layers, the situation is relatively clear since each layer has clear and documented maintainership and it is up to the layer maintainership to make decisions on whether code should be reverted. 
In cases where there is any doubt, the OE TSC has final decision and authority.
Category:Policy
Category:Quality Assurance
Ronetix-PM9263

Ronetix PM9263 device 
Hardware features:
 	
* CPU: AT91SAM9263, 240 MHz ARM926EJ-S
* 64MB DRAM, 32-bit
* 4MB NOR Flash, 16-bit (bootable, see note)
* 256 MB NAND Flash (see note)
* 4 MB Atmel Serial DataFlash (bootable, see note)
* 4 MB Video Memory on a separate external bus
* SPI EEPROM (optional)
* 10/100 MBits Ethernet
* Serial number chip DS2401
* SODIMM200 module (67x40mm)
Ronetix PM9263 is maintained by Marco Cavallini (mckoan) and KOAN team.
Category:machine
SDK/Toolchain/Application Developer Toolkit

Along with recipes for building a compiler for internal its own use, OpenEmbedded has recipes to create a full cross-compiler environment for the host. First, you need to have a working OpenEmbedded environment (see Getting_started). Note that throughout this article we will use the example of working on the ARM architecture. While particular file names may differ in your case, the general process should be similar. To build the cross-compiler, build the meta-toolchain recipe,
<nowiki>
$ bitbake meta-toolchain
</nowiki>
This will produce a tarball in a subdirectory of deploy/sdk. This tarball includes compiler executables, libraries, and core headers, as well as a small environment script, all under the prefix of usr/local/angstrom. To install this tarball, simply untar into /,
<nowiki>
$ sudo tar -C / -pxvjf $SDK_ROOT/sdk- 
</nowiki>
To cross-compile a package for your target platform, simply source the provided environment-setup script and compile as usual,
<nowiki>
$ source /usr/local/angstrom/arm/environment-setup
$ make
</nowiki>
Note that the meta-toolchain environment does not include any of the libraries included in your target image.
= Installing libraries and headers =
Along with a compiler, the meta-toolchain also comes with an installation of opkg with which one can install libraries into your cross-compilation environment. To install packages for use in cross-compiling use the opkg-target executable (not opkg; does anyone know what the latter is for?) There are a few For instance, to install the development headers for the boost library (boost-dev),
<nowiki>
$ sudo -i
# source /usr/local/angstrom/arm/environment-setup
# opkg-target update
# opkg-target install boost-dev
</nowiki>
This will fetch a package list from the Angstrom repository then fetch and install the boost package.
= Cross-compiling the kernel =
Because of the self-contained nature of the kernel, one must proceed slightly differently than with cross-compiling user-mode software. Namely, one must not use the environment-setup script provided with meta-toolchain. This script modifies environment required by the host compiler used to compile tools used during the build process, resulting in difficult to trace errors.
Instead, one simply must pass the target architecture and the cross-compiler executable name prefix to Kbuild,
<nowiki>
$ cd linux-2.6
$ export ARCH=arm
$ export CROSS_COMPILE=/usr/local/angstrom/arm/bin/
$ make menuconfig
$ make 
</nowiki>
The kernel Makefile also contains useful rules for packing the kernel image and modules into a tarball, for easy installation on the target,
<nowiki>
$ make 
</nowiki>
= Other Resources =
The OpenMoko wiki has a very useful page describing toolchain installation and usage.
Sources mirror

What is the OE sources mirror network?
Openembedded uses a large number of upstream sources for compilation. Quite naturally, given the sheer number, at any point in time, one can usually expect at least a few of them to be either temporarily or permanently unavailable. This leads to avoidable user frustration and lost time. The solution is for the Openembedded project to provide a mirror of all the sources used in the recipes as a fallback of last resort. This is done in the OE sources mirror network which has two components.
* sources.openembedded.org: the main mirror is currently hosted on melo. It aims to have a complete copy of free-to-publish sources used by the current org.oe.dev branch (the stable branch may be added later)
* mirrors.openembedded.org: a swarm of possibly incomplete source mirrors provided by the community and load-balanced via DNS round robin. They act as a first line of defense and lower bandwidth for the main mirror.
Fetching from these mirrors is transparent to the user and enabled by default in the dev branch.
How can I become a member in the mirrors.openembedded.org network?
tbd. right now, ask Laibsch in IRC if you want to help
Category:FAQ
Standards For Significant Factors For pregnancy

youtube.comIt isn't uncommon to own abdominal cramps during early pregnancy. Many women become frightened and fear that they're going to be using a miscarriage. This is normally not the explanation for abdominal cramps during early pregnancy. The embryo is embedding itself inside the lining with the uterus. This is what allows you to feel cramps just like those felt once you?re your period. The cramps takes several days and you will suffer how you did when using a period with a normal basis. Please do 't be fearful of those cramps as they are a standard part in the pregnancy.Pregnancy Without Pounds Reviews avoid permanent fat gain really weight reduction plan work, stop flabby belly syndrome,forget about stretch-marks and cellulite, prevent painful abdominal splitting,this ebook you'll have easy pregnancy miracle of life, labour and delivery your kid and get a fat loss and weight-loss.Pregnancy is among the most beautiful portion of women?s life as it completes her. A woman looks more beautiful during this period. It is surely an occasion being celebrated so that as always said dress will be the main attention grabbing section of every occasion thus this event may also be best exemplified with beautiful trendy maternity clothes. Dress is the representation of how a happy woman has been being pregnant and just how much it matters to her. Women who tend to be than thirty five yrs . old and have abandoned conceiving should also never give up hope. It is often a misconceived notion that elderly women cannot become pregnant. You can surely give birth to some healthy baby if you desire to have one. It is pretty disheartening when your tries to have a baby fail each time. Check out for holistic books which will make suggestions concerning how to conceive and provides birth with a healthy baby. You may also want to browse the internet on tricks to become pregnant as well as reviews of ladies who've had a fantastic experience along with the options they adopt for conceiving.Women, that are suffering from chills, fever, spotting as well as abdominal cramps during early pregnancy maybe being affected by other more harmful conditions, when a fertilized egg attaches beyond women?s uterus then this condition is called Ectopic Pregnancy. The egg usually will attach itself on the fallopian tube. Normally this problem is caught inside initial few weeks and treated right away. If for reasons uknown it doesn't rise above the crowd and treated maybe it's really dangerous because the fallopian tube may result in rupture. The signs and symptoms of an ectopic pregnancy include spotting, abdominal pain and tenderness. These signs are followed by back pain, shoulder pain, dizziness or faintness. If you suspect an ectopic pregnancy please contact your physician immediately.
Storage Selection

== Volatile (RAM) ==
In a nutshell: get as much as possible! :-)
As a rule of thumb, many users suggest (Number of cores) * 2GB. In general, more available RAM will always help caching and therefore increase your build speed.
== Non-Volatile ==
=== SSD ===
While SSDs can help improve the general perceived responsiveness and application startup time for desktop systems, they should not be considered very important for working on OE builds. During a build as little as possible is really synced to storage so optimal caching effects can be archieved. If you are on a budget, better get more RAM and "just" a HDD.
=== HDD ===
Most builds require a couple of 10GB, so HDDs are the primary storage technology for OE-based projects. Most users should be fine with a standard drive and 50-100GB of free space, although working on multiple projects, automated or world builds can significantly increase the storage footprint.
=== Filesystems ===
Any general purpose filesystem fulfilling the following requirements should be fine:
* Proper case sensitivity
* Support for partition sizes in the 10-100GB range
an OE build does not utilize any special features of the underlying filesystem, so it is only needed to provided a reliable storage backend.
Building on those filesystems is known to be faulty/impossible:
* HFS(plus)
* Any FAT variant
TS-7500

==Overview ==
The TS-7500 is based on a Cavium CNS2132 (aka Star Semi STR8132) which contains a Faraday FA-526 core and as a ARMv4 it has NO thumb or thumb interworking support. Most major linux distributions have decided to make ARMv4T (not ARMv4) the minimum supported architecture for their packages so OE is the best way to roll your own. see the Debian discussion. That is why you need to use openembedded.
==Basic Setup==
See here for the image and instructions for oe 
Main Wiki 
==Kernel==
If you need to build your own kernel 
See https://github.com/embeddedarm/linux-3.4-ts75xx/network
==Cflags==
These flags let you build code with almost any gcc-arm toolkit. 
-march=armv4 -mno-thumb-interwork -marm -mfloat-abi=soft
TSCCharter

The Technical Steering Council (TSC) is a committee within OpenEmbedded
(OE) appointed by the board with its members voted by election of the eV
members.
The TSC is ultimately answerable to the members of the OE eV through the
OE board!
The TSC has 5 positions which will be filled by 5 people elected by the
OE eV members using the eV voting processes.
The serving term of a TSC member is 1 year, they may be re-elected to
serve more than one term. Each position on the TSC is elected seperately.
No member is required to serve out his full term, the board would prefer
that if a member of the TSC feels that he is not in a position to best
serve the TSC that he can step down and trigger an election for his
position.
Decisions by the TSC are made where necessary by majority vote. Once a
decision is made by the technical steering committee, the decision
should be respected as a democratic decision.
The board will leave the internal running of TSC
meetings/roles/communication/task allocation to the current committee to
decide, but we would wish that the TSCs actions were transparent to the
members.
The rights and responsibilities of the TSC within the project:
# To lead the technical development of OpenEmbedded forward.
# To generally promote good development practice in OpenEmbedded.
# To assist the board anticipating future developments in world outside OpenEmbedded, that could affect the project technically, and bring these to the members notice.
# To govern access to all technical aspects of OpenEmbedded, this includes official git trees, openembedded-devel mailing list, bug trackers, QA systems, and others as the TSC sees fit.
# To make decisions in the technical implementation of OpenEmbedded where the membership is unable to obtain a consensus within itself.
# To guide the technical aspects of cooporation with outside entities, whether upstreaming or collaborating.
# To inform the OpenEmbedded board if there is an area not covered in the charter the TSC feel should be and the board can make a decision on updating the charter.
TSCDecisions

== TSC Decisions ==
= 2010/11/03 =
* The TSC supports the idea of regular patchwork days and proposes these should be on a regular timeslot around a Friday/Weekend/Monday on a monthly basis. Stefan Schmidt has kindly volunteered to coordinate these and has the support of the TSC. Mickey takes the action to communicate this to members via email.
* The TSC feels bitbake 1.8 should be an option for the upcoming OE December stable release as switching to 1.10 before the release is too soon. After the release OE.master should switch to 1.10. For reference, standalone python binaries from Yocto can be used (https://lists.yoctoproject.org/pipermail/yocto/2010-November/000176.html) on systems which don't have a recent python version.
* The TSC considered the issue of staggered election of its members. It felt that with members serving a one year term, staggering this could lead to a lot of "paperwork" without any real net benefit. If the OE members wish the TSC to do this, they are happy to do so though, they would just like to see member representation of this.
* For the fetch/unpack issues, moving the unpack code into bitbake and calling into the fetchers to run the unpack command is looking like the preferred option. Using the opportunity to clean up the fetcher code is desirable with a "fetch2" implementation in bitbake being acceptable. The TSC supports the idea in principle subject to final review of the patches.
* FILESPATH - This doesn't scale well with layers and the TSC supports the idea of reducing the number of directories listed. The exact solution still needs to be determined.
Testing:TestBuilder

= TestBuilder =
Here is script collections I using for doing OpenEmbedded test-builds.
It is on OE tree now (contrib/testing/testbuilder). You can view it online here: http://cgit.openembedded.org/cgit.cgi/openembedded/tree/contrib/testing/testbuilder
== How to setup and use ==
I assume below that you wish to install TestBuilder into `~/testbuilder` directory.
1. Copy the files from OE `contrib/testing/testbuilder` directory to any place you wish to use (e.g. `~/testbuilder`) and go to that directory.
2. Run the `setup-testbuilder` script with an OE branch and BitBake branch you wish to use. E.g.:
 ./setup-testbuilder "testing-next" "1.12"
It will clone the OE and BitBake trees and prepare the file `build/conf/local.conf` for you. You can review `local.conf` afterward and add some settings there.
3. Create `testbuilder.conf` according to your needs. You can use `testbuilder.conf.sample` as reference.
4. Create your build configs in `testbuilder.d` directory. You can use provided sample config files as reference.
5. Run `./testbuilder` and wait for the build results. Check the `logs` subdir for log files (`tail logs/B.*` is useful)
You can run a single configured build (e.g. "testing").
 ./testbuilder -B ./testbuilder.d/testing.conf
Or you can use TestBuilder to build a specific distro/machine/image just like bitbake (e.g. angstrom-2008.1/qemuarm/console-image).
 ./testbuilder -D angstrom-2008.1 -M qemuarm console-image
If you wish to only setup an environment and run BitBake by hand you can use the option `-S`.
 ./testbuilder -D angstrom-2008.1 -M qemuarm -S
Look ./testbuilder -h for full list of possible options.
Testing with QEMU

QEMU is great for testing images and apps. There is no need to flash or install images back and forth on real hardware. Here are a few things that may help you testing OE stuff with QEMU. The qemu machines are available with the qemu prefix, currently qemumips, qemuarm, qemuppc, qemux86 and qemux86-64 are available.
You can boot images within QEMU using the runqemu command. It can boot disk images and also NFS images. NFS support uses the unfs user mode server and does not require root access. Sudo access is required for network device setup but there is a script that can create the tap/tun device in advance removing the need for root privledges.
The qemu targets support automatic testing of images so that they are booted after image creation. Please see local.conf.sample for details on how to enable this.
= Useful keyboard shortcuts =
* Ctrl+Alt+1: guest OS
* Ctrl+Alt+2: qemu monitor (supports tab-completion, hint: sendkey)
* Ctrl+Alt+3: serial console
* Ctrl+Alt+4: parallel console (?)
= Other links =
* official documentation
* some more info in the Angstrom wiki
Category:Machine
Category:FAQ
Category:User
The Most Overlooked Solution For Act Of Aggression Hack

An Act of Aggressiveness Maphack, is a hack created to allow you see the entire game map, resources, structures, as well as units. This is a software application that works on your COMPUTER, and also communicates with the Act of Aggressiveness game customer, changing code in order to allow functions that typically typically aren't feasible within the game.Envision you're a general managing an armed forces operation. You utilize satellites, radar, and troop reports to assess exactly what your opponent is doing, and also where they are. In mediaeval times, your only information on adversary army activities would come from dust in the air, or the records of your precursors. Due to this, maybe tough to know where your all your adversaries were any any offered time.With this Act of Hostility cheat, that's a distant memory. You could see precisely where your foes base and units are, what buildings they are occupying, whether they have established a covert base, or are intending a sneak assault. With this information you could definitely damage them, having units in the right place to stop an attack, or striking at that station they really did not think you found out about. With the cheat you can be the MVP of your group every suit, boosting your win proportion greatly.When you initially start utilizing this cheat, it'll take a bit to obtain used to it. Checking exactly what your foe is doing is extremely valuable, yet it takes added time to browse their base, meanings you aren't taking any activities throughout that time. If you excel at macro, you'll be able to keep building and also creating units while checking your opponents without throwing away at any time.An additional means you can utilize the maphack is to track what kind of build your opponent is using. You can easily counter this with anti-air units as well as structures if it's a heavy air develop. You'll have an opportunity to construct your own units or prepare some static defense if it's a rush build. As well as of course, if they're playing the long game, you can try as well as punish them with some early aggressiveness when they the very least anticipate it.Inspect out the video clip if you're interested in obtaining a Maphack for Age of Hostility. It shows the cheat at work, so you can see it performs in truth work. The cheat is updated for the most up to date variation of the game, and also is undetected by the client, suggesting you will certainly not have your account disabled using it!Here is more info about act of aggression beta steam review the web page.