Error when integrating RapidEars

Home Forums OpenEars plugins Error when integrating RapidEars

Viewing 10 posts - 1 through 10 (of 10 total)

  • Author
    Posts
  • #1019379
    Sat
    Participant

    Hi,

    I get errors when integrating RapidEars with OpenEars sample app.

    <versions and conditions>
    – OpenEars(1.52)
    – RapidEars(1.64) demo version
    – Using the sample app of OpenEars. The sample app works fine.
    – Followed the tutorial and added the codes for RapidEars.

    <error message>
    Apple Match-O Linker Warning
    Directory not found for option ‘F”/Users…


    ld: warning: directory not found for option ‘-F”/Users/satoshi/Downloads/OpenEarsDistribution/OpenEarsSampleApp/../Framework”‘
    Undefined symbols for architecture i386:
    “_closeAudioDevice”, referenced from:
    -[ContinuousModel(RapidEars) realtimeListeningLoopWithLanguageModelAtPath:dictionaryAtPath:acousticModelAtPath:] in RapidEarsDemo(ContinuousModel+RapidEars.o)
    “_openAudioDevice”, referenced from:
    -[ContinuousModel(RapidEars) realtimeListeningLoopWithLanguageModelAtPath:dictionaryAtPath:acousticModelAtPath:] in RapidEarsDemo(ContinuousModel+RapidEars.o)
    “_readBufferContents”, referenced from:
    -[ContinuousModel(RapidEars) realtimeListeningLoopWithLanguageModelAtPath:dictionaryAtPath:acousticModelAtPath:] in RapidEarsDemo(ContinuousModel+RapidEars.o)
    -[ContinuousModel(RapidEars) realtimeListeningLoopWithLanguageModelAtPath:dictionaryAtPath:acousticModelAtPath:] in RapidEarsDemo(ContinuousModel+RapidEars.o)
    “_startRecording”, referenced from:
    -[ContinuousModel(RapidEars) realtimeListeningLoopWithLanguageModelAtPath:dictionaryAtPath:acousticModelAtPath:] in RapidEarsDemo(ContinuousModel+RapidEars.o)
    “_stopRecording”, referenced from:
    -[ContinuousModel(RapidEars) realtimeListeningLoopWithLanguageModelAtPath:dictionaryAtPath:acousticModelAtPath:] in RapidEarsDemo(ContinuousModel+RapidEars.o)
    ld: symbol(s) not found for architecture i386
    clang: error: linker command failed with exit code 1 (use -v to see invocation)

    I searched on the web and found that it is related to framework reference. But I can see Rapidears framework on the navigator bar and in “Build Phases > Link Binary with Libraries”.
    I am sorry if this is a basic thing.

    Thank You.

    #1019380
    Halle Winkler
    Politepix

    Welcome,

    This is probably going to be the framework search path in build settings being wrong. When you do the tutorial, at the part with instructions about how to initially add the framework folder, there is a description of the required settings on the add dialog in order to avoid getting these issues — would you mind trying the tutorial process again with a fresh app and take some extra time checking out that step?

    #1019381
    Halle Winkler
    Politepix

    Oh, also — although it’s of course possible to add RapidEars to the sample app, the tutorial doesn’t explain how to do that. It’s written on the assumption that you are creating a new app following the tutorial steps. I would not add RapidEars to the sample app but instead follow the tutorial with a new app. This is much better because you’ll know the app is set up correctly but also because it very quickly walks you through the major functions of the SDK so you have a sense of what is going on once you’re done.

    #1019382
    Sat
    Participant

    Hi Halle, thank you very much for the quick reply.

    I tried the tutorial process again with a fresh app, but ended up with the same result. (OpenEars works fine, again.)

    I carefully added frameworks with the options described in the tutorial.

    <selected options> (both for OpenEars and RapidEars)
    – “Create groups for any added folders” is selected
    – “Create folder references for any added folders” is NOT selected
    – “Copy items into destination group’s folder (if needed)”

    Actually, I have been already struggling with this error for days with another original app. Is there any sample app of RapidEars, maybe?

    #1019383
    Halle Winkler
    Politepix

    Have you taken a look at that Framework Search Paths setting in Build Settings and verified that it looks correct? This sounds like it could be the Xcode bug that is described in the tutorial. If it is a search path that seems wrong or has a lot of weird backslashes in it, replace it with a path ending with the same resource that isn’t so weird.

    #1019384
    Halle Winkler
    Politepix

    Sorry, I didn’t answer your question about the sample app. I’ve decided that it isn’t a good idea to have individual sample apps for all of the plugins since the tutorial usually works fine to get started quickly and having 4 (and soon 5) different sample apps to test and maintain for every OpenEars/plugin release, every Xcode release and every significant iOS or Objective-C change would create overhead that wouldn’t be sensible to take on, in addition to a new area of tech support from developers who want to integrate a second or third plugin into a different plugin’s sample app, which is common. That attention would really be better focused on the frameworks which is why the quickstart tutorial tool was made instead. But I’ll be happy to help you out until we have the tutorial working for you, since it is known to work.

    #1019389
    Sat
    Participant

    Following the advice, I checked the Framework Search Path setting.

    /$(inherited)
    /Users/satoshi/Desktop/testApps/test_20130111_1/Framework
    /Users/satoshi/Desktop/testApps/test_20130111_1
    All of them are non-recursive.

    OpenEars frameworks are under the second directory, and RapidEars is under the third one. I also tried deleting /$(inherited), but there is no effect.

    I understand what you wrote about sample apps. Thanks for the help.

    #1019396
    Halle Winkler
    Politepix

    OK, I just saw that you are using OpenEars 1.5.2, can you use 1.6.4 for everything? This could be happening because you are mixing a 64-bit version of RapidEars with a 32-bit version of OpenEars and they don’t have the same architectures available (meaning they don’t have the same objects available for each architecture). Be sure to start with a new app.

    #1019399
    Sat
    Participant

    I installed OpenEars 1.6.4, and it works now! Thank you very much!

    #1019400
    Halle Winkler
    Politepix

    Very glad to hear it — sorry I overlooked that detail which you shared right at the start.

Viewing 10 posts - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.