You are viewing a single comment's thread from:

RE: Introducing EOSFactory, an EOS smart-contract development and testing framework

in #eos • 7 years ago

awesome work!
is it possible for one to keep the c++ layer and replace the python one with a .net core built one?

7 years ago in #eos by
$0.00
    Reply 2
    Sort:  
  • Trending
    • [-]
     7 years ago 

    Thanks :)

    We intend to move the C++ layer (it's called teos) into a separate repository, with EOSFactory having it as a dependency. So yes, once we do that you could use teos as a foundation for other projects.

    Actually, we'd love to see it being used that way, as it was designed with this purpose in mind - that's why it's a static library, not an executable like cleos.

    However, there is one important thing we need to take into account: teos is dependent on EOSIO source code, which unfortunately is incompatible with Windows - you cannot build EOS with any C++ compiler that's available on Windows. We've tried it for a long time and it looks quite hopeless. The main obstacle is that EOS is heavily dependent on an integer type that's not supported by Windows.

    So I guess any .NET-based solution is out of reach, at least at this moment.

    $0.00
      Reply
      [-]
       6 years ago 

      thanks for the answer. I said .net core which runs on mac and linux ;-)

      $0.00
        Reply