Robert Black schrieb: > Hello > > I have recently been able to get OOo to build on windows and have made a few > hacks from the tutorials. I am now trying to figure out how I can work most > efficiently in terms of make code change, rebuild, and run to view changes. > > What I have been doing is making my changes, rebuilding the particular > module, then calling "deliver -check" to see what needs updating. Then I > manually find those files in the source tree, search my development OOo > install directory to find out where they belong, then manually copy them in. > It seems to me that this process of manually locating files in two trees and > copying between them is a big time waster and there must be a better way. > > I gather OOo cannot run from the source directory so some kind of scripted > copying seems to be in order. Does anyone know of any tools that can do > this? Am I missing something?
OOo does not run from a source directory, it must be installed. One might think that it should be possible to make OOo load libraries from the "solver" directory by starting the installed OOo from a shell and point the path variable of the shell to solver/wntmsci12/bin so that all modified and delivered libraries are found first. This indeed should work for most of the OOo libraries. IIRC in pre-3.0 times at least VCL, configmgr and the cppu library had to be located next to the executable file so that they couldn't be loaded from elsewhere. I don't know how this works nowadays in the "3 layer world", but I would assume that these libraries still are a little bit "special". Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[email protected]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
