may be you can specify where the buildfile is located and then invoke desired action.
Eg: ant -file {BuildfileLocation/build.xml} -v
this one works in ubuntu This command will cre android update project -p "project full path"
You have invoked Ant with the verbose (-v) mode but the default buildfile build.xml
does not exist. Nor have you specified any other buildfile
for it to use.
I would say your Ant installation is fine.
Using ant debug after building build.xml file :
in your cmd your root should be your project at first then use the ant debug command e.g:
c:\testApp>ant debug
Please install at ubuntu openjdk-7-jdk
sudo apt-get install openjdk-7-jdk
on Windows try find find openjdk
If you couldn't find the build.xml file in your project then you have to build it to be able to debug it and get your .apk
you can use this command-line to build:
android update project -p "project full path"
where "Project full path" -- Give your full path of your project location
after this you will find the build.xml then you can debug it.
If I understand correctly, you assumed that -v
is the "print version" command. Check the documentation, that is not the case -- instead ant -v
is running ant build in verbose
mode. So ant is trying to perform your build, based on the build.xml
file, which is obviously not there.
To answer your question explicitly: there is probably nothing wrong with both the system nor ant installation.
There may be two situations.
Please see and confim the same.
In the case one you have to find where your build file is located and in the case 2, You will have to run command ant -f <your build file name>
.
Source: Stackoverflow.com