AIDL(1)
π NAME π
okok so aidl β literally the Java bindings generator of AIDL interfaces β¨ she takes your AIDL and manifests the Java for you, no cap.
πΈ SYNOPSIS πΈ
aidl OPTIONS INPUT [OUTPUT]
aidl --preprocess OUTPUT INPUT...
bestie pls note there are two whole moods here: the regular run, and the --preprocess era π«Ά
β¨ OPTIONS β¨
-I<DIR>β search path forimportstatements. every place you want her to go digging, list it π-d<FILE>β generate a dependency file. drop the path, get the deps π-aβ generate a dependency file right next to the output file, and the name is based on the input file. cute and automatic π-ninjaβ same dependency-file energy but in the formatninjaunderstands π₯·-p<FILE>β the file that--preprocesscreated, which you now want toimportπ-o<FOLDER>β base output folder for all the generated files π-bβ fail when trying to compile a parcelable. like, just refuse, on purpose πINPUTβ anaidlinterface file, queen πOUTPUTβ the generated interface files β¨
so the tea on where stuff actually lands, fr fr:
- if you skip
OUTPUTand you didn't use the-ooption, the input filename gets used, with the.aidlextension changed to a.javaextension. glow up π - if you do use the
-ooption, the generated files go in the base output folder, tucked under their package folder π
π₯ SEE ALSO π₯
iykyk, go read it π¦
π«Ά AUTHORS π«Ά
The Android Open Source Project.
and that's the whole page!! this little cutie lives in the General Commands Manual under the name AIDL(1) β slay, periodt πβ¨π
π¦ where this page comes from
- ubuntu stonking: aidl 1:14.0.0+r75-1 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms