1. Hello

If you want me to reproduce something, please send me an *Xcode project*, not the link to a website that will require me to spend hours reading specific documentation about something I never heard of before, setting things up, following procedures and going through a lot of hassle just for reproducing a Xcode project such as the one that I could get from you in much less time.

Also, when you attach build logs, please provide a link to the full log, in debug mode (Shift + Build), instead of just pasting a few lines for which I have little context.

Thank you for your understanding.

Hello

Yes, I noticed your message. The problem you discovered doesn’t look like an easy one. I need to be able to secure periods of uninterrupted time to be able to study it efficiently. This is not easy for me at the moment. I promise to spend some time on it this week, but I can’t announce the date at which this task will be completed, unfortunately.

I suppose that this add-on isn’t essential for your project, is it ?

:: @Pierre-Marie Baty added on 14 May ’24 · 23:31

*edit* well, there are days like this. Just as I finished writing the previous message the cause of the problem struck me like the obvious. I read the log again and it turns out that your add on adds a bunch of compiler flags to the Xcode project, but when doing so it includes the whole lot in double quotes, which makes the compiler think that those separate flags are in fact one single element, which it interprets as a file name, obviously nonexistent. Hence the error message.

The proper way to fix this would be to instruct your plugin to not add those extra quotes when it adds compiler flags to the Xcode project file. The fact that it works on Mac suggests that Xcode dequotes them automatically, but it’s not a very safe thing to do because it creates the opposite problem : it becomes impossible to pass the compiler a definition flag whose value would be a string, for example.

I could, however, align the builder with this Xcode behavior and strip quotes from all flags but I’m wary that it could cause problems elsewhere. Do you have the possibility to tell your plugin to not add these problematic quotes in the first place ?