The root cause of this problem needs locating and a longterm fix
or mitigation (Dynamic Plugins?) is required as each new engine or
increase in code size retriggers this issue.
These both use platform-9 API, rather than platform-4 as the x86 and
MIPS toolchains were only added in platform-9.
Changed directory name for third party libraries to reflect the
platform system libraries compiled against.
The dsymutil-macosx is a OSX binary loaded via maloader and ld-mac,
which uses mmap() to do this. This currently fails, possibly as it
requires write permissions to dsymutil-macosx to achieve this.
Will need to investigate and avoid adding write permissions to other
to fix as this is highly insecure.
It may be possible to patch the ld-mac / maloader to fix or worst case,
change the dsymutil-macosx to be owned by buildbot user and set user
write permission.
This is as per a user request as tar.xz can not be decompressed
directly on iOS devices, so required an intermediate desktop device
to install these builds.
Other tar formats such as bz2 can be reportedly decompressed fine
using iFile etc.
Minor incorrect usage for staticlibpath passed to configure.
Removal of all parameters which are now uneeded as the SDK wrapper
script deals with this.
This should build successfully as Freetype2 is already present for both
toolchains. If this fails to build, it is likely due to missing
iconv libraries which will be added if necessary.
The Clean buildstep has started failing as the "rm" command runs
with no output, and due to the size of the builders directories. after
1200 secs of no output, the buildbot framework assumes that the command
has got stuck and kills the process and fails.
This is preventing nightlies from running correctly.
To prevent this, the verbose flag is added to the rm command to ensure
output and prevent the timeout.
This will add MIPS and x86 Android builds in addition to the current
ARM builds as separate builds. This will need a bit of work to build
the third party libraries for the new architectures before this can
be implemented on the buildbot.
Due to the increase in the Buildbot VM disk space, we should now be
able to keep 14 days of snapshot history, but this will need periodic
checking to ensure it does not cause issues.
This needs to run just prior to the previous key expiration via a
cron script on the server. The keys are set for expiration in 365
days from generation i.e. 1 year.
As the buildbot VM has issues with low disk space currently, changing
to the LZMA based xz format instead of bz2 for most packages will help
with this.
This is intended for builders present to allow build compile
testing for specific compilers / configurations, rather than to generate
nightly packages for user/development testing.
This is important as the buildbot box has a limited amount of disk space
and each new builder which packages uses a significant amount for
storage of these. Have set this on the existing builders of this type.
D G Turner