本文介绍了使用bitcoinj从Maven的中央时坏的apk的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我只是试图从本地bitcoinj罐子切换到从Maven的中央拉一个版本,并面临着一个奇怪的问题。由此产生的apk设备兼容性标记坏了。

I just tried to switch from a local bitcoinj jar to a version pulled from maven central and face a strange problem. The resulting apk's device compatibility marking is broken.

本节展示我尝试改变:

this section shows the change I tried:

// compile "com.google:bitcoinj:0.11.1"
// the above looks like a really good idea, but unfortunately the apk resulting from this
// is broken in the way that it is marked as available only for x86_64 - which are 0 devices
// in google play at the moment - something strange gets pulled in there 

compile files('libs/bitcoinj-0.8.jar')

调查是什么多余的东西被拉到这里之前,我只是想在这里问,如果有人遇到同样的事情。奇怪的只有这似乎是一个jar依赖,我不希望这样的事情被拉到 - 不应该有本土code ..

before investigating what unwanted thing is pulled in here I just wanted to ask here if somebody faced the same thing. Strange only that this seems to be a jar dependency and I do not expect things like this to be pulled - there should be no native code ..

推荐答案

我挖一个深一点。 Bitcoinj拉在libscrypt。从bitcoinj POM:

I digged a bit deeper. Bitcoinj pulls in libscrypt. From the bitcoinj pom:

<dependency>
<groupId>com.lambdaworks</groupId>
<artifactId>scrypt</artifactId>
<version>1.3.3</version>
</dependency>

和libscrypt包含本地$ C $下x86_64的只有:

and libscrypt contains native code for x86_64 only:

$> unzip -l scrypt-1.4.0.jar | grep libsc
21708  2013-05-26 12:20   lib/x86_64/darwin/libscrypt.dylib
22140  2013-05-26 12:20   lib/x86_64/freebsd/libscrypt.so
21306  2013-05-26 12:20   lib/x86_64/linux/libscrypt.so

这似乎导致问题

这篇关于使用bitcoinj从Maven的中央时坏的apk的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-15 04:14