Hello

From your build log, I guess that those missing header files might be created by the UNIX shell script for which you're getting a warning. Here:

%
cd "$CONFIGURATION_BUILD_DIR/$WRAPPER_NAME" || exit 1
if [ ! -d Versions ]; then
  # Not a versioned framework, so no need to do anything
  exit 0
fi
 
public_path="${PUBLIC_HEADERS_FOLDER_PATH#$CONTENTS_FOLDER_PATH/}"
if [ ! -f "$public_path" ]; then
  ln -fs "${PUBLIC_HEADERS_FOLDER_PATH#$WRAPPER_NAME/}" "$public_path"
fi
 
private_path="${PRIVATE_HEADERS_FOLDER_PATH#$CONTENTS_FOLDER_PATH/}"
if [ ! -f "$private_path" ]; then
  ln -fs "${PRIVATE_HEADERS_FOLDER_PATH#$WRAPPER_NAME/}" "$private_path"
fi
%

Basically the BoringSSL-GRPC pod expects to run on a POSIX-compatible machine (which Windows is not) and creates two forced symbolic links. There are a lot of shell variables involved here:

PRIVATE_HEADERS_FOLDER_PATH
PUBLIC_HEADERS_FOLDER_PATH
CONTENTS_FOLDER_PATH
WRAPPER_NAME
public_path
private_path

It's not straightforward to work this around, but it's doable.

Those variables should be defined in your Xcode project file. Use the "pbxprojparse.exe" utility supplied with the builder to extract them with their actual value for the right target and configuration. Once you know these variables, you can basically search/replace them in the above script with their contents, and you'll understand exactly where these symbolic links should be created and where they should point at. This will give you the possibility to create them by hand (using the "mklink" command in the Windows console), so that your project can build.

It'll be difficult for you to workaround this issue without being fluent enough with UNIX semantics because what is needed is to translate a UNIX shell script into a Windows equivalent.

In your situation, I advise you to prefer precompiled frameworks. Download the corresponding iOS framework releases for Firebase, Admob, Facebook and Singular and proceed to adding them to your build using the method described in the documentation. Do you need help for that ?

You can proceed either way. Either you remove just one pod from the Podfile, and you supply it by hand to the linker, or you disable the Podfile completely, and you must supply all of the pods. I recommend the latter case, as it's not more difficult to feed several precompiled frameworks to the builder than to have just one.

Either way I *DO NOT* advise that you attempt things without understanding what they do. You say that you hope to just copy/paste a list of compiler and linker flags. It won't work that way. There are countless differences between SDK versions, framework versions, Unity engine versions, and user projects themselves. Not counting that every now and then the suppliers of all those popular SDKs completely change their API or the layout of their SDKs.

The thread you gave the link to is quite outdated ; don't rely on it. Take the time to read through the documentation (the builder's, and your SDK suppliers'), proceed step by step, and everything will go fine. Post here if you need help, after you've made reasonable effort at it.

You can save yourself a lot of time by reading the Firebase, Admob, Facebook, and Singular documentation -- they necessarily tell somewhere how to build iOS projects using their SDK without CocoaPods (look for paragraphs that talk about "manual" setup in their docs). With some luck, you won't even need to go through the missing parts identification step : if you follow these suppliers' instructions and add the right frameworks for your project to the builder upstart, there are great chances that your project will compile successfully at the first try.

If it doesn't, and there are still "missing symbols", the global idea that you should follow is that even if you're trying to build your project without all the necessary stuff, the fact that it fails is a *good thing*, because the error message will tell you what's missing. Don't close the window, read the errors and understand them. Proceed methodically, identifying the missing "symbols" the linker tells you are missing (that's actually "functions" and "variables" that have been compiled to machine code) by looking up their name in a search engine, download the precompiled framework for iOS in which they are from their supplier's website, and try again. You don't need to understand what these functions and variables do, not at all -- all you need is to find out which framework they come from. Don't feel discouraged by the large number of missing "symbols" : each time you'll add a framework in which one of them is defined, you'll make dozens of them disappear from the error list at once. At some point you'll have no more errors and your project will build. When you reach this point, *save* the builder's configuration to preserve the precious compiler and linker flags that enabled you to build your project.

Once you'll get used to this method, I promise you'll never be tempted to use CocoaPods again. And this is not something specific to Windows : macOS users can perfectly do that too in Xcode - the build logs are just somewhat less readable.

Hello

Sorry for the delay. By reading your build log I see that Facebook not only adds frameworks, but also injects Swift source files in your project, which has the effect of making it a *mixed-language* Swift/Objective-C project. The bad news is that at the moment, only Xcode is able to build mixed-language projects ; I haven't had enough time to reverse-engineer how they do to reimplement that properly in the builder.

The workaround to this at the moment is to change your Facebook SDK version to the latest Facebook SDK that did not have Swift files in it. Until I find the time to finish implementing mixed-language support. Hopefully you won't lose a lot of features by using an older Facebook SDK.

Thank you for your appreciation.