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

[winrt support] Adding macro to help check and test what API of the Windows Runtime is being used. #3

Closed
wants to merge 2 commits into from

Conversation

stgates
Copy link
Contributor

@stgates stgates commented May 13, 2014

This change adds a macro BOOST_WINDOWS_RUNTIME that can be used by individual Boost libraries to determine which Windows APIs are available for use.

This is part of the work mentioned on the Boost dev mailing list to help get portions of Boost working in Windows store and phone.

http://boost.2283326.n4.nabble.com/winrt-support-Adding-support-for-Windows-8-store-phone-to-Boost-libraries-tc4661713.html

Originally I added this macro to Boost.Config but received feedback on the name and that it better belongs in Boost.Predef. For history here is the previous pull request from Boost.Config:
boostorg/config#13

stgates added 2 commits May 13, 2014 16:35
…ost libraries to determine which Windows APIs are available for use.

BOOST_WINDOWS_RUNTIME maps to the WINAPI_FAMILY macro when targeting WinRT.
@@ -1,6 +1,7 @@
/*
Copyright Rene Rivera 2008-2013
Copyright Franz Detro 2014
Copyright (c) Microsoft Corporation
Copy link
Member

Choose a reason for hiding this comment

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

Since copyrights do expire this needs to include a year indicating the age of the changes.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Agreed will fix.

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.

2 participants