Re: [dev] Problem with CWS configuration
Hi Bartosz
On 07/01/10 09:11, Bartosz wrote:
Hi.
I have big problem with configuration of the $HOME/.cwsrc file.
I followed instruction:
http://wiki.services.openoffice.org/wiki/Mercurial/Cws
If I do not create $HOME/.cwsrc file i have following error after type command:
cws create --hg DEV300 svarray_remove
Here is an error:
Use of uninitialized value $ENV{COMMON_ENV_TOOLS} in concatenation (.) or
string at
/home/a/Pulpit/rozne/dev/openoffice/DEV300/solenv/bin/modules/CwsConfig.pm
line 560.
ERROR: can't find CWS config file '$HOME/.cwsrc'.
at /home/a/Pulpit/rozne/dev/openoffice/DEV300/solenv/bin/modules/Cws.pm
line 47
Compilation failed in require at
/home/a/Pulpit/rozne/dev/openoffice/DEV300/solenv/bin/cws.pl line 51.
BEGIN failed--compilation aborted at
/home/a/Pulpit/rozne/dev/openoffice/DEV300/solenv/bin/cws.pl line 51.
I found WIKI page how to configure CWS, but it is outdated :-( It setup the
CVS, not mercurial.
http://wiki.services.openoffice.org/wiki/CWS
What about http://wiki.services.openoffice.org/wiki/.cwsrc ?
How I should setup the .cwsrc file?
Maybe someone have proper an example of the $HOME/.cwsrc file?
Best Regards
Bartosz
Ruediger
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Problem with CWS configuration
On 07/01/10 09:55, Bartosz wrote: Hi Ruediger. 2010/7/1 Ruediger Timm ruediger.t...@sun.com: What about http://wiki.services.openoffice.org/wiki/.cwsrc ? I don't understand this .cwsrc example. I think it is outdated. Why I must configure CVS (login and password)? I thought that CVS is obsolete, and I would like to use Mercurial. That page states: Of course Subversion or Mercurial will not access the CVS repository, but the CVS_ID and CVS_PASSWORD fields are also used by the cws tool for EIS access. The command: cws create --hg DEV300 foo42 mean that it should use mercurial (--hg parameter). Why it ask me about CVS login/password. If the CVS login/password is required to Mercurial connect, how I could get it? The example given in the wiki has # Your CVS login (for authentication with the CWS database). CVS_ID=YOUROOOLOGIN # Your scrambled CVS password (for authentication with the CWS database). # Take this one from .cvspass (should be last field on the line and look # like Aac`l;kde or something like that) CVS_PASSWORD=YOURSCRAMBLE Could you please send some example of the .cwsrc file? That wiki page gives an example. Best Regards Bartosz Rüdiger - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Prebuilt Mozilla DLLs on tools.openoffice.org differ from those in the installer
On 07/01/10 14:18, Tor Lillqvist wrote: So if you say that in an OOo installed from a downloaded installer, there are *Mozilla* libs (*not* OOo libs!) which are linked against msvcr90.dll, I'd b somewhat surprised. Do you have an example? Sure. For instance nspr4.dll and nss3.dll in an OOo installed from OOo_3.2.1_Win_x86_install_en-US.exe downloaded on June 25. --tml Those two libs AFAIK originate from module nss. Rüdiger - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Working with OOO330 and DEV300
On 06/18/10 22:01, Pavel Janík wrote: Hi, On 18.6.2010, at 19:41, Jens-Heiner Rechtien wrote: Lastly: RE will do always complete builds on DEV300 milestones from now on. yay! Thanks for this decision. /me waiting for GSI-cs.url file containing the link to http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/build/Files/DEV300/GSI_cs.sdf.bz2 :-) and build wgetting it all the time. After this /me retires :-) So, hopefully such thing won't get implemented in the foreseeable future. It would be a pity if you retired ;-) Rüdiger - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Build Open office 3.20 on window XP
Hi! What shell do you use for building? Rüdiger On 06/20/10 14:25, Lê Vie^.t Quang wrote: Dear sir , I try to build OOO320_m12 on window XP , but it fail , and take this error , what is it ? = Building module soltools /cygdrive/e/ooo320_m12/soltools/winunistd `../wntmsci12.pro/inc/unistd.h' is up to date /cygdrive/e/ooo320_m12/soltools/mkdepend - /cygdrive/e/ooo320_m12/soltools/support -- Compiling: soltools/support/simstr.cxx C:/PROGRA~1/MICROS~1.0/VC/bin/cl.exe -Zm500 -Zc:forScope,wchar_t- -GR -c -nologo -Gs -Gy -Ob1 -Oxs -Oy- -DENABLE_LAYOUT=0 -DENABLE_LAYOUT_EXPERIMENTAL=0 -Gd -I. -I../ wntmsci12.pro/inc/soltools_support -I../inc -I../inc/pch -I../inc -I../WIN/inc -I../wntmsci12.pro/inc -I. -IE:/ooo320_m12/solver/320/ wntmsci12.pro/inc/stl -IE:/ooo320_m12/solver/320/wntmsci12.pro/inc/external-IE:/ooo320_m12/solver/320/ wntmsci12.pro/inc -IE:/ooo320_m12/solenv/wntmsci12/inc -IE:/ooo320_m12/solenv/inc -IE:/ooo320_m12/res -IE:/ooo320_m12/solver/320/ wntmsci12.pro/inc/stl -IC:/PROGRA~1/Java/JDK16~1.0_2/include/win32 -IC:/PROGRA~1/Java/JDK16~1.0_2/include -IC:/PROGRA~1/MI2578~1/Windows/v6.1/include -IC:/PROGRA~1/MICROS~1.0/VC/include -IE:/ooo320_m12/solver/320/ wntmsci12.pro/inc/offuh -I. -I../res -I. -Wall -wd4061 -wd4127 -wd4191 -wd4217 -wd4250 -wd4251 -wd4275 -wd4290 -wd4294 -wd4355 -wd4511 -wd4512 -wd4514 -wd4611 -wd4625 -wd4626 -wd4640 -wd4675 -wd4710 -wd4711 -wd4786 -wd4800 -wd4820 -wd4503 -wd4619 -wd4365 -wd4668 -wd4738 -wd4826 -wd4350 -wd4505 -wd4692 -wd4189 -wd4005 -wd4180 -DWNT -DWNT -DNT351 -DMSC -DM1500 -DINTEL -D_X86_=1 -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_NON_CONFORMING_SWPRINTFS -DFULL_DESK -DBOOST_MEM_FN_ENABLE_CDECL -DSTLPORT_VERSION=400 -D_MT -DWINVER=0x0500 -D_WIN32_IE=0x0500 -DCPPU_ENV=msci -DSUPD=320 -DPRODUCT -DNDEBUG -DPRODUCT_FULL -DOSL_DEBUG_LEVEL=0 -DOPTIMIZE -DCUI -DSOLAR_JAVA-DWIN32 -D_MT -D_DLL -DWIN32 -D_MT -D_DLL -DEXCEPTIONS_OFF -Fo../ wntmsci12.pro/obj/simstr.obj E:/ooo320_m12/soltools/support/simstr.cxx simstr.cxx echos PATH=%PATH%;E:/ooo320_m12/solver/320/wntmsci12.pro/bin ../ wntmsci12.pro/bin/makedepend @E:/Cygwin/tmp/mklDci6b ../ wntmsci12.pro/misc/o_simstr.dpcc echos: Command not found. E:/ooo320_m12/solver/320/wntmsci12.pro/bin: Permission denied. dmake: Error code 1, while making '../wntmsci12.pro/obj/simstr.obj' dmake: '../wntmsci12.pro/obj/simstr.obj' removed. ERROR: Error 65280 occurred while making /cygdrive/e/ooo320_m12/soltools/support rmdir E:/Cygwin/tmp/TUczZ67IPM dmake: Error code 1, while making 'build_instsetoo_native' - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Build Open office 3.20 on window XP
On 06/21/10 11:02, kanminru wrote: Rüdiger Timm wrote: Hi! What shell do you use for building? Rüdiger I use tcsh shell. This is my first time working with OpenOffice and I do not have much experience. I try to follow the instructions in http://wiki.services.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows http://wiki.services.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows AFAIK tcsh shell is not really supported any more (though it might be on that 3.2 code base - I just do not remember exactly). Could you just try using bash instead? Ruediger - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Re: BigPointerArray, SvPointerArray vs STL containers
On 06/15/10 09:06, Bartosz wrote:
Getting rid of SvArray might not be enough alone to fix this, but it
would be a big step in the right direction. Please also have a look at
the work in cws new_itemsets which tries to get rid of the old
SfxItemSet implementation and replace it with stl container-based stuff
whereever possible. Changing such a fundamental datastructure is not
easy at all, but the new implementation is mostly stable by now -- only
a few minor glitches remaining.
Where I could find the cws new_itemsets?
Please specify link to it.
Childworkspaces may be found like this:
Code repository at
http://hg.services.openoffice.org/hg/cws/new_itemsets/
Additional information (EIS) at
http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fnew_itemsets
Ruediger
By the way.
After replace svArrays by STL containers, in some cases I observed boost of performance.
For example:
for (USHORT i = 0; i aEntries.size(); ++i)
{
if (aEntries.at(i).aFntFmt == rFntFmt)
{
aRes = aEntries[i].aId;
break;
}
}
is much faster than:
USHORT nCnt = aEntries.Count();
USHORT i;
for (i = 0; i nCnt0 == aRes.Len(); ++i)
{
if (aEntries[i].aFntFmt == rFntFmt)
aRes = aEntries[i].aId;
}
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Should assertions abort?
Hi Frank, I am indifferent regarding whether assertions should abort, but please let me comment your suggestions below: On 02/12/10 09:11, Frank Schoenheit, Sun Microsystems Germany wrote: Hi, issue 109142 (http://www.openoffice.org/issues/show_bug.cgi?id=109142) requests to change the behavior of assertions (OSL_ASSERT/DBG_ASSERT and friends) to abort if their condition is not met. The current behavior is that the assertion text is reported to the user, usually by a message box. All of the above applies to non-product builds only, in particular, the request, as I understand it, is *not* to extend assertions to product builds. Since this is a controversial topic, I think we should discuss it in a wider audience before actually implementing the change - so, let's get the party started ... [...] The problem which the issue tries to address, however, is still valid, and highly legitimate, in my opinion. Assertions are a cheap and already-existing measure to improve our product quality (and in my personal opinion, both the 3.1 and the 3.2 release have shown that we should improve here). Still, too few people use non-product builds, which means new assertions are introduced, which means more people are scared away from using non-product builds ... which renders assertions nearly useless. So, my suggestions would be the following (admittedly, they're more on a social level, than on a technical one, and thus harder to enforce): - Developers should use non-product builds *only*. That's a very apparent measure, still, a lot of people don't do. If you ask why, often the answer is it's unusable 'cause of the many assertions. Hmm? - QA should use non-product builds *only*. Yes, I am not kidding about this. An assertion which fails indicates a *bug*, that's the very original intention of assertions: report bugs. Speaking strictly, QA which refuses to use non-product builds refuses to do their job, which at least in parts consists of finding bugs. Here I strongly disagree. Assertions should be fought before a CWS sees QA. That's something developers should do. Testers have to test what the customer will get. - Report assertions as you find them, and fix them as you get the issues assigned. Give them high priority, as every assertion might be a little effort for you to fix, but it is a lot of paint for a lot of other people as long as it is not fixed. +1 - Get *serious* management backup for the three previous items. (insiderThat's something which is highly missing since MA left years ago :) /insider) - Provide non-product builds for release code lines, too. At least do so much longer than we did with OOO320 (This item strictly applies to Sun-internal workflows.): For OOO320, we stopped providing non-product builds at branch-off day, which was about half a year before the product was actually released. During a significant part of this time, there still happened heavy development on that code line, which is prone to introducing new assertion failures, going unnoticed in product builds. That's not correct. OOO320 started end of September 2009. Branch date was code freeze, afterwards only stopper bugs got accepted. We once decided to restrict non-product builds for code lines where active development happens, and I still believe that is a good decision. Release branches as we currently handle them are definitely not the place for heavy development. - Basically: Understand that assertions are not there to hinder your work. They exist to help you (at pretty low costs) finding bugs in your code, and thus improving our product - which is something we all should be interested in, right? - Consequently, *use* assertions when writing new code. There's no such thing as too much assertions in the code - as long as they never fire, of course :) Ciao Frank Rüdiger - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Errors using gsicheck on DEV300_m60
On 09/30/09 00:12, Kristján Bjarni Guðmundsson wrote:
I tried running gsicheck on the en-US.sdf file for the DEV300_m60 release
and I am getting these errors:
Error: File format, Line 72253, UniqueID uui/source\ids.src/title/)///:
Source Language entry double. Treating as Translation.
Error: File format, Line 72254, UniqueID uui/source\ids.src/title/)///:
Source Language entry double. Treating as Translation.
Error: File format, Line 72254, UniqueID uui/source\ids.src/title/)///:
Translation Language entry double. Checking both.
Error: File format, Line 72255, UniqueID uui/source\ids.src/title/)///:
Source Language entry double. Treating as Translation.
Error: File format, Line 72255, UniqueID uui/source\ids.src/title/)///:
Translation Language entry double. Checking both.
Error: File format, Line 72255, UniqueID uui/source\ids.src/title/)///:
Translation Language entry double. Checking both.
I there a newer version of gsicheck that I am supposed to use with the
DEV300_m60 version?
There is a syntax bug in file uui/source/ids.src causing this buggy
lines in the sdf file. So, gsicheck is correct, the sdf file isn't. The
bug is fixed in revision 276471 for upcoming DEV300 m61 and in revision
276464 for branch OOO320.
Rüdiger
Index: ooo/uui/source/ids.src
===
--- ooo/uui/source/ids.src (revision 276428)
+++ ooo/uui/source/ids.src (working copy)
@@ -45,12 +45,12 @@
};
-String( STR_WARNING_BROKENSIGNATURE_TITLE )
+String STR_WARNING_BROKENSIGNATURE_TITLE
{
Text [ en-US ] = Invalid Document Signature ;
};
-String( STR_WARNING_INCOMPLETE_ENCRYPTION_TITLE )
+String STR_WARNING_INCOMPLETE_ENCRYPTION_TITLE
{
Text [ en-US ] = Non-Encrypted Streams ;
};
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
