Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers. Visit Stack Exchange.
What you need to install Windows 10 on Mac
- MacBook introduced in 2015 or later
- MacBook Air introduced in 2012 or later
- MacBook Pro introduced in 2012 or later
- Mac mini introduced in 2012 or later
- iMac introduced in 2012 or later1
- iMac Pro (all models)
- Mac Pro introduced in 2013
The latest macOS updates, which can include updates to Boot Camp Assistant. You will use Boot Camp Assistant to install Windows 10.
64GB or more free storage space on your Mac startup disk:
- You can have as little as 64GB of free storage space, but at least 128GB of free storage space provides the best experience. Automatic Windows updates require that much space or more.
- If your Mac has 128GB of memory (RAM) or more, the Windows installer needs at least as much free storage space as your Mac has memory. For example, if your Mac has 256GB of memory, your startup disk must have at least 256GB of free storage space for Windows.
An external USB flash drive with a storage capacity of 16GB or more, unless you're using a Mac that doesn't need a flash drive to install Windows.
A 64-bit version of Windows 10 Home or Windows 10 Pro on a disk image (ISO) or other installation media:
- If installing Windows on your Mac for the first time, use a full version of Windows, not an upgrade.
- If your copy of Windows came on a USB flash drive, or you have a Windows product key and no installation disc, download a Windows 10 disk image from Microsoft.
- If your copy of Windows came on a DVD, you might need to create a disk image of that DVD.
How to install Windows 10 on Mac
To install Windows, use Boot Camp Assistant. It's in the Utilities folder of your Applications folder.
1. Use Boot Camp Assistant to create a Windows partition
Open Boot Camp Assistant and follow the onscreen instructions:
![Mac Mac](/uploads/1/2/5/2/125218006/698421130.jpg)
- If you're asked to insert a USB drive, plug your USB flash drive into your Mac. Boot Camp Assistant will use it to create a bootable USB drive for Windows installation.
- When Boot Camp Assistant asks you to set the size of the Windows partition, remember the minimum storage-space requirements in the previous section. Set a partition size that meets your needs, because you can't change its size later.
2. Format the Windows (BOOTCAMP) partition
When Boot Camp Assistant finishes, your Mac restarts to the Windows installer. If the installer asks where to install Windows, select the BOOTCAMP partition and click Format. In most cases, the installer selects and formats the BOOTCAMP partition automatically.
3. Install Windows
Unplug any external devices, such as additional displays and drives, that aren't necessary during installation. Then click Next and follow the onscreen instructions to begin installing Windows.
4. Use the Boot Camp installer in Windows
After Windows installation completes, your Mac starts up in Windows and opens a ”Welcome to the Boot Camp installer” window. Follow the onscreen instructions to install Boot Camp, including Windows support software (drivers). You will be asked to restart when done.
If the Boot Camp installer doesn't open automatically, your final step should be to open the Boot Camp installer manually and use it to complete installation.
How to switch between Windows and macOS
Restart, then press and hold the Option (or Alt) ⌥ key during startup to switch between Windows and macOS.
Learn more
If you have one of these Mac models using OS X El Capitan 10.11 or later, you don't need a USB flash drive to install Windows:
- MacBook introduced in 2015 or later
- MacBook Air introduced in 2015 or later2
- MacBook Pro introduced in 2015 or later2
- iMac introduced in 2015 or later
- iMac Pro (all models)
- Mac Pro introduced in late 2013
For more information about using Windows on your Mac, open Boot Camp Assistant and click the Open Boot Camp Help button.
1. If you're installing Windows and macOS Mojave on an iMac (27-inch, Late 2012), iMac (27-inch, Late 2013), or iMac (Retina 5K, 27-inch, Late 2014) and your Mac is configured with a 3TB hard drive, learn about an alert you might see during installation.
2. These Mac models were offered with 128GB hard drives as an option. Apple recommends 256GB or larger hard drives so that you can create a Boot Camp partition of at least 128GB.
Join GitHub today
![Get Core.hpp Mac Get Core.hpp Mac](http://seanerikoconnor.freeservers.com/WebDesign/Images/SciPy.jpg)
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upHave 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
Comments
commented Feb 1, 2016
There is a line of code in the OpenCV 3.1 utility.hpp the tries to create a bool check() const;. It occurs when you #include opencv2/core.hpp. Unfortunately this causes the error 'Expected member name or ';' after declaration specifiers. Since Apple uses 'check' in their AssertMacros.h,. opencv 3.1, El Capitan 10.11.3, Xcode 7.2. |
commented Feb 1, 2016
commented Feb 2, 2016
Thx for the suggestion, but Apple has that macro for a reason. I tried that already and it just creates more errors with the ViewController.o file. It needs to be fixed on opencv's framework. Call the macro cvcheck. Simple. |
commented Feb 2, 2016
There is no 'check' macro in OpenCV. It is just normal method name. Workaround #2: You can also try '__ASSERT_MACROS_DEFINE_VERSIONS_WITHOUT_UNDERSCORES=0' |
added the platform: ios/osx label Feb 2, 2016
commented Feb 2, 2016
So Apple's 'check()' macro is deprecated and should not be used anymore. |
commented Feb 2, 2016
True. There is not a macro in opencv, it is a bool that uses the same name as the Apple macro. |
commented Feb 3, 2016
I ran into quite a few problems with this method named check() and was able to work around the problem like this: As long as the opencv.hpp header is included BEFORE any apple foundation headers then the compilation works. But, this method in OpenCV really should just be changed from 'check' to anything else like 'check2' or whatever would avoid the problem |
commented Feb 4, 2016
Thank you for the help. That did the trick. I also imported all the libraries from my 'build/lib' folder. I agree, the methods bool should be renamed to help matters. I have opencv up and running on OS X! |
closed this Feb 4, 2016
added the wontfix label Feb 8, 2016
commented Feb 9, 2016
It still says the utility.hpp does nothing, but it us just a warning now. Maybe you should fix this...just my opinion. Get rid of useless files! I dont care if you fix it or not...I have fixed it myself. You really should be a bit more concerned with the problems of your clients, instead of giving them the middle finger. The tech here is completely worthless. Three cheers for GitHub........ |
commented Feb 9, 2016
@jmbapps , what do you mean? File utility.hpp is used in many places. Method CommandLineParser::check is called in several C++ sample apps to validate command line arguments. |
commented Feb 9, 2016
Thank you for the explanation, but I can read the comments. Ahem, and I quote.... Returns true if error occured while accessing the parameters (bad conversion, missing arguments, etc.). Call @ref printErrors to print error messages list. Here is what I get. opencv2/core/utility.hpp utility.hpp:729:5: Declaration does not declare anything. Thank you for your help. |
commented Feb 9, 2016
This means that check is still defined to something wrong somewhere in your build setup.For example, try to find and remove:
|
commented Feb 9, 2016
Again, thank you for the help. It is not necessary, as I have opencv working in Xcode project. The comments above fully explain what is going on. Apple Macro check is conflicting with utility.hpp bool check. If you import the opencv file before the Foundation.h then it works, but with the above warning. All you guys would have to do is rename this bool to cvcheck or something similar, but as you said...wontfix. So be it. I have it running so I do not care....until the next version. ;o) |
commented Feb 9, 2016
@jmbapps , unfortunately we can not rename this method because it will break source and binary compatibility with previous versions. As I see, the best way to reduce potential inconveniences is to add a #warning statement in the beginning of the utility.hpp explaining the cause of the problem and a suggesting a way to avoid it. Feel free to provide pull request. |
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment