[Mono-ue] Build Error

[Michael Hutchinson]

rc.exe is the MS resource compiler. It looks like it doesn't like some
of the arguments we're passing it via UBT. My guess is that it's the
string constants we're passing in via the Defines list (see
MonoRuntime/Source/ThirdParty/mono/EmbeddedMono.Build.cs), since C++
compilers (and related tools) tend to be pretty finicky about those.
Maybe some characters in your path are breaking the escaping or
something.

In the latter case, the missing overrides, it looks like you haven't
applied the engine patchset.

- m


On 10 March 2015 at 19:33, Ryan Burnham <nitro52 at iinet.net.au> wrote:
> Yeah I suspect the issue is with the CompileAction.CommandArguments. It
> build a large list of CompileActions. Each have the same
> CompileAction.CommandPath which looks like it’s the C++ compiler. I tried
> outputting the CommandArguments but each one has a huge list of arguments. I
> couldn’t find where it actually uses CompileAction to execute RC so I could
> stick some error handling around the failing one. I’m not sure how to debug
> the UnrealBuildTool without knowing what command line arguments it is using.
>
>
>
> I rolled back 2 commits and got a different build error, so I’m not sure if
> it started there. I was defiantly able to build before, I think it was
> preview 4
>
> Error      1              error CS0115:
> 'UnrealBuildTool.Plugin.Rules.MonoRuntime.PreBuildTarget(UnrealBuildTool.UEBuildTarget,
> System.Collections.Generic.List<UnrealBuildTool.FileItem>)': no suitable
> method found to override       e:\Source
> Control\UnrealEngine\Engine\Plugins\XamarinUE4\MonoRuntime\Source\MonoRuntime\MonoRuntime.Plugin.cs
> 378         38           UE4
>
>
>
> From: mono-ue-bounces at lists.ximian.com
> [mailto:mono-ue-bounces at lists.ximian.com] On Behalf Of Robert Vissers
> Sent: Tuesday, 10 March 2015 6:54 AM
> To: mono-ue at lists.ximian.com
> Subject: [Mono-ue] Build Error
>
>
>
> I have the same build error on 2 of my PC’s. I got it to work on one other
> for some reason. I have no idea what the difference is. All VS2013, even one
> without update 4 (failed).
>
>
>
> CompileAction.CommandPath output is quite useless, is there some way to
> trace what the actual arguments are at the moment of failure? It compiles
> the RC list before executing it, making it quite hard to guess. Especially
> when it is running in parallel.
>
>
> _______________________________________________
> Mono-ue mailing list
> Mono-ue at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-ue
>



-- 
~ https://mhut.ch