Hi Per, *, On Wed, Jul 15, 2009 at 10:01 PM, Per Eriksson<pereriks...@openoffice.org> wrote: > Christian Lohmaier skrev: >> On Wed, Jul 15, 2009 at 9:07 PM, Per Eriksson<pereriks...@openoffice.org> >> wrote: > [...] >> Having a "book" on how to build OOo gives a wrong impression or is way >> too broad to be useful as reference. >> > > Think about the following: > > We have new developers who need to find all the information related to > building farily quickly and easily.
Yes. I agree. But in my eyes that means: The page(s) must be short. With only the necessary parts listed. Everything else on seperate pages. > We have new developers who would benefit a lot to see the similarities > between the platforms in the building process. Exactly why it is so similar, the page needs to be small and the os-specific parts left out. > [...] > For the Windows platform etc. there are several ways of building the > software, and the instructions in its most compact form seem to take up at > least 5-6 pages. For community builders, there is only one way. Namely using cygwin (and 4nt is going to be obsoleted/removed completely) anyway. And virtually any newcomer will build using the personal-edition of the MS-compiler (available free of charge). And the walkthrough page (Building OOo on Windows with cygwin) is good for the prerequisites, but the actual building (running configure and everything afterwards) should not be part of the actual build instructions. Neither is the (details of) OOo's source-code management. Most developers wouldn't mind installing linux for developing OOo anyway (compiling on linux is way faster than compiling on windows) ciao Christian --------------------------------------------------------------------- To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org For additional commands, e-mail: mac-h...@porting.openoffice.org
