summaryrefslogtreecommitdiffstats
path: root/recipes-core/jamvm/jamvm_git.bb
Commit message (Collapse)AuthorAgeFilesLines
* jamvm: Do not build for aarch64 targetsRicardo Ribalda Delgado2019-07-091-0/+1
| | | | | | | | | | | Avoids: | configure: error: aarch64-poky-linux-gnu not supported | NOTE: The following config.log files may provide further information. | NOTE: /workdir/build/tmp/work/aarch64-poky-linux/jamvm/2.0.0-devel+gitAUTOINC+6cef41d859-r0/build/config.log | ERROR: configure failed Signed-off-by: Ricardo Ribalda Delgado <ricardo@ribalda.com> Signed-off-by: Richard Leitner <richard.leitner@skidata.com>
* jamvm: avoid checking x11 distro feature for native buildMing Liu2018-01-091-4/+0
| | | | | | | | | x11 is not a mandatory distro feature for building jamvm-native, so avoid checking it for native build, or else it would lead parsing errors. Signed-off-by: Ming Liu <liu.ming50@gmail.com> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
* jamvm-git uprev to 2.0.0Amy Fong2016-01-041-2/+2
| | | | | Signed-off-by: Amy Fong <amy.fong@windriver.com> Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
* Avoid parse time errors due to dependency on x11, for distros without x11Jens Rehsack2015-10-291-0/+4
| | | | | | | | | | | | | | | | | | | | | BitBake raises some errors when processing recipes that depend on x11 for distros that don't have x11 in DISTRO_FEATURES. To work around that issue, REQUIRED_DISTRO_FEATURES = "x11" (from distro_features_check.bbclass) has been set for the following recipes: * cacao (_class-target) * classpath (_class-target) * jamvm (_class-target) * openjdk-7-release That makes BitBake skip those recipes during the cache generation (they'd still be parsed, but ignored). This patch improves the idea from Mario Domenech Goulart <mario@ossystems.com.br> Signed-off-by: Jens Rehsack <sno@netbsd.org> Acked-by: Richard Leitner <richard.leitner@skidata.com> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
* jamvm: update git url to sourceforge while berlios is goneHenning Heinold2014-04-161-1/+1
|
* jamvm: update git version to ebd11bde0a97b57f0d18938c6b65468d3c932719Henning Heinold2014-04-161-2/+1
| | | | * remove annotations.patch, because it was fixed upstream
* jamvm: update to git revision ac22c9948434e528ece451642b4ebde40953ee7eHenning Heinold2013-09-291-3/+3
| | | | * fix gnuclasspath annotations
* jamvm: update git versionHenning Heinold2012-10-181-2/+2
|
* jamvm: update git version to 2fdfc86c4c52c14668bcb87fec8cd8ba87e24fc3Henning Heinold2012-07-191-2/+2
|
* jamvm: work around min heap size greater than max errorJan Luebbe2012-05-251-1/+2
| | | | | | | | | | On system with large amounts of RAM (such as 96GB), the default initial heap size is larger than the max heap size specified in some build commands. Set min_heap to the max_heap value in those cases instead. Signed-off-by: Jan Luebbe <jlu@pengutronix.de> Signed-off-by: Henning Heinold <heinold@inf.fu-berlin.de>
* classpath-initial: fix installation of tools.zip fileOtavio Salvador2012-04-041-0/+2
| | | | | | | | | | This fixes an unpredicability of sysroot tools.zip version as classpath-initial and classpath-native were installing the tools.zip at same path. We also bump PR of affected recipes to force them to rebuild. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
* jamvm git: use proper PVKoen Kooi2011-12-011-1/+1
| | | | | Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Henning Heinold <heinold@inf.fu-berlin.de>
* meta-java: initial commitHenning Heinold2011-11-261-0/+15
* taken over mostly stuff from oe classic * cleaned up recipes * added license checksums * bump icedtea6-native to 1.8.11 * use jamvm from git as native