Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

YACoind. now compiles on MSVC++ 2005 and later #38

Closed
wants to merge 3 commits into from

Conversation

ya-old-c-coder
Copy link

No meaningful changes have been made to the gcc sources, though some of
the MSC changes may be of interest.

The yacoind.exe produced uses a steady ~271MB of memory and should work on all versions of Windows (XPSP2, Vista, 7, 8). The creation of the static multi-threaded libraries; Boost, OpenSSL and BerkeleyDB will follow as described in my previous code for yacoind 0.4.1b

Ron

No meaningful changes have been made to the gcc sources, though some of
the MSC changes may be of interest.
// Copyright (c) 2009-2012 Bitcoin Developers
// Distributed under the MIT/X11 software license, see the accompanying
// file COPYING or http://www.opensource.org/licenses/mit-license.php.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So you have to take the blue pill and the red pill together to stay in wonderland?

@ya-old-c-coder
Copy link
Author

Since I "defined" THE_BLUE_PILL in MSVC++ properties-=>Configuration Properties=>C/C++=>Preprocessor=>Preprocessor Definitions, I added the ability to turn on warnings selectively if one wanted by just adding a #define THE_RED_PILL before the header line #include "msvc_warnings.push.h". :)

Of course if you would like to be "entertained" by the warnings, one only has to not "define" THE_BLUE_PILL as above. This "pharmacy" also allows one to selectively "study" the, shall I say suspicious code by commenting out one type of warning or another and then noting the particular warnings.

In gcc, linux or Windows, it seems all one can do with the makefiles given is to remove the -w and try to redirect the output. Boost is so "warning-rich" that it pollutes the stream when one is studying the actual bitcoin or *coin sources!

Ron

ron winter added 2 commits April 5, 2014 11:41
I forgot this one file, that presumes a VS 2008 or later.  In 2005, MS
didn't have a "tmmintrin.h" file for SSSE3 instructions.

Ron
I kept the side affects of all the assertions in so release mode would
behave like debug mode.

Also changed the method by which YACoind exits in MS so it is a little
more "correct".

Ron
@ya-old-c-coder
Copy link
Author

Hello all

The latest changes,
ya-old-c-coder@2a3973c
address the issue of assertions in the code and the way YACoind exits under MSVC.

The original pull,
ya-old-c-coder@d9623a9
may not exit gracefully!

Ron

@yacoin
Copy link
Owner

yacoin commented Apr 8, 2014

Ron, thanks so much! I merged your changes to yacoin::MSVC++ so closing this request.

@yacoin yacoin closed this Apr 8, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants