abi generation failure on Windows (outside of wsl) - always

[dj8yfo]

Steps to reproduce: cargo build --features near-sdk/__abi-generate on any contract

More details: near/cargo-near#188

Problematic target is x86_64-pc-windows-msvc

[Jemiiah]

@dj8yfo i would love to work on this issue may I ?

[onlydustapp]

Hey @Jemiiah!
Thanks for showing interest.
We've created an application for you to contribute to near-sdk-rs.
Go check it out on OnlyDust!

[frol]

@Jemiiah How is your Rust experience? Please, try to reproduce the issue first and if you have an idea of where to look at, apply it via OnlyDust website.

[Bosun-Josh121]

I am applying to this issue via OnlyDust platform.

My background and how it can be leveraged

Software engineering background with contributions to similar projects in past odhacks

How I plan on tackling this issue

I would use the provided info from the guide and make necessary adjustments & implementations

[frol]

@Josh-121 Do you have Windows machine to reproduce the issue? Do you have understanding of the DLL / shared symbols topic to address the problem we have here?

P.S. First thing we should try is to enable unit-testing feature: cargo build --features near-sdk/__abi-generate,unit-testing, see #1168 (comment) for context. If that will fix it, we would need to make sure we enable mocked blockchain functions (storage_read, ...) together with near-sdk/__abi-generate feature.

[Bosun-Josh121]

@Josh-121 Do you have Windows machine to reproduce the issue? Do you have understanding of the DLL / shared symbols topic to address the problem we have here?

P.S. First thing we should try is to enable unit-testing feature: cargo build --features near-sdk/__abi-generate,unit-testing, see #1168 (comment) for context. If that will fix it, we would need to make sure we enable mocked blockchain functions (storage_read, ...) together with near-sdk/__abi-generate feature.

Yes I do. I'll be working on that

[ScottyDavies]

I am applying to this issue via OnlyDust platform.

My background and how it can be leveraged
I am a backend developer who usually works with django and I have made use of OAuth on a number of projects. I want to contribute on this proJect

How I plan on tackling this issue
Understand the Issue: The cargo build --features near-sdk/__abi-generate command is failing on Windows, while other commands succeed, suggesting an issue with the ABI generation process.
Reproduce the Issue: Set up a fresh Windows environment and follow the steps to reproduce the problem.
Analyze Logs: Carefully examine the error logs to identify potential root causes.
Research Solutions: Look into the Rust RFC 1717 on DllImport and explore other known workarounds or fixes.
Implement and Test: Develop a solution, test it thoroughly, and document the implementation details.
Contribute the Solution: Submit a pull request to the near/cargo-near repository with the solution.

[onlydustapp]

Hi @ScottyDavies!
Maintainers during the ODHack #6.0 will be tracking applications via OnlyDust.
Therefore, in order for you to have a chance at being assigned to this issue, please apply directly here, or else your application may not be considered.

[lauchaves]

hey @frol is this the right way to reproduce it?

Im using windows btw

if so, looks good to me 🤔

[dj8yfo]

@lauchaves the issue 😭 occurred with x86_64-pc-windows-msvc rust target in Command shell and PowerShell.

It looks like it's ok with x86_64-pc-windows-gnu rust target in MinGW environment. Please confirm the latter, if you feel like doing so

[lauchaves]

I am applying to this issue via OnlyDust platform.

My background and how it can be leveraged

Hi again! Lau here 👋. I've been contributing these days! I'd like to give this one a try!

How I plan on tackling this issue

Earlier I tried to reproduce it on my end, but it seems to work on x86_64-pc-windows-gnu which is my current setup so...

• I'll set up the x86_64-pc-windows-msvc for cmd and PowerShell (I'll install that target as the default for powershell).
• I'd reproduce the issue.
• I'll give Frol's approach a try, which is to enable the unit-testing feature with: cargo build --features near-sdk/__abi-generate, unit-testing, hoping it works. If not, I'll keep investigating and def read about DLL/shared symbols!

[Bosun-Josh121]

@Josh-121 Do you have Windows machine to reproduce the issue? Do you have understanding of the DLL / shared symbols topic to address the problem we have here?

P.S. First thing we should try is to enable unit-testing feature: cargo build --features near-sdk/__abi-generate,unit-testing, see #1168 (comment) for context. If that will fix it, we would need to make sure we enable mocked blockchain functions (storage_read, ...) together with near-sdk/__abi-generate feature.

I now have it setup as well on my windows & know about dll/shared symbols as previously mentioned. Still awaiting ur response so far

[frol]

@Josh-121 Please, go ahead.

@lauchaves I want to maximize chances of everyone to participate in contributions to NEAR stack, but I will find more issues to work on later today