eric b wrote: > Hi Albert, > > Le 20 janv. 09 à 21:17, Albert Law a écrit : > >> Hi Mathias, >> >> I tried #1 and #2, but that didn't solve the problem. I'm >> switching to MSVS2008Express to see what happens with my luck there. >> >> Someone on IRC suggested I use the following to fix the testtools >> issue: >> cp testtools/prj/build.lst testtools/prj/build.lst_back && head -1 >> testtools/prj/build.lst_back > testtools/prj/build.lst >> >> > > That's me, and the question was: how to avoid building testtools. The > command above is just an uggly hack, not the solution to your problem.
As I wrote: just rename or remove "testtools" from your source tree. The "build" command should just skip it then. And as "testtools" does not deliver anything that any other module needs to build successfully, this should not prevent you from creating an installation set. That's what I did on Windows (and that's the platform we are talking about now). I had the same problem as Albert and until yesterday this "solution #2" was the only one I know, and it worked for me. After seeing that I wasn't the only one with this problem I asked Jochen Lingner yesterday and we analyzed the problem and came up with the two other solutions. And Jochen told me that this problem will go away for the 3.1 code line soon when the version number of the assemblies will be increased. In future we should try to make sure that the version number of the assemblies is changed not only on one code lines but on all other existing newer code lines also. The problem arose because the version number was increased on the ooo300 code line (in preparation of the 3.0.1 release), but not on the dev300 code line in parallel. We should avoid that mistake when we will prepare 3.1.1. > Last, if the testtool fails, avoid building it won't solve the other > issues who will probably occur ( e.g. at packaging time, very probably ) No, as I wrote, testtools is not required to build an installation set or build any other module. Regards, 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]
