Michael wrote: > [reasons against autotools] > Granted. Though re-working OOo's make system in and of itself will consume substantial resources, so I guess the question whether to code another make system that's only used inside OOo, or whether to use/extend something that's in wide-spread use out there deserves some thoughts ...
> [cmake] > > but regarding IDEs, Bjoern just yesterday tried loading the sw module and > the inc directory from the solver into some IDEs... > iirc, visual studio parsed the headers for half an hour, and was then > unusably slow; netbeans (with some gigabytes of heap) was barely usable. > Reportedly eclipse works rather well with a limited set of modules; which will be more or less attained via the split build endeavour at some point in time. > does anybody really use an IDE for developing OOo? > from what i know people use text editors, or they use an IDE basically > like a text editor. > I know a few cases where people have tried; ultimately though, if one becomes a core dev, folks work on OOo the way you describe it (which may be related to the fact that maintaining those project files manually is a PITA). But may considerably lower the barrier of entry for new devs. Cheers, -- Thorsten
pgpRFrO0S5w04.pgp
Description: PGP signature
