Developer Manual/Tools/Cygwin

From coreboot
Revision as of 08:42, 8 June 2013 by PatrickGeorgi (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

The following Howto by an anonymous contributor details how to configure a Cygwin setup as a coreboot development environment.

  1. $ git clone # Get the coreboot code
  2. $ cd /cygdrive/c # this is your C drive
  3. $ cd source/coreboot/util # assuming you have downloaded coreboot code under C:\source
  4. $ cd crossgcc
  5. $ ./buildgcc
  6. 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.
  7. Once “./buildgcc” is done, you have all the GCC tools available to you.
  8. Open a DOS window and type “path” at the prompt. You should have something like C:\cygwin\usr\local\bin;C:\cygwin\usr\bin;C:\cygwin\bin in your PATH variable.
  9. Now, you need iasl in your path as well:
    1. Download ACPICA from
    2. Change directory to where your APCICA is downloaded
    3. $ tar xzf acpica-unix-VERSION.tar.gz
    4. $ cd acpica-unix-VERSION && make clean && make && make install
    5. iasl will show up in /usr/bin
  10. At this point, you should all the tools you need for building a Coreboot project.
  11. Now, let’s try to build it:
    1. $ cd source/coreboot # or wherever your Coreboot source code is
    2. $ 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
    3. If your “make” shows error messages, like, “Permission Denied”, you need to go to the problematic directories, and does a “chmod 644 *.*” to make sure all files are readable and writable.
    4. 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 the c:/cygwinc/source/coreboot directory and try again.
    5. Once you did all the “chmod” to resolve permission denied errors and deleted the .xcompile file, try “make clean” and “make” again.
  12. You should see the build complete with a ROM image map showing at the end.