So digging in I saw there were in the .S files, and didn't look like building. So, stumbling around, I finally looked at the Conf templates and saw new entries for nasm and such. I went through the process of updating all my tool defs, setting up the PYTHON_HOME and NASM_PREFIX directories, and seems to build now except my own batch file didn't do what it normally does and give me a SUCCESS or FAILURE message so I know if all the nonsense on the screen should be looked at or not. So looking a bit more "where build" I see it's not using a batch file which will break everyone's batch files since a "call" is now needed. I think the errorlevel is returned from the call so it's sample to add call.
In short, you'll need to update build Conf if updating from older version and adjust your batch files to use "call" for build. On Sat, Dec 1, 2018 at 7:37 PM David F. <df7...@gmail.com> wrote: > Hi, > > My last SVN update was from July 2018. I just did one Yesterday now my > build breaks linking with: > > LibC.lib(Main.obj) : error LNK2001: unresolved external symbol SetJump > BaseLib.lib(LongJump.obj) : error LNK2001: unresolved external symbol > InternalLongJump > > The build is using VS2008 and the target is for X64. > > Any ideas? > > > > > _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
