If someone only has windows available, is it possible to develop a smart contract?
Yes, you have a couple of options, with WSL2 being the recommended approach:
Using Windows Subsystem for Linux (WSL2):
WSL2 is supported for smart contract development and is actively used by some KleverChain development team members
While our extension isn’t currently compatible with WSL2, development is fully possible through the Command Line Interface (CLI)
If there’s interest in a guide to develop SC using WSL2, let me know so i can prepare one
What about Direct Windows Development?
While it’s technically possible to write code in Windows, there are important limitations to consider:
Key features like compilation and automated testing require a Unix-like environment
You would need to handle compilation and testing on a different operating system
For the best development experience, we recommend using WSL2 or a Linux environment
For those who prefer not to use WSL2, you might want to consider:
Running a Linux virtual machine
Using Docker Desktop for Windows
Setting up a remote development environment
Feel free to ask if you need more specific details about any of these approaches!
I have now set up a Linux machine with Ubuntu Desktop.
VSCode installed
Klever Extension installed
Rust installed
cloned klever-sdk
and now
marco@MarcoUbuntu:~/klever$ /home/marco/klever-sdk/koperator account create
bash: /home/marco/klever-sdk/koperator: File or directory not found
Where do I get the koperator file now?
Update: Creating workspace solved this. But now the following message:
marco@MarcoUbuntu:~/klever-sdk$ /home/marco/klever-sdk/koperator account create
/home/marco/klever-sdk/koperator: error while loading shared libraries: libvmexeccapi.so: cannot open shared object file: No such file or directory
hey @Duka and @Nicollas I hope you are doing well so far!
Is there a time frame for when the update for the Mac will be released?
I don’t know about the others, but currently it is impossible (at least for me with Mac and Windows) to deploy one of the example contracts.
This is important for us to make sure our environment is running properly before we can create and test our own smart contracts.
We’re excited to announce the release of version 1.0.8 of our VSCode extension! Here’s what’s new and important in this update:
What’s New in v1.0.8:
Wallet generation location is now set to the SDK path (modifiable in the configuration).
“Missing lib” error has been fixed.
The faucet is now accessible only if the wallet address is defined in the extension settings.
Windows is no longer officially supported.
Update Instructions:
With these changes, we recommend starting with a clean setup. Here’s how:
Delete the SDK Folder: Go to your SDK location (typically ~/klever-sdk, unless you specified a different path in settings) and delete this folder.
Uninstall Previous Extension: Remove the old version of the Kleverchain IDE extension from VSCode.
Restart VSCode.
Delete Old Workspace Files: Remove any kleverchain.workspace.json files from previous projects.
Install v1.0.8: Add the new version of the Kleverchain IDE extension.
One more important step! When starting a new project, run the following command to ensure the correct Rustup version:
rustup override set nightly-2024-06-12
rustup target add wasm32-unknown-unknown
Finally, remember to update the wallet address in your extension settings when generating a new wallet. This will ensure the faucet functions properly.
If you have any questions or run into any issues, let us know—we’re here to help!
yes, unfortunately this also sets us back a little in our schedule!
we do have the option of switching to a different system, but this also requires the corresponding know-how!
I can only agree with Marco… windows must be made available as quickly as possible.
Not for us as a project and participant in the hackathon, but especially for new projects and users.
Especially because we (Klever) advertise with user-friendly conditions for everyone
It is Windows support that you guys want?
We already have an experimental version being validated by our team.
I can’t make promises yet (Windows has its own characteristics), but we’re listening to you! We know how important Windows is, and we’ll keep working to make this official again.
For now, I ask that you continue experimenting with and using Linux and macOS while we work to make Windows officially supported again as soon as possible.
I want to emphasize the purpose of this forum, which is to build solutions together.
Your feedback is extremely important to us, especially in this early extension phase.
Everyone’s experience now will help shape the future of this extension.
I’m excited to hear your thoughts on the extension workflow. We’re looking for constructive feedback to incorporate into the next version
Don’t hesitate to reach out to me if you encounter any issues. Every computer is unique, and our goal is to develop something reliable across all platforms.
MacOS Update:
Windows Compatibility Note:
For Windows users:
