[EOSIOCPP] Clarify the Situation around eosio.wasmsdk

[ghost]

Problem

Multiple users reported problems to get a simple contract compiled. (see the references to this issue)

Possible Cause

@larryk85 within #5015 (comment):

The new workflow moving forward is to use eosio.wasmsdk. This has the new compiler (toolchain), eosiolib and standard libs.

@wanderingbort within #5106 (comment)

We are no longer maintaining the eosio.system contracts or the eosiolib from this repository. We port over eosiolib changes to maintain parity while it is in deprecation but the official repository is : https://github.com/EOSIO/eosio.wasmsdk/

Once the base feature is added and released there, then the contracts repo can be upgraded to take advantage of it: https://github.com/EOSIO/eosio.contracts/

Solution

• Provide a workaround: see [REGRESSION] [FIX] eosiocpp library problems #5133
• Document the current status and the future plans: https://github.com/EOSIO/eos/releases/tag/v1.2.0
• Update Changelog (done, see https://github.com/EOSIO/eos/releases/tag/v1.2.0)
• Update Documentation on developer.eos.io
  • New Installation
  • New Workflow

Suggestion

Such changes should not be done with without an RFC-Issue (Request for Comments from all interested parties, usually an [RFC] issue within the repo is enough). Sometimes the "annoying" folks has a point that you core-devs don't see.

More info within #5133

Sidenote

eosio.wasmsdk should possibly become eosio.sdk

[ghost]

@taokayan , could you please add this to the 1.3 Milestone?

[halsaphi]

Please refer to latest eosio.cdt, code and documentation:
https://github.com/EOSIO
https://developers.eos.io/
If problem persists with latest version please raise new issue.