Slightly better wording in the README. ant-prepare success prints.
This commit is contained in:
parent
cfcdfebe4e
commit
07b79c1e06
14
README.md
14
README.md
@ -94,12 +94,22 @@ When building F-Droid, the following error may occur:
|
|||||||
|
|
||||||
> Invalid file: extern/UniversalImageLoader/library/build.xml
|
> Invalid file: extern/UniversalImageLoader/library/build.xml
|
||||||
|
|
||||||
Check the output of the ./ant-prepare.sh command. This error is often accompanied by the following message:
|
Check the output of the ./ant-prepare.sh command. This error is often
|
||||||
|
accompanied by the following message:
|
||||||
|
|
||||||
> Error: The project either has no target set or the target is invalid.
|
> Error: The project either has no target set or the target is invalid.
|
||||||
> Please provide a --target to the 'android update' command.
|
> Please provide a --target to the 'android update' command.
|
||||||
|
|
||||||
The most likely cause of this is that your installed Android SDK is missing the target API specified by one of the dependencies. For example, at the time of writing this, UniversalImageLoader requires the "android-16" API (extern/UniversalImageLoader/library/project.properties), however the default install of the Android SDK will usually only install the latest version ("android-19" as of writing). NOTE: While it may be tempting to add "--target=android-19" to the ./ant-prepare.sh script, it is not the correct solution. Although it may work, it can also cause strange bugs when the upstream library uses features of the earlier SDK which have changed in later versions.
|
The most likely cause of this is that your installed Android SDK is missing
|
||||||
|
the target version specified by one of the dependencies. For example, at the
|
||||||
|
time of writing this, UniversalImageLoader uses the "android-16" target API,
|
||||||
|
however the default install of the Android SDK will usually only install the
|
||||||
|
latest version ("android-19" as of writing). So you will have to install
|
||||||
|
the "android-16" target via the SDK manager.
|
||||||
|
|
||||||
|
NOTE: While it may be tempting to add "--target=android-19" to the
|
||||||
|
ant-prepare.sh script, it is not the correct solution. Although it may work,
|
||||||
|
it can cause strange bugs at runtime.
|
||||||
|
|
||||||
|
|
||||||
License
|
License
|
||||||
|
@ -5,6 +5,10 @@ android update lib-project --path extern/AndroidPinning
|
|||||||
android update lib-project --path extern/MemorizingTrustManager
|
android update lib-project --path extern/MemorizingTrustManager
|
||||||
android update project --path . --name F-Droid
|
android update project --path . --name F-Droid
|
||||||
|
|
||||||
|
{ echo -e "\nSuccessfully updated the main project.\n"; } 2>/dev/null
|
||||||
|
|
||||||
# technically optional, needed for the tests
|
# technically optional, needed for the tests
|
||||||
cd test
|
cd test
|
||||||
android update test-project --path . --main ..
|
android update test-project --path . --main ..
|
||||||
|
|
||||||
|
{ echo -e "\nSuccessfully updated the test project.\n"; } 2>/dev/null
|
||||||
|
Loading…
x
Reference in New Issue
Block a user