On 02/14/14 00:58, Bill Paul wrote:
> Of all the gin joints in all the towns in all the world, Bill Paul had to
> walk
> into mine at 15:58:11 on Thursday 13 February 2014 and say:
>
>> In case there are any other interested parties out there, I put up a quick
>> description of how I set up the EDKII to build OVMF on FreeBSD. It's pretty
>> straightforward. As long as you have the required packages installed
>> (Python, GNU make, bash, etc...) it goes pretty smoothly. Yes, I know the
>> UNIXGCC build is not a path well traveled, but it works well enough for
>> me.
>>
>> -Bill
>
> It helps if I include the URL, doesn't it. >_<
>
> http://people.freebsd.org/~wpaul/edk2/README.txt
I'm attaching a patch that fixes two typos, explains that the default FD
size depends on the build target (DEBUG vs. RELEASE), and mentions the
-n build option (for a multi-threaded build). Feel free to apply what
you feel like.
Jordan, can we link this document from the TianoCore wiki?
I'm thinking of the
<http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Step-by-step_instructions>
article.
Under "Unix-like systems", we could create another bullet (indented one
level deeper), saying "FreeBSD (not officially supported for the time
being)", and linking to Bill's article.
(Technically I could do that right now, but I want to run it by you first.)
Thanks
Laszlo
--- README.txt.orig 2014-02-14 00:54:23.000000000 +0100
+++ README.txt 2014-02-14 14:59:18.132862525 +0100
@@ -9,7 +9,7 @@
The EDKII developer kit is supported on many platforms. Below are my notes
for building OVMF on FreeBSD.
-Using the EDKII with FreeBSD not that different from other platforms,
+Using the EDKII with FreeBSD is not that different from other platforms,
with the one major difference being that you can't use the host tool chain
to build: you have to use the cross compiler approach instead, with a
GCC and binutils targeted for a MinGW configuration. (This approach
@@ -85,7 +85,7 @@
your path so that /usr/local/bin comes first, or else you can use the
following trick:
-% cd muEDKdir
+% cd myEDKdir
% ln -s /usr/local/bin/make make
% setenv PATH `pwd`:$PATH
@@ -203,10 +203,14 @@
bash$ build -a IA32 -b RELEASE -t UNIXGCC -DFD_SIZE_2MB
-DSECURE_BOOT_ENABLE=TRUE -p OvmfPkg/OvmfPkgIa32.dsc
bash$ build -a X64 -b RELEASE -t UNIXGCC -DFD_SIZE_2MB
-DSECURE_BOOT_ENABLE=TRUE -p OvmfPkg/OvmfPkgX64.dsc
- The FD_SIZE_2MB option is used because I have found that when building
- with secure boot enabled, the X64 object code is too big to fit into a 1MB
- compressed image, which is the default. If you elect not to build with
- secure boot, it should be okay to leave this out.
+ The FD_SIZE_2MB option is used because I have found that when building with
+ secure boot enabled, the X64 object code is too big to fit into a 1MB
+ compressed image, which is the default for the RELEASE build target. If you
+ elect not to build with secure boot, or are fine with the default DEBUG build
+ target, it should be okay to leave -DFD_SIZE_2MB out.
+
+ The -nTHREADS option can be optionally specified for a parallel (faster)
+ build.
NOTE: Compilation may halt due to warnings when building the
edk2/OvmfPkg/QemuFlashFvbServicesRuntimeDxe/FwBlockService.c
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
