Of all the gin joints in all the towns in all the world, B Cran had to walk into mine at 11:27:01 on Monday 06 July 2015 and say:
> (re-sending since I sent it from an address that’s not subscribed to > edk2-devel) > > On Jul 6, 2015, at 12:25 PM, B Cran <bruce.c...@gmail.com> wrote: > > On Jul 6, 2015, at 11:33 AM, Laszlo Ersek <ler...@redhat.com > > <mailto:ler...@redhat.com>> wrote: > > > > Hm... memories memories memories... Yes. Are you aware of this: > > > > http://people.freebsd.org/~wpaul/edk2/README.txt > > <http://people.freebsd.org/~wpaul/edk2/README.txt> > > I’d read bits of it a few months ago, but it seemed rather complicated and > a bit outdated so I started afresh. Er... it's not that complicated. It's only about 3 pages of instructions, and the majority of them are just telling you what packages you need on your system. :) The only outdated thing is that I think they're using a newer version of the OpenSSL package for doing secure boot. I did a fresh EDK build just a couple weeks ago so these instructions can't be that stale. I strongly prefer building a cross compile environment rather than trying to use any of the system compiler tools or the packages. It doesn't really make sense anyway since you're effectively cross-building a whole other OS in the first place. And if you're running FreeBSD on a PPC/MIPS/ARM host instead of i386/amd64, you're going to need to create your own cross build setup anyway. Once you make sure you have the right packages and have downloaded the right GCC and binutils sources, you should be good to go. The one thing that would be really nice is to have the mingw-gcc-build.py script updated to use newer versions of GCC and binutils. (Yes, I know I know: "Gee Bill, that sounds like a great idea: why don't you do that and submit a patch?" Sheesh, you guys...) > I’m hoping I can get changes such as > fixing “#! /bin/bash” to “#! /usr/bin/env bash” (non-default shells live > in /usr/local/bin on BSD) committed so people won’t need to do quite as > much patching in future. What script in particular forces you to patch this? I don't recall having to jigger any of the scripts to adjust the path of bash. -Bill > > Can it do git-blame? (AFAIK github can't, and I've missed it > > occasionally.) > > Yup. Just browse to a file (in Diffusion) then click “Enable Blame” on the > right-hand side - see http://bluestop.org/edk2/GitBlamePhab.png > <http://bluestop.org/edk2/GitBlamePhab.png> for an example. > > — > Bruce -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Member of Technical Staff, wp...@windriver.com | Master of Unix-Fu - Wind River Systems ============================================================================= "I put a dollar in a change machine. Nothing changed." - George Carlin ============================================================================= ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
