microdee / microdee/mp.essentials

Build Errors

Open
#2 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
4
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Hi MD,
I get this warning a problem other people may come across:

> There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "VVVV.Nodes.Generic", "AMD64". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.

I guess this means you have to build x86 or x64. Or is this libaray 64bit only?

I also got the following error:

[FailingOutput.txt](https://github.com/microdee/mp.essentials/files/2131277/FailingOutput.txt)

In the code for "ValueTouchProcessorNode" the 'ftc' on line 115 shows a compile error:
> ) expected

Can't figure out what it is but it seems to be related to many other errors. If you'd like more info just drop me a msg.

yY

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the attached FailingOutput.txt and inspect ValueTouchProcessorNode around line 115, where the reported compile error occurs. Check the project and reference processor architectures to determine whether the MSIL and AMD64 mismatch contributes to the failures. Done means the project builds without the reported architecture warning or compile errors, with the supported target architecture documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.