Skip to content

Fix CMake build in test subdirectories #150

Fix CMake build in test subdirectories

Fix CMake build in test subdirectories #150

Triggered via pull request July 4, 2023 20:00
Status Success
Total duration 1h 37m 21s
Artifacts

amd64_linux_cmake_dotnet.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
cmake
Some target frameworks declared in the dependencies group of the nuspec and the lib/ref folder do not have exact matches in the other location. Consult the list of actions below:
cmake
- Add lib or ref assemblies for the net6.0 target framework
cmake: build/dotnet/Google.OrTools/ortools/linear_solver/Variable.cs#L13
'Variable' defines operator == or operator != but does not override Object.Equals(object o)
cmake: build/dotnet/Google.OrTools/ortools/linear_solver/Variable.cs#L13
'Variable' defines operator == or operator != but does not override Object.GetHashCode()
cmake: ortools/linear_solver/csharp/LinearConstraint.cs#L21
'LinearConstraint.ToString()' hides inherited member 'object.ToString()'. To make the current member override that implementation, add the override keyword. Otherwise add the new keyword.
cmake: ortools/linear_solver/csharp/LinearExpr.cs#L19
'LinearExpr' defines operator == or operator != but does not override Object.Equals(object o)
cmake: ortools/linear_solver/csharp/LinearExpr.cs#L19
'LinearExpr' defines operator == or operator != but does not override Object.GetHashCode()
cmake: ortools/sat/csharp/IntegerExpressions.cs#L107
'LinearExpr' defines operator == or operator != but does not override Object.Equals(object o)
cmake: ortools/sat/csharp/IntegerExpressions.cs#L107
'LinearExpr' defines operator == or operator != but does not override Object.GetHashCode()
cmake: build/dotnet/Google.OrTools/ortools/constraint_solver/RevPartialSequence.cs#L86
'RevPartialSequence.ToString()' hides inherited member 'object.ToString()'. To make the current member override that implementation, add the override keyword. Otherwise add the new keyword.
cmake
.NET Core 3.1 is no longer supported and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the .NET support policy.