Login
Discover
Waves
Communities
Write
Login
Signup
alphabeta
@alphabeta
56
Followers
594
Following
32
Follow
Email digest
Resource Credits
Available
Used
Created
2016-07-17 14:52
RSS Feed
Subscribe
Comments
Blog
Posts
Comments
Communities
Wallet
alphabeta
crypto
9y
RE: Passive Income with Cryptos is the New Mining
Reward sent out:
$ 0.000
0
alphabeta
steemit
10y
RE: 64 Bit Window Binary compiled with VS2013 (Hardfork v0.15.0)
Thanks.
$ 0.000
0
alphabeta
steemit
10y
RE: 64 Bit Window Binary compiled with VS2013 (Hardfork v0.15.0)
Thanks @abit. Well, the problem was the commit adding fixed_string definition. I have pointed out the lines on Github flat.hpp line44, flat_fwd.hpp line20 and variant.hpp line 94. Those changes cause the
alphabeta
witness-category
10y
RE: Abit Witness Log 2016-10-22 ~ 2016-10-28
That mean the changed is not correct. I guess steemd can not be compiled with vs2013 from v0.14.3rc1 onward. :( Thanks for your help.
alphabeta
witness-category
10y
RE: Abit Witness Log 2016-10-22 ~ 2016-10-28
Thanks for the reply. It is too difficult to debug these errors for me, especially when I am not a c++ coder. I did manage to get rid of "fc::raw::unpack" error by removing the ... from
alphabeta
witness-category
10y
RE: Abit Witness Log 2016-10-22 ~ 2016-10-28
Hi @abit, Since you are reviewing codes. Can you look at these errors? When I am Compiling v0.14.3rc1 with VS2013. I encounter two ambiguous call to overload function errors: I believe the errors were
alphabeta
steemit
10y
RE: 64 bits Window binary compiled with VS 2013
I saw that yesterday and compiled a binary with it. I did not see any hashing power improvement but it found a block for me just half hour ago. I did not post on Github yet.
alphabeta
steemit
10y
RE: Modified Steem Source Code for VS2013 (Hardfork 0.14.2).
@arcange, Will re-post on Github later. Update: Here is the link:
alphabeta
steemit
10y
RE: Modified Steem Source Code for VS2013 (Hardfork 0.14.2).
Hey @abit, I am not familiar with Github. I did create a branch vs2013 with modification and push to Github. I did a pull request and then I closed it because I thought it will merge with my fork, not
alphabeta
steemit
10y
RE: Modified Steem Source Code for VS2013 (Hardfork 0.14.2).
Thank you very much. I downloaded Git Bash with GUI. Looks complicated. Will try it later.
alphabeta
steemit
10y
RE: 64 bits Window binary compiled with VS 2013
Ok. I will try that later.
alphabeta
steemit
10y
RE: 64 bits Window binary compiled with VS 2013
Update2: Thank you @abit. All the below code change compiled without error. FC_CAPTURE_AND_LOG( (_user_agent_string) ) add a line friend bool operator<(const address& a, const address& b); >to
alphabeta
steemit
10y
RE: Modified Steem Source Code for VS2013 (Hardfork 0.14.2).
Thanks @abit. I just created a Github account, I trying to figure out how to put the binary and source up there. Do I have to create a Branch in order post files? BTW, I am testing the cli_wallet code
alphabeta
steemit
10y
RE: Modified Steem Source Code for VS2013 (Hardfork 0.14.2).
You're welcome.
alphabeta
steemit
10y
RE: Modified Steem Source Code for VS2013 (Hardfork 0.14.2).
right click "secp256k1" scroll down to property and make the changes. Edit: Make sure you hit apply after the change.
alphabeta
steemit
10y
RE: 64 bits Window binary compiled with VS 2013
Hi @abit, I did a test with above code FC_CAPTURE_AND_LOG( (_user_agent_string) ), it compiled fine with VS2013. But after it fully syncs, it crashed, not sure why. I would like to ask you a different
alphabeta
steemit
10y
RE: 64 bits Window binary compiled with VS 2013
I will test it when I can.
alphabeta
steemit
10y
RE: 64 bits Window binary compiled with VS 2013
Thank you! Maybe I will post the source later today when I have the time. Save me the trouble posting all the code change on a post.
alphabeta
steemit
10y
RE: 64 bits Window binary compiled with VS 2013
I will post the list of code change here later. Because I do not have a Github or steem-chat account(did not sign up one).
alphabeta
steemit
10y
RE: 64 bits Window binary compiled with VS 2013
I followed @bitcube's guide and look @ the change that he made on his commit. There are few more codes change needed on the new source for it to work with VS2013.
Older →