| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
|
|
The function allocated a fresh buffer upon every call but callers didn't
care to free the returned value.
To solve this in a most simple way, make the function non-reentrant,
returning a pointer to a local, statically allocated buffer which is
being overwritten upon each consecutive call.
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
function, problem reported by Oliver
|
|
|
|
|
|
Signed-off-by: Waldemar Brodkorb <wbx@uclibc-ng.org>
|
|
|
|
|
|
|
|
|
|
After the addition of bare metal toolchains the menu system allowed
to create non-valid configurations. I reworked it so we can also
add other operating system support if we wish.
So first you choose your operating system, then your architecture
and endianess, after that your embedded system, emulator or
generic device and then you choose your task you want to run.
Tasks may be toolchain, a new appliance/application or some preconfigured
sets of packages and configurations as kodi, mpd, firefox and more.
The tasks are limited to a plausible choice of hardware and software.
Deduplicate CPU configuration.
You don't wanna compile Kodi for a H8/300 microcontroller ;)
|
|
|
|
The new prereq check is completely implemented in
POSIX shell in scripts/prereq.sh.
It combines the old features from Makefile, scan-tools.sh,
scan-pkgs.sh, reloc.sh and some wrappers for tools.
The big benefit is to have all portability stuff in one place.
Furthermore we can compile GNU make and bash on the fly, for
systems lacking the required tools.
All changes on the host are detected on the fly, no make
prereq required anymore.
The build process is separated in following three phases:
1. small wrapper Makefile is used for BSD make or GNU make
2. prereq.sh is called, doing all checking, calling Makefile.adk
3. old logic in Makefile.adk or mk/build.mk is used
Tested successfully on Linux, MacOS X, Cygwin, FreeBSD, OpenBSD
and NetBSD.
An old depmaker bug was fixed, only optional host tools are compiled.
For example, even when a host provides xz, a local xz was compiled
in the past, because other packages had a build dependency on it.
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
|
|
package
|
|
Please use PKG_NEEDS for marking of packages needing C++ compiler.
Remove the old bitrotted uClibc++ package and support for some
packages.
|
|
There are a lot of packages which needs special features either
toolchain or hardware features. Add a new symbol which will be
used to disable packages, when a toolchain for example does
not provide this feature.
At the moment following features are required to set for a
package: threads rt c++.
There will follow: mmu iconv.
This will help to better support targets without MMU or
threading support.
|
|
|
|
|
|
|
|
As mentioned by Phil, a lot of disk space is needed nowadays
to build OpenADK. Switch to non debug builds as default to
save 2 GB for each default build.
|
|
generated
|
|
- Sync with Kernel upstream Kconfig
- use new feature visible
- add a patch for select on choices
https://lkml.org/lkml/2011/2/17/379
- rename ADK_LINUX -> ADK_TARGET_ARCH
- remove package collection feature
- add appliance feature to define a appliance
more complete
|
|
This helps to find any regressions made in uClibc-ng.
|
|
to avoid namespace collisions in some packages, rename TOPDIR.
Sorry you need to make cleandir && make prereq && make
|
|
|
|
After Joerg asked me about the difference between
ADK_TARGET_ARCH and ADK_TARGET_CPU_ARCH I recognized many duplication
of variables for this information.
These patch fixes this up. Use make cleandir && make menuconfig && make
|
|
|
|
|
|
|
|
|
|
|
|
There is no need to use trstate for userland packages, because an ipkg
or txz is always build anyway. This make it more clear for the user.
A while ago a user asked me, what does it mean to use M for a package
and why it is not documented. Anyway, I think it make no sense at all.
|
|
|
|
|
|
|
|
|
|
|
|
|
