Build fail - Semantics: "Reference to ‘Point’ is ambiguous"



  • I’m trying to install HISE onto my Macbook Pro OS 10.15.4 (Catalina.) I’ve been following David’s video (which is really helpful!), I’ve installed the newest versions of XCode, IPP, and placed the ASIO and VST folders into the tools/SDK folder.

    I opened HISE Standalone.jucer and changed to 64-bit only (I get an error message if i don’t do that), then do the "Save and open in IDE" thing. Then in XCode, I select Project > Build For > Running, and it starts to compile, but then stops, saying there is a “Semantic Issue," where a “Reference to ‘Point’ is ambiguous." In fact, I get a whole bunch of errors where “Point” is ambiguous. Here are some screencaps of the first three:
    https://realitone.net/realitone/uploads/pix/HISE_Install_Error1.png
    https://realitone.net/realitone/uploads/pix/HISE_Install_Error2.png
    https://realitone.net/realitone/uploads/pix/HISE_Install_Error3.png

    Any ideas what might be going on?



  • Hi Mike, which version of the source code are you building? The scriptnode branch tends to be the most up to date but it's often buggy as it's the development branch.

    I have a branch here that should work - https://github.com/davidhealey/HISE/tree/develop

    You should select build for profiling, build for running builds the debug version which isn't optimized... I thought it would be the other way around too 🙂



  • @Mike-Greene Hey Mike have you tried
    Project. Build For> Profiling

    ??

    Might not fix your problem but its the route to (eventually) get a non-debug version of HISE, also what version of XCode are you running?

    (Edit: - I really really should read Dave's posts...)



  • I tried again with David's download. Oddly, the Projucer app from that the tools folder wouldn't open, so I copied the Projucer app I already had into David's folder. (I suspect the one in David's folder is a Windows version?)

    I get the same “Reference to ‘Point’ is ambiguous" errors. I tried both the Plugin and Standalone versions, and both Running and Profiling. Same error.

    I'm using XCode 11.4 (11E146). In case it matters, the Intel IPP install was the newest one: 2020.0.166

    Regarding which version of the source code this is, I don't know where I would find that. If it's the .jucer files, there don't seem to be version numbers on them.

    One interesting thing (although I don't think this was what made the build fail) - In David's download, there is a hi_snex folder and an stk_wrapper folder which wasn't in the download I got a few days ago.

    One other thing - I moved the HISE folder to my Applications folder, rathe than keeping it in the Downloads folder. I can't imagine that matters, but in case it does, there you go.

    I suppose I could try using older versions, but I don't know how to do that.



  • I don't think the latest IPP will work and someone was saying recently that they couldn't find a download for the older version now.

    I also think that you have to use xcode10, but I could be wrong about that.

    When you downloaded the source code I linked to and opened Projucer I assume Projucer automatically opened the previous version you had (assuming you didn't delete it). Did you manually open the Projucer project from the new source code?

    Regarding which version of the source code this is, I don't know where I would find that

    Do you have the link you downloaded it from?

    In David's download, there is a hi_snex folder and an stk_wrapper folder which wasn't in the download I got a few days ago.

    I'm guessing you downloaded the old Release source which hasn't been updated for ages.



  • In that thread you linked, Azrul mentioned he was using Mac OS 10.11, which I think is El Capitan. That's why he couldn't use the newest IPP. It's a compatibility with an older OS situation.

    Last week, I was having the same issues when I was using Sierra and High Sierra (OS 10.12 and 10.13), and I needed to get not only an older version of IPP, but also older Xcode versions. The documentation for which versions you need is practically non-existent and sometimes even wrong, so after a few non-compatible combinations attempts, I gave up and bought another laptop with Catalina, since this way I can simply install the newest of everything on a totally clean computer and all should be compatible. (The laptop was $600 used, not brand new, so it's a worthwhile expense.)

    Regarding which versions of HISE I downloaded, my first attempt was using the folder I got when I went to the github link from the HISE Downloads page :
    https://github.com/christophhart/HISE/
    and clicked the green "Clone or download" button and then selected "Download Zip."

    The second attempt was the same thing, except I went to the page you linked:
    https://github.com/davidhealey/HISE/tree/develop
    and then I clicked the green "Clone or download" button and then selected "Download Zip."

    I'm pretty confident Projucer was opening new versions (not yesterday's versions) because I did a lot of project closing, plus I renamed the old folders, so that Projucer (and Xcode) wouldn't be able to find the old ones. I also got an Xcode error when I hadn't changed a setting to 64-bit, whcih suggests this was a new compile, not yesterday's. This is all new to me, though, so maybe I did something wrong there.



  • Renaming the folder should have removed that issue but if it was me I'd delete the other version. It's come up a few times where people have multiple copies that interfere with each other.



  • @Mike-Greene you will need to use XCode 10.



  • @Mike-Greene said in Build fail - Semantics: "Reference to ‘Point’ is ambiguous":

    I’m trying to install HISE onto my Macbook Pro OS 10.15.4 (Catalina.)

    If using Catalina, you need to use the latest projucer from the JUCE website.



  • Thanks guys. Projucer from the JUCE site should be easy, but I'm wondering how difficult it will be to install Xcode 10 if I already have Xcode 11. Maybe easy (or not?), but now I wonder if I should have started with Mojave instead of Catalina.

    My original reason for Catalina was that the Xcode installation was nice and easy through the App Store (Xcode in the App Store requires Catalina), but if I'm going to use Xcode 10.3, I should probably take a step back and make sure I really want Catalina rather than Mojave.

    This laptop is totally clean, with nothing on it except what I've done here, so switching is easy and painless. So since I'm in a position where I can use whichever OS would make things easiest, which would you recommend?



  • @Mike-Greene Mojave - every time -- in fact Windows 10 is easily the best install and run HISE scenario...



  • @Mike-Greene said in Build fail - Semantics: "Reference to ‘Point’ is ambiguous":

    now I wonder if I should have started with Mojave instead of Catalina.

    I'm using Catalina on an unsupported 2010 mac mini. Projucer from JUCE website and xcode 11.
    All is working well here.



  • Victory! Per Lindon's suggestion, I wiped the drive and installed Mojave, Xcode 10.3 and the newest IPP, then did all the steps, and I now have a Standalone version working.

    I'm getting an error with the Plugin version, though. Not a big deal, since the standalone version is all I care about right now, but still, if anyone knows what this is about, the error I'm getting is on this line:
    #include "pluginterfaces/vst2.x/aeffect.h"

    The error is 'pluginterfaces/vst2.x/aeffect.h' file not found.

    I'm thinking VST2 isn't even needed, and in fact, there are some comments above that line that seem to suggest that this is optional. However, I don't see where I would turn that off. My guess is in Projucer, but I don't see a tab for "Don't use VST2."



  • @dustbro said in Build fail - Semantics: "Reference to ‘Point’ is ambiguous":

    I'm using Catalina on an unsupported 2010 mac mini. Projucer from JUCE website and xcode 11.
    All is working well here.

    Your ninja skills are way beyond mine if you got a 2010 Mac Mini to let you install Catalina. 😉



  • @Mike-Greene I got that error building the plugin too. I'll make a quick video later today to explain the solution, if someone doesn't post it before me.



  • Actually I can do this without a video.

    cbf6f469-13e8-44e8-bbd4-d9250c7b8bc4-image.png

    Open the .jucer file for the plugin version in Projucer.

    Go through each of the modules in the menu at the left side.

    Look at the path entries for Xcode, Visual Studio 2017, and Linux Makefile.

    If any of those paths are red it means it's incorrect. You need to set those incorrect paths to ../../

    feb2f86a-a028-431f-a65b-185261b73f85-image.png

    Next, make sure that the VST (Legacy) SDK Folder path is set in the Exporters section. This should point to the HISE source code folder/tools/SDK/VST3 SDK - or wherever you've put the VST SDK.

    After you've done this just save the project, open in IDE, and rebuild.



  • Thanks David! That did the trick.

    One thing for any other newbies who may read this thread- when setting the path for the Xcode (MacOSX) >> VST (Legacy) SDK Folder, it was easier to click the "..." browser button, rather than typing the address (which I kept getting wrong.) That's what led me to see that file path needed to be written as:
    ../../tools/SDK/VST3 SDK
    rather than:
    HISE-master/tools/SDK/VST3 SDK

    Also, Xcode annoyingly keeps displaying yesterday's fail, without any indication it's starting a new process. When I ran it today, that's what it displayed, so at first, I thought I failed again. It had a time stamp at the top from yesterday, mind you, but still, it was confusing and I couldn't clear it. It took a minute or so before I could tell it was running (I thought it wasn't at first) and eventually gave me a Success indication. So all is well, but for other newbies, it's something to be aware of.

    Also a new thing I learned - In Projucer, it's when a path is red that we have an error. In David's video, he mentions checking the Modules, but they were all fine, so I wasn't sure what we were looking for that might indicate anything was bad. Now I know it's red paths that I'm looking for.

    I'm slowly gettin' it. 😉


Log in to reply
 

5
Online

647
Users

2.6k
Topics

21.4k
Posts