Nebukam
commented
9 months ago Hey @AtomicTroop ! First off -- thank you for taking the time to log this issue!
(sidenote: you are indeed right regarding the sidenote for PublicIncludePaths, I'll remove it from the doc today)
The current main is indeed stable, at least on PC: I never had the chance to test on Apple hardware.
I'm waiting to finish the documentation write-up before locking the first tag in, as I keep on discovering a few minor issues/details here and there.
For the issue at hand, I'm a bit at a loss. I tried locally with a fresh project (both blueprint and C++) but I can't seem to reproduce the errors. I know the code is using some C++20 features which may not be your default (Unreal supports as low as C++17, but should come with C++20 as a default) on Mac?
The first error about FNonAbandonableTask is puzzling because it's as if UnrealHeaderTool is missing some forward declaration in the code (or not taking a class ). I'd like to try and rule out something with you:
If you go to the source of the plugin, and edit PCGExMT.h at line 204 add an explicit forward declaration like so:
...
}
}
class FPCGExNonAbandonableTask; // <- This line
class PCGEXTENDEDTOOLKIT_API FPCGExAsyncManager
{
friend class FPCGExNonAbandonableTask; // <- this is there already and used to be enough on PC
public:
~FPCGExAsyncManager();
...If this helps you get rid of the first error, the C++ environment/version you're using is somehow too strict.
If that seem to solve the issue, I'll do a cleanup pass based on your error log hoping that it solve the issues on the M1 but we're in for some nasty back'n forth; and even then there are some C++ template errors I'm not sure what the fix would be :/
AtomicTroop
Hi, I'm testing out this plugin in a new, freshly created Unreal 5.3.2 C++ project. I'm developing on an M1 Macbook Pro, so this is an arm64 editor build.
I've added the plugin as a git submodule and added the C# side ModuleRules additions to my project's Build.cs.
As a side note, the
PublicIncludePathsaddition in the installation instructions seems to be unnecessary in 5.3 as per the comment left on that field's API docs:When I try to build the plugin after these installation steps, I get a big bunch of compilation errors, I've attached the logs at the end of this issue description.
I'm not quite sure what's going on here, whether it's something wrong with my local configuration or an issue with Mac/arm64 support maybe, but I'd also like to rule out the option that the current state of the main branch is broken, considering there's no stable tag to pin the submodule at right now. Any thoughts or advice would be appreciated.
Compile logs
<projectroot>and<engineroot>are the absolute paths to my local project and installed engine, respectively