Re: [dev] warnings01: status and how to proceed

Thorsten Behrens wrote: Stephan Bergmann <[EMAIL PROTECTED]> writes: The most pragmatic approach (and the one at least I have taken during the last couple weeks when working on warnings01) is probably to not touch the headers delivered from external projects, but instead use pragmas at the pla

Re: [dev] warnings01: status and how to proceed

Stephan Bergmann <[EMAIL PROTECTED]> writes: > The most pragmatic approach (and the one at least I have taken during > the last couple weeks when working on warnings01) is probably to not > touch the headers delivered from external projects, but instead use > pragmas at the places where those head

Re: [dev] warnings01: status and how to proceed

Stephan Bergmann wrote: [...] Another problem that only dawned on us recently is the following: The OOo source includes a number of external projects that deliver C/C++ headers that are included from other modules. To suppress warnings from such headers, patches have been included for some of

Re: [dev] warnings01: status and how to proceed

Volker Quetschke <[EMAIL PROTECTED]> writes: > IMHO tinderbox builds should be FULL builds with the community style build > system, i.e. not reusing old stuff that's in solver from previous builds. > Can you do that? > Sure, why not? -- Thorsten If you're not failing some of the time, you're

Re: [dev] warnings01: status and how to proceed

What about asking the community for these builds? We have currently a few volunteer tinderbox clients running, see . Yes, I know that there are clients already running - though, are they covering the range of platforms that Stephan mentioned?

Re: [dev] warnings01: status and how to proceed

Volker Quetschke <[EMAIL PROTECTED]> writes: > What about asking the community for these builds? We have currently a few > volunteer tinderbox clients running, see >. > Yes, I know that there are clients already running - though, are they cov

Re: [dev] warnings01: status and how to proceed

Caolan McNamara wrote: On Wed, 2006-03-01 at 20:57 +0100, Thorsten Behrens wrote: Stephan Bergmann <[EMAIL PROTECTED]> writes: However, some people build OOo in such a way that they use system-supplied alternatives of those external projects, so that the patches will have no effect for them.

Re: [dev] warnings01: status and how to proceed

On Wed, 2006-03-01 at 20:57 +0100, Thorsten Behrens wrote: > Stephan Bergmann <[EMAIL PROTECTED]> writes: > > > However, some people build OOo in such a way that they use > > system-supplied alternatives of those external projects, so that the > > patches will have no effect for them. That means t

Re: [dev] warnings01: status and how to proceed

Thorsten Behrens wrote: Stephan Bergmann <[EMAIL PROTECTED]> writes: (snip) I guess it is largely unrealistic to have every community CWS built on the four mentioned platforms - unless we (Sun) do it ourselves (me thinks that especially wntmsci10 will pose problems). Thus it's maybe a bit moo

Re: [dev] warnings01: status and how to proceed

Stephan Bergmann <[EMAIL PROTECTED]> writes: > It follows that, in an ideal world, every CWS should then be built > on unxlngi6, unxsol{i|s}4 (sufficiently similar so that one of them > ought to be enough), and wntmsci10, so that build breaks are found > early, before integration. > and > However

[dev] warnings01: status and how to proceed

Hi all, The following is an overview of where we currently are with CWS warnings01, and a discussion of how to continue: CWS warnings01 is about making the C/C++ source code of OOo warning free, at least on the four main platforms (unxlngi6, unxsoli4, unxsols4, wntmsci10). For those four pl