I tried build OOO340 code line on cygwin and got an error:
=
Building module postprocess
=
Entering
/cygdrive/c/Users/user/projects/openoffice/OOO340/source/postprocess/checkdeliver
mkout -- version: 1.8
C:/cygwin/bin/perl checkdeliver.pl -l
../
Hi Dmitry,
you should do what the message at the end says: deliver "sc" and "sd"
again. For whatever reasons the time stamps don't match.
Go to sd and sc and call "deliver -force" in both directories, then goto
instsetoo_native and call "build --all:postprocess" or "build --from
postprocess"
On Wed, May 18, 2011 at 3:40 AM, tora - Takamichi Akiyama <
t...@openoffice.org> wrote:
> How big benefits could we get when such structure or class instances are
> produced in large numbers?
>
The "produced in large numbers" (plus "processed in bursts of large chunks,"
I would say) is the crucia
8.05.2011 11:20, Mathias Bauer пишет:
Hi Dmitry,
you should do what the message at the end says: deliver "sc" and "sd"
again. For whatever reasons the time stamps don't match.
Go to sd and sc and call "deliver -force" in both directories, then
goto instsetoo_native and call "build --all:post
On 18.05.2011 03:40, tora - Takamichi Akiyama wrote:
The size of class Impl_Font would reduce to 50 bytes or so from 88 bytes.
How big benefits could we get when such structure or class instances are
produced in large numbers?
Generally, this is a very valid concern. In some places where we fo
On 2011/05/18 18:06, Niklas Nebel wrote:
> Generally, this is a very valid concern. In some places where we found out
(or just assumed) that it makes a difference, we currently use smaller integer
types directly for member variables, instead of enum. For example, see eCellType
in ScBaseCell (sc
Am 18.05.2011 13:44, schrieb tora - Takamichi Akiyama:
The motivation of this topic comes from a different point. I have been
looking for a way to prevent a well-known phenomenon "A single sheet
that fits in a A4 paper with Excel turns into two or four A4 papers with
Calc."
Tweaking nPPTX and nPP
