mirror of
https://github.com/f-droid/fdroidserver.git
synced 2025-11-04 14:30:30 +03:00
document new fdroid build behavior with .fdroid.* metadata
This commit is contained in:
parent
578218a8b0
commit
3b20153cd7
1 changed files with 23 additions and 3 deletions
|
|
@ -314,7 +314,7 @@ To build a single version of a single application, you could run the
|
||||||
following:
|
following:
|
||||||
|
|
||||||
@example
|
@example
|
||||||
./fdroid build org.fdroid.fdroid:16
|
fdroid build org.fdroid.fdroid:16
|
||||||
@end example
|
@end example
|
||||||
|
|
||||||
This attempts to build version code 16 (which is version 0.25) of the F-Droid
|
This attempts to build version code 16 (which is version 0.25) of the F-Droid
|
||||||
|
|
@ -336,7 +336,7 @@ tarball containing exactly the source that was used to generate the binary.
|
||||||
If you were intending to publish these files, you could then run:
|
If you were intending to publish these files, you could then run:
|
||||||
|
|
||||||
@example
|
@example
|
||||||
./fdroid publish
|
fdroid publish
|
||||||
@end example
|
@end example
|
||||||
|
|
||||||
The source tarball would move to the @code{repo} directory (which is the
|
The source tarball would move to the @code{repo} directory (which is the
|
||||||
|
|
@ -366,6 +366,26 @@ all such prebuilts are built either via the metadata or by a reputable third
|
||||||
party.
|
party.
|
||||||
|
|
||||||
|
|
||||||
|
@section Running "fdroid build" in your app's source
|
||||||
|
|
||||||
|
Another option for using @code{fdroid build} is to use a metadata file
|
||||||
|
that is included in the app's source itself, rather than in a
|
||||||
|
@code{metadata/} folder with lots of other apps. This metadata file
|
||||||
|
should be in the root of your source repo, and be called
|
||||||
|
@code{.fdroid.json}, @code{.fdroid.xml}, @code{.fdroid.yaml}, or
|
||||||
|
@code{.fdroid.txt}, depending on your preferred data format: JSON,
|
||||||
|
XML, YAML, or F-Droid's @code{.txt} format.
|
||||||
|
|
||||||
|
Once you have that setup, you can build the most recent version of
|
||||||
|
the app using the whole FDroid stack by running:
|
||||||
|
|
||||||
|
@example
|
||||||
|
fdroid build
|
||||||
|
@end example
|
||||||
|
|
||||||
|
If you want to build every single version, then specify @code{--all}.
|
||||||
|
|
||||||
|
|
||||||
@section Direct Installation
|
@section Direct Installation
|
||||||
|
|
||||||
You can also build and install directly to a connected device or emulator
|
You can also build and install directly to a connected device or emulator
|
||||||
|
|
@ -386,7 +406,7 @@ will take a URL and optionally some other parameters, and attempt to construct
|
||||||
as much information as possible by analysing the source code. Basic usage is:
|
as much information as possible by analysing the source code. Basic usage is:
|
||||||
|
|
||||||
@example
|
@example
|
||||||
./fdroid import --url=http://address.of.project
|
fdroid import --url=http://address.of.project
|
||||||
@end example
|
@end example
|
||||||
|
|
||||||
For this to work, the URL must point to a project format that the script
|
For this to work, the URL must point to a project format that the script
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue