Home › Forums › OpenEars › [resolved] Install Problems

This topic has 2 voices, contains 10 replies, and was last updated by  Halle 58 days ago.

Viewing 11 posts - 1 through 11 (of 11 total)
Author Posts
Author Posts
February 11, 2012 at 7:10 am #8583

gotok

Hi,
I am trying to install OpenEars and have run into a problem which I hope you can help with.
The problem occurs at step 3 of “Configuring Your App for OpenEars”. The file, libOpenEarsLibrary.a, shows up as red and if I try to “Show in Finder”, it seems to be missing. I tried installing twice and had the same problem each time.
If I continue on, the only other problems is that “Compile for Thumb” in step 6 is not found.
When I tried to build and run, I got several ARC errors and a Lex Error. I turned off ARC, and the ARC errors went away, but the Lex error is still there.
I would appreciate any advice you can give me.

thanks…

  • This reply was modified 95 days ago by  Halle.
February 11, 2012 at 11:51 am #8584

Halle

Hi gotok,

There is no install step that requires doing anything with libOpenEarsLibrary.a, which will always appear in red. I would just re-read it again — you also shouldn’t have any ARC errors if you’re installing it according to the instructions. Recent testing has shown me that you don’t actually have to check “compile for thumb”. You’ll have to show me what the lex error is but I suspect it will also go away if you re-read the instructions and follow them precisely.
February 11, 2012 at 10:53 pm #8585

gotok

Thanks for your quick reply. My mistake was that at the very first step, I was dragging the [OpenEars] directory to the Project Navigator window in xCode rather than using Finder. Anyway I think my app is configured correctly now. However, I still get ARC errors on these lines:

[audioSessionManager release];
[pocketsphinxController release];
[fliteController release];
[languageModelGenerator release];

The first three lines has the error: ARC forbids explicit message send of ‘release’
The last line has the error: ‘release’ is unavailable not available in automatic reference
counting mode.
If I turn off ARC, then my app will build and run with no errors. I also noticed that ARC is turned off in the sample app (OpenEarsSampleProject). So, what do I need to change in order to use ARC in my app?

thanks for your help
February 11, 2012 at 11:23 pm #8586

Halle

Why did you add the release statements to your app if it uses ARC?
February 12, 2012 at 12:25 am #8587

gotok

Well, probably because I’m pretty new at this. I just did a cut and paste of the test code from the instructions. Since I deleted those test lines, my app compiles just fine with ARC turned on. Sorry for the beginner questions.

February 12, 2012 at 2:50 am #8588

Halle

OK, not a problem. Glad it’s working for you now.
February 12, 2012 at 6:03 am #8589

gotok

I’m having the problem where I can compile, but changes to OpenEarsConfig.h are not being recognized, and OpenEars doesn’t seem to be running. I enable logging, but get no logs. Can you clarify a couple of points for me?
1. I set up [OpenEars] in /Users/username/Documents/OpenEars as per the example in the instructions. The sample project works fine. My confusion is when I drag this [OpenEars] folder to my project directory, is the whole folder moving, or am I making a copy of it and end up with a copy where I unzipped it and another copy in my project directory? After I drag the folder, what does [OpenEars] in the instructions refer to?
2. Should my project and the OpenEars sample project be pointing to the same OpenEarsConfig.h file or separate copies of them.
Sorry to keep asking questions, but I’ve tried every combination and still can’t get it going.
thank..
February 12, 2012 at 11:21 am #8590

Halle

1. Either way. [OpenEars] in the instructions always refers to the OpenEars in the root of your app directory, whichever app you are working with.
2. In 100% of cases so far, OpenEarsConfig.h wasn’t being recognized because the developer didn’t add it to their project using the settings shown under “Conventions used in these instructions:” on the page http://www.politepix.com/openears/configuring. If it is copied into your app structure instead of just being referenced from the OpenEars static library structure, the library will not be able to see it or use it, so changes won’t apply. This goes for all the other items that get added into your app from the OpenEars docs.
February 13, 2012 at 5:00 pm #8593

Halle

(A couple of posts were lost here since they occurred in the middle of a server move, sorry gotok, but glad to hear that the advice in the previous post fixed your issue.)
March 21, 2012 at 3:18 am #8865

gotok

Hi Halle,
I’ll close out this thread by reporting that my app just made it into the App Store.

I don’t know if you keep track, but I would be interested in seeing the list of OpenEars based apps in the App Store.

Anyway, thanks for making OpenEars available, and for providing strong support for the developers using it.

  • This reply was modified 58 days ago by  Halle. Reason: fixed link html
March 21, 2012 at 11:39 am #8872

Halle

Congratulations gotok!

Good idea, I just made a new thread at the top of the forum for sharing your shipping app URLs and info. Feel free to post about it there as well.
Viewing 11 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic.