Hi Takashi, Takashi Ono wrote: > Hi Pavel, > > In message "Re: [tools-dev] Requirement for DEV300 build-Win32", > Pavel_Jan〓 wrote... > > >I think we should switch .NET2003 into the same mode as gcc-3.3 is on > >unixes. We should apply patches that are available but our default > >compiler should be the newer one (I now have e.g. WaE issue in module > >svx, #i87959#). > > I quite agree with you at the point we should not stick to older versions of > compilers, but I do not see any essential problems with .NET 2003 except that > it does > not fit with new SDK because of the following a) and b) > > a) Microsoft no longer recommends .NET 2003.
the .Net 2003 compiler doesn't support the new manifest mechanism for Windows Vista. You will run from one workaround into the next workaround. I don't think that a self assembled .Net 2003 compiler / Vista SDK configuration will work as a good reference for your MingW port project to eliminate side-effects, because the side-effects of such a configuration itself haven't been investigated. > b) New SDK includes a header sal.h that is not distributed along with SDK. > The suggestion to copy the missing sal.h from a .Net 2008 Express installation into the Vista SDK and then using .Net 2003 with this self assembled SDK isn't a real way. Where is the beef doing so? Who should fix bugs based on side-effects for such a configuration? > Everything else is perfect if we handle SDK dependencies and compiler version > dependencies independently. Unfortunately in some OOo makefiles SDK dependent > conditionals are included within compiler version conditional blocks > (#i87940#, > #i87941#). > > Takashi Ono ([EMAIL PROTECTED]) Oliver --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
