LOGIC: version invalid on built plugins in Plugin Manager

[tomekslesicki]

Just to add to this: the plist included in the .component file seems to have the proper version number (as set in HISE) but Logic doesn’t seem to care.

It’s on unviersal binaries, if it matters, but then I’m not sure if anybody would want to export non-M1 native at this point anyway ;-)

[DanH]

@tomekslesicki It's on non-universal binaries too

[DanH]

@Christoph-Hart did you manage to take a look at this this week?

[tomekslesicki]

@Christoph-Hart it would be great to have this fixed!

[tomekslesicki]

Ok, I have some more intel. I updated XCode to 13.4 and macOS to 12.4 and things are both better and worse. The worse first: when I build the plugin, I get this:

❌  clang: error: unable to execute command: Abort trap: 6



❌  clang: error: linker command failed due to signal (use -v to see invocation)

I can't build the latest develop version of HISE either but I'm just using my backup copy from April 24th.

Now the good part: if I open the autogenerated Jucer file and build it for Native Architecture Of Build Machine, it builds fine AND the plugin version is displayed correctly in auval at last!

...but I guess the Native Architecture Of Build Machine is M1 only and won't work on Intel macs, right? Because my mac is M1 so that would kind of make sense?

@Christoph-Hart @d-healey

[d.healey]

@tomekslesicki Looks very similar to this error I was getting (on my Intel Mac Mini). My solution was to roll back to an earlier version of Xcode.

LLVM Error building on OSX

I'm getting an error I've never come across before on MacOS. It occurs during the linking and I see that all my system memory is being eaten up by the linkin...

Forum (forum.hise.audio)

[Casey Kolb]

Running into this issue as well. Starting to get complaints from Logic users because it has to rescan the plugin every time due to the version being “invalid”

[DanH]

@Casey-Kolb All I could find online so far: https://forum.juce.com/t/au-plugin-version-in-logic-pro-x/46992/4

Would be great to get this fixed :)

[DanH]

@DanH the commit from 30th November 2021 works fine fyi - I just happened to have that still on my machine

[tomekslesicki]

Ok, I have a little breakthrough:

The last XCode that can build plugins or HISE at the moment is 13.2.1

When the AU is built from HISE, the AU version is not written properly and auval can't process it.

When the AU is built from the autogenerated projucer file, everything is fine.

@Christoph-Hart ?

[Christoph Hart]

@tomekslesicki Great news, we're getting close (I can't find anything in the source code so I think it might have something to do with the build tools).

What happens if you run the batch file (Builds/batchCompileOSX) manually? Does the AU version work then or do you need to go into Xcode for compilation? It might be the case that the command line build tools (xcodebuild) is using a different Xcode version, otherwise there shouldn't be too much difference.

You can check this with a terminal command:

Which version of Xcode does xcodebuild use?

I have installed both Xcode 3.2 and Xcode 4.0.2 on the same machine, which uses Hudson for automated CI (continuous integration) builds. When I say that both were installed, what I mean by that is ...

Stack Overflow (stackoverflow.com)

Is it the same version than you're using manually?

[Christoph Hart]

Or are you using a different Projucer binary than the one shipped with HISE?

[tomekslesicki]

@Christoph-Hart I'm using a different Projucer to compile, the one that came with HISE can't be run and I remember there's a way to hack that but I just downloaded a copy from JUCE back in December I guess. Here's what I'm using:

I only have XCode 13.2.1 installed, I remove all other copies not to get confused ;-)

[d.healey]

@tomekslesicki

I remember there's a way to hack that

It's just a permission issue. You have to run this command: terminal command "xattr -cr" + path to projucer

But I have the same AU version problem with the same version of Xcode and Projucer from the HISE repo.

[ulrik]

@d-healey I have the same problem as well.

[Christoph Hart]

OK, just to summarize:

• Xcode versions do not matter
• if you open the Autogenerated file in the Projucer shipped with HISE, it doesn't work.
• if you open the Autogenerated file with a Projucer built from JUCE directly, it works.

Does it also work with the Projucer 6.1.3 from the JUCE repo? Using a 6.1.4 Projucer with a 6.1.3 JUCE codebase might lead to other issues.

[tomekslesicki]

@Christoph-Hart

• I wouldn't say XCode doesn't matter - nothing will build on versions newer than 13.2.1 ;-)
• it works with the Projucer that comes with HISE, I just tested so I'm not going to test the other Projucer build to save some time
• it doesn't work when building from HISE - I need to manually open the autogenerated projucer project and build from that to get the version embedded

[DanH]

@tomekslesicki @Christoph-Hart using the projucer that come with HISE (6.1.3) doesn't work for me. I can't find the one from the JUCE repo - can anyone link me?

[ustk]

@DanH https://github.com/juce-framework/JUCE/tree/master/extras/Projucer/Builds

[DanH]

@ustk at the risk of sounding rather silly, I can't see a way to download the project in order to build it natively