I would rather not have the noise. :) I'll see if it is affecting the EVC4 build in a little bit.
David Trotz wrote: > John, > My eVC 3 has these errors as well but if you let it run through you will > find they are not critical enough to lead to a broken build. You will > still get a sword.dll in the end. > As far as commenting the line out I suggest you do not do that. The file > is part of the sword library and thus the file may serve a purpose on a > different platform. If we find it to be a problem later we can instead > do something like > #ifndef __EVC3__ > #include <mem.h> > #endif > But for now just leave it be. > > In Christ, > David Trotz > > > SonWon wrote: > >> When I Rebuild All using EVC3 I get many errors like this: >> >> Could not find file mem.h >> >> If I remember correctly this is needed for a DOS build not windows. So >> I rem the line out in swbuf.h (A Sword function) and now all of the >> mem.h errors are gone. Do we need to just rem this out or is there a >> better way to fix this? >> >> Someone not getting these errors check your swbuf.h to see if it is rem >> out. I am thinking that if you are using Visual Studio (VS) then you do >> not need to rem this line out as mem.h comes with VS, I think. I have a >> copy of VS 2005 now and I can test later. I don't want to reload all of >> the modules again at this time, that was painfully slow. >> >> >> > > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > -- SonWon I choose God and all that my choice entails in this life even unto death and look forward to the new life that will come. _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page