Thanks for sharing

You're welcome.

Thanks for sharing @alphabeta...

> To use @bitcube's external "secp256k1.dll". Open it's property and change Target Extension from ".lib" to ".dll", and Configuration type from "static" to "dynamic".

Which solution I need to edit for this? secp256k1 or steemd?

[IMAGE: https://ipfs.pics/ipfs/QmNWECbsABTpe1epqJa6d1mf1JXx7C87K5T59aa7GmeNyh]

right click "secp256k1" scroll down to property and make the changes.
Edit:
Make sure you hit apply after the change.

Great job! Upvoted, although I'm a bit late.

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 now. I will give you feedback when I am done.

I'm not sure what git client you're using. Assume you're on Windows and you have Git Bash, try these steps:
* On page https://github.com/steemit/steem , clone the repository to your account by clicking "fork"
* open Git Bash
* git config --global user.name="your_github_user_name"
* git config --global user.email="your_github_user_name@users.noreply.github.com"
* git clone https://github.com/your_github_user_name/steem.git "your_new_path_to_the_project"
* cd "your_new_path_to_the_project"
* git checkout v0.14.2
* git branch "your_new_branch_name"
* git checkout "your_new_branch_name"
* git submodule update --init --recursive
* Copy your modified source code (tree) to "your_new_path_to_the_project"
* git diff
(use above step to check whether the new code is correct)
* git commit -a -m "your_commit_comment"
* git push origin "your_new_branch_name"

Then you'll see the new branch on github, you can create a pull request from your branch so the changes can be merged to upstream repository.

If you have modified code in libraries/fc, it would be a bit more complicated, you may need to
* On page https://github.com/steemit/fc , clone the repository to your account by clicking "fork"
* Edit the file ".gitmodules" in "your_new_path_to_the_project", replace the URL in the file to your FC library
* Remove the "fc" directory from "libraries" folder
* cd "your_new_path_to_the_project"
* git submodule --init --recursive
* cd libraries/fc
* git branch "your_new_fc_branch_name"
* git checkout "your_new_fc_branch_name"
* Copy the modified FC code here
* git commit -a -m "your_commit_comment_to_fc_lib"
* git push origin "your_new_fc_branch_name"
* cd "your_new_path_to_the_project"
* git commit -a -m "your_commit_comment_to_the_main_project"
* git push origin "your_new_branch_name"

With these changes your repository would be able to compile independently, but it can't be merged directly to upstream repository (due to the change on .gitmodule file).

//Update: to upload binaries, follow the instructions on https://github.com/your_github_user_name/steem/releases

Thank you very much. I downloaded Git Bash with GUI. Looks complicated. Will try it later.

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 the original develop branch. And also it appears that dan created vs2013 branch 23 days ago. I need more time figure this out.

Update:
I created another branch called win_steem and pull request(#496) it.
Please review it when you have a chance. Thanks for your help.

Hey @alphabeta, I've been a bit late to try download your .zip file and the link seems to be broken now.
Can you republish it? Thx

@arcange,
Will re-post on Github later.

Update:
Here is the link:
https://github.com/alphab3ta/steem/releases/tag/v0.14.2

Thanks a lot!