Repository navigation
v1.3.3 Fails Compilation on Linux #110
Description
The following commands:
git clone -b master --single-branch https://github.com/compomics/ThermoRawFileParser --branch v1.3.3 /src
xbuild
Yield the following error
Writer/MetadataWriter.cs(421,51): error CS0012: The type 'Enum' is defined in an assembly that is not referenced. You must add a reference to assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'.
Writer/MgfSpectrumWriter.cs(204,52): error CS0012: The type 'Enum' is defined in an assembly that is not referenced. You must add a reference to assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'.
Writer/MzMlSpectrumWriter.cs(1915,97): error CS0012: The type 'Enum' is defined in an assembly that is not referenced. You must add a reference to assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'.
Writer/MzMlSpectrumWriter.cs(40,37): error CS0012: The type 'Enum' is defined in an assembly that is not referenced. You must add a reference to assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'.
Writer/MzMlSpectrumWriter.cs(44,37): error CS0012: The type 'Enum' is defined in an assembly that is not referenced. You must add a reference to assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'.
Writer/OntologyMapping.cs(14,43): error CS0012: The type 'Enum' is defined in an assembly that is not referenced. You must add a reference to assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'.
Writer/OntologyMapping.cs(85,43): error CS0012: The type 'Enum' is defined in an assembly that is not referenced. You must add a reference to assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'.
Writer/OntologyMapping.cs(156,43): error CS0012: The type 'Enum' is defined in an assembly that is not referenced. You must add a reference to assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'.
Writer/ParquetSpectrumWriter.cs(25,37): error CS0012: The type 'Enum' is defined in an assembly that is not referenced. You must add a reference to assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'.
Writer/ParquetSpectrumWriter.cs(28,37): error CS0012: The type 'Enum' is defined in an assembly that is not referenced. You must add a reference to assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'.
2 Warning(s)
10 Error(s)
v1.3.2 does not cause this issue.
Activity
nielshulstaert commentedon Apr 6, 2021
Thanks for reporting this, I'll have a look at it and get back to you.
nielshulstaert commentedon Apr 6, 2021
I have the same problem with an old mono version (4.6.2) from the Ubuntu repositories. It works with the latest mono version (6.12.0) from the official mono repository. I'll have a look to make it work again on older mono versions. Suggestions are welcome.
caetera commentedon Apr 6, 2021
Can it be because Mono 4.6.2 do not support NET Standard 2.0?
https://docs.microsoft.com/en-us/dotnet/standard/net-standard
nielshulstaert commentedon Apr 6, 2021
Yes indeed, there should be a version of the thermo libraries that don't use .net standard, I'll try to get it so it still works on older mono versions.
nielshulstaert commentedon Apr 21, 2021
Hi I don't have access to the new version of the thermo libraries without .net standard, but it should work for mono 5 and higher. If you can't upgrade mono, I can make branch that use the previous thermo libraries, let me know.
zslastman commentedon Jun 10, 2021
So I'm still getting this bug, and am using mono 6.12.0 (Installed with conda, though I get it if I use the mono .pkg installer on my mac laptop instead).
I also get issues with 1.3.2:
caetera commentedon Oct 21, 2022
I have stumbled upon this issue and have a suggestion. Can it be that the compilation problem can be solved by switching from
xbuildtomsbuild? See #138ypriverol commentedon Mar 22, 2025
@caetera should we link this issue to the new PR and close it, when the PR is ready #193
caetera commentedon Mar 24, 2025
Yes. There wasn't a lot of development in this issue.