Landis v8 compiling issue

[kai sheng]

Dear Landis developers

I hope this message finds you well.

I am currently setting up a sandbox environment to run LANDIS-II v8 and the necessary extensions (e.g., Extension-NECN-Succession). Most of the setup process has gone smoothly, but I have encountered an issue related to Landis.Library.Metadata-v2.

I have edited the .csproj files in the extension's src folder and the Tool-Console's src folder to ensure that the paths to Landis.Library.Metadata-v2.dll are correct. Despite this, I am still encountering the following error(in the screenshot, and how I edit the .csproj file)

I would greatly appreciate it if you could help me troubleshoot this issue. If there are any specific steps I might have missed or additional configurations I need to perform, please let me know.

Thank you for your time and assistance.

[Robert Scheller]

Kai,

I recommend removing all of the hint paths in the csproj file.  You want to make sure it's building from the latest downloaded dlls in the src/lib directory.  The risk is that it will be loading outdated dlls that were previously installed.

R

[kai sheng]

Hi Robert,

Thank you for your response! I didn’t quite understand your point. If I remove all the hint paths in the .csproj file, it will report errors when running dotnet build. My metadata.dll is from the LANDIS-II Support Library GitHub repository. Are you suggesting that the metadata.dll in this repository is outdated?

Also, I’d like to clarify: when you mention removing all hint paths in the .csproj file, are you referring to the .csproj file in the extensions' src directory, or the .csproj file in the Tool-Console directory?

Since I am confident that the hint paths in the .csproj files are correct, I wondered if the issue might be due to an outdated version of the metadata.dll.

Thank you!

Kai

[Robert Scheller]

Kai,

Yes, I'm referring to the csproj for each extension.  There should be no need to rebuild Tool-Console.

You want to build the extension from extensions located in src/lib.  Run the script located there somewhat frequently to download the latest versions of all dlls.  The dlls in the bin/debug/netstandard directory are from your last build and will not necessarily reflect the latest versions of dlls.  If you remove the hint path, it should default to the using those in the src/lib directory.   

Cheers,

R

[Klemet]

Hey Kai !

Me and other people have been trying to compile LANDIS-II v8 for Linux too, and have encountered similar problems with the libraries.

Sometimes, the libraries on the Support libraries repository (which the script inside src/lib is supposed to download) doesn't seem to be up to date, leading to compatibility issues.

In any case, we were able to develop a dockerfile that can successfully compile all of the current extensions available for LANDIS-II v8 - including NECN - and make them work. See the attached .zip folder. If you're not familliar with Docker, I should be able to answer your questions on how to use such an image.

Good luck !