Ant build.xml does not exist! Build failed

itphoenix · April 19, 2011, 2:25pm

Ant was installed in yast2 but will not run since build.xml was never created. How can this be fixed?

I would like to run AudioTool.

martin_helm · April 19, 2011, 5:58pm

itphoenix wrote:

>
> Ant was installed in yast2 but will not run since build.xml was never
> created. How can this be fixed?
>
> I would like to run AudioTool.
>
build.xml is not a part of ant. ant is a build environment mainly used for
java software, similar to what is make for c/c++ development.
The build.xml is the equivalent of a Makefile which has to be provided by
the software package you want to build.

itphoenix · April 20, 2011, 12:22am

I see. The original problem is to get pocketsphinx to use krecord as the mixer by default. So whether doing that or running Java’s AudioTool, a compilation of the program is necessary. Is that correct?

There is a switch option that can be used at startup that supposedly selects the device to be used. But I have no idea how to specify the option part of the switch.

Thank you for your answer and any pointers here would be appreciated.

martin_helm · April 20, 2011, 1:06am

itphoenix wrote:

>
> I see. The original problem is to get pocketsphinx to use krecord as
> the mixer by default. So whether doing that or running Java’s
> AudioTool, a compilation of the program is necessary. Is that correct?
>
I do not know the program, I think it is better if you create a new thread
with an appropriate title which mentions the original problem and what you
want to do with pocketsphinx. This will help to get attention from the
multimedia guru’s, do it in the multimedia subforum.
They will probably not look into a thread where the title points to a
general programming problem.

tsu2 · April 21, 2011, 3:02am

Besides Martin’s suggestion to re-post in the Multimedia forum,

I might add that your assumption that re-compilation is required probably isn’t likely (yet).

As Martin described, Ant is simply a compilation tool, but to use it you’ll need source code that is known to be built using Ant (and would then automatically include the missing XML file).

So,

Since build.xml isn’t found, IMO it’s unlikely that Ant is the recommended tool to use. Often with the sourcecode compilation instructions are included, often in a file called INSTALL.
Configuring to use an app to use another app can be tricky without specific info. If you know how to read source or the source is well documented, you might be able to figure that out on your own but for a newbie is very unlikely.
Read the App Docs. Read the Man page if available. Find the Project on the Web and see what’s on the website. And, only after your personal investigation has turned up empty, ask in the openSUSE Multimedia forum or the app’s Project forum/mailing list. I can see you’ve at least found a little info about a “switch option” so you’re making progress. If a switch is available then bare syntax can usually be displayed by invoking the app name followed by hyphen-hyphen-help

eg

foobar --help

If a Man page is available then it can be invoked by

man foobar

HTH,
Tony

itphoenix · April 23, 2011, 4:34am

Thanks everybody. The instuctions provided by CMUSphinx are not newbie-friendly. I went further into Java code and was stymied. In any event, it has been found that the ALSA driver combined with pavucontrol is not going to work. I turned the input level up on the mic a little and the application perceived speech. Moreover, I still had to talk right into the mic for the app to detect my voice as before.

I am pursuing the oss driver which does not have a turn-key install yet for openSUSE but it is close. I may eventually have to purchase an up-to-date Creative card which could be used on W7 if it does not work here. The older Creative cards do not have “What you hear” for W7 so there is no recording from the system, only the mic or another input.

The nVidia video rpm worked good, but I expect much difficulty with sound here. I found Terminal Emulator useful as I can operate as super user. The oss driver will not go in properly otherwise, and any errors are easily copied to a txt file.

Again, I appreciate all the pointers.