Revision as of 10:21, 9 June 2013 by PatrickGeorgi (iasl instructions aren't necessary, simplify chmod handling)
The following Howto by an anonymous contributor details how to configure a Cygwin setup as a coreboot development environment.
$ git clone http://review.coreboot.org/coreboot.git# Get the coreboot code
$ cd /cygdrive/c# this is your C drive
$ cd source/coreboot# assuming you have downloaded coreboot code under C:\source
$ cd util/crossgcc
- Wait for it finish in about 30 minutes, including download and build; if it fails, it might be your firewall preventing it from downloading. Sometimes, if you download or use an older version of coreboot, the ./buildgcc may not finish due to either mismatched package names or mismatched versions.
- Once “./buildgcc” is done, you have all the GCC tools available to you.
- At this point, you should have all the tools you need for building a coreboot project.
- Now, let’s try to build it:
$ cd source/coreboot# or wherever your coreboot source code is
$ make menuconfig# to make sure you have the right platform, chipset, and other options you want to build, but you may skip this step if you just want to build an existing project
- If your "make" shows error messages like "Permission Denied", you need to fix up access permissions. In cygwin, run "chmod -R a+rwX ." from the coreboot directory (/cygdrive/c/source/coreboot in the example above). Note that the arguments are case sensitive.
- If you receive a message “.xcompile:1: no suitable gcc found”, You have a .xcompile file hanging around from a previous failed build. Delete the .xcompile file from /cygdrive/c/source/coreboot directory and try again.
- Once you used "chmod" to resolve permission denied errors and deleted the .xcompile file, try “make clean” and “make” again.
- You should see the build complete with a ROM image map showing at the end.