Revision as of 08:42, 8 June 2013 by PatrickGeorgi (Created page with "The following Howto by an anonymous contributor details how to configure a Cygwin setup as a coreboot development environment. # <code>$ git clone http://review.coreboot.org/...")
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/util# assuming you have downloaded coreboot code under C:\source
$ cd 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.
- 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.
- Now, you need iasl in your path as well:
- Download ACPICA from https://acpica.org/downloads
- Change directory to where your APCICA is downloaded
$ tar xzf acpica-unix-VERSION.tar.gz
$ cd acpica-unix-VERSION && make clean && make && make install
- iasl will show up in /usr/bin
- At this point, you should 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 go to the problematic directories, and does a “chmod 644 *.*” to make sure all files are readable and writable.
- 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.
- Once you did all the “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.