On Fri, Sep 12, 2014 at 6:05 AM, Scott Duplichan <[email protected]> wrote: > Jordan Justen [mailto:[email protected]] wrote: > > > ]On Thu, Sep 11, 2014 at 10:17 PM, Nikolai Saoukh <[email protected]> wrote: > ]> Probably no one use debug stuff nowadays ;-) > ] > ]You didn't intend for this line to be in the commit message, right? > ] > ]I think this may have been the 3rd time someone submitted this. (And, > ]this goes way back...) :( > ] > ]The reason I think it was added this way originally is that someone > ]was using CYGWIN on Windows. That has also been the hangup for not > ]fixing it in the past. Concern about what it *might* break. > > I am pretty sure EDK2 projects cannot be built using Cygwin > on Windows. I was told the gcc linker supplied with Cygwin > makes PE only executables, while the EDK2 unix build > environment expects ELF executables.
Some toolchains make ELF executables, but they get converted to PE by the GenFw tool. So, in the CYGWIN case GenFw would just skip that conversion since it is already PE. > Other tool chains that > are not in good working order: > 1) DDK3790 > 2) VS2003 > 3) VS2005 > 4) VS2013 What issue do you see? > I would be happy to submit a patch to fix the 4 broken > Windows tool chains if there is any interest. Yes, of course. -Jordan ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
