linux/meta-java.git/recipes-core/classpath, branch rocko

classpath-native: fix build dependencies

2017-03-03T10:15:46+00:00

Add missing dependencies in order to build according to latest changes done in poky where all dependencies must be installed relative to recipe WORKDIR. Signed-off-by: Adrian Calianu Signed-off-by: Maxin B. John

classpath: fix the license

2016-02-05T16:17:58+00:00

There is no 'Classpath' license, set it as the same with classpath-native. Signed-off-by: Jackie Huang Signed-off-by: Maxin B. John

classpath: fix invalid options

2016-01-04T11:22:35+00:00

After updated to version 0.99, the following options became invalid: * --with-ecj: use JAVAC env variable instead * --with-fastjar: change to --with-jar * --with-vm: uae JAVA env variable instead * --disable-qt4-peer: invalid even in 0.93, just drop it. Signed-off-by: Jackie Huang Signed-off-by: Otavio Salvador

Missing inheritance and dependencies in some java packages

2016-01-04T11:21:06+00:00

icedtea7-native, openjdk-7, and jamvm-native requires pkg-config to configure without running into an error similar to 7554: syntax error near unexpected token `NSS,' 7554: `PKG_CHECK_MODULES(NSS, nss, NSS_FOUND=yes, NSS_FOUND=no)' classpath-native and jamvm-native both needs to depend on java-initial-native Signed-off-by: Amy Fong Signed-off-by: Jackie Huang

Revert "meta-java: rely on well known bootstrap-path"

2016-01-04T11:21:06+00:00

This reverts commit 04d5d0bf414c05ca59618d77f17ff9898aa1c566. Detail reason is in the following commit. Signed-off-by: Jackie Huang

meta-java: rely on well known bootstrap-path

2015-12-08T15:43:35+00:00

Instead of potential circular depending virtual/javac-native (even this recipe provides such a useable java-native), rely on well known path via cacao-native to build up to icedtea7-native in reliable manner. virtual/javac-native should be used by parts not belonging to the bootstrap phase. Signed-off-by: Jens Rehsack Signed-off-by: Maxin B. John

Avoid parse time errors due to dependency on x11, for distros without x11

2015-10-29T11:02:28+00:00

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 Signed-off-by: Jens Rehsack Acked-by: Richard Leitner Signed-off-by: Otavio Salvador

Revert "Don't depend on a hardcoded compiler"

2015-08-26T21:31:20+00:00

This reverts commit 15ed9662e26ed4ac8d843fb9d2335a49a9c03088. The change has break external builds causing build failures. The change here needs to be revisited to avoid the breakages and than re-applied. Signed-off-by: Otavio Salvador

Avoid parse time errors due to dependency on x11, for distros without x11

2015-08-18T21:54:17+00:00

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 * classpath * jamvm * openjdk-6-release * openjdk-7-release That makes BitBake skip those recipes during the cache generation (they'd still be parsed, but ignored). Signed-off-by: Mario Domenech Goulart Signed-off-by: Otavio Salvador

Don't depend on a hardcoded compiler

2015-08-18T21:54:17+00:00

The recipes below depended on a hardcoded native compile (ecj-initial-native). Since we may use another native compiler to build them, we set the dependency in virtual/javac-native instead. * cacao * classpath-native * jamvm Signed-off-by: Mario Domenech Goulart Signed-off-by: Otavio Salvador