On 2014-11-07 15:53:55, Andrew Fish wrote: > I was having lunch today with Mike Kinney, and Vincent Zimmer > (unfortunately no Tanqueray involved) and I think I’ve distilled the > issue down to a new feature that we need from the build system. I > want to be able to have an Xcode (or VC++, or Intel compiler) target > that uses .S (.asm) if both .S (.asm) and .nasm are present. I was > want to be able to have an Xcode target that uses .nasm if both the > .S and .nasm are present. Mike was going to go talk to the > BaseTools maintainers and figure out the best way to do this.
Hmm. If we are considering a BaseTools change, then one thought I had was let a toolchain (or maybe family) select a preference list for certain extensions. *_GCC49_*_*_EXTENSIONS = nasm S *_VS2013_*_*_EXTENSIONS = nasm asm *_XCODE5_*_*_EXTENSIONS = S nasm I don't see rules like this in tools_def, so I'm not sure it is supported, but it would be nice too: GCC:*_*_*_*_EXTENSIONS = nasm S Basically this would only be used if 2 source files have the same base name. In that case, the extension listed first would be used. This would still allow XCODE to build modules that had .nasm only. But, for modules where a .S is available, then NASM wouldn't be required. -Jordan ------------------------------------------------------------------------------ _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
