[dev] ERROR: Error 65280 occurred while making /cygdrive/c/ooo2/libwpd

2007-01-17 Thread KAMI

Hello!

I tried to compile OOo 2.1 under Windows/Cygwin, but somehow liwpd has 
error. Here is my log:



=
Building project libwpd
=
/cygdrive/c/ooo2/libwpd
mkout -- version: 1.7
dmake: Executing shell macro: +$(WRAPCMD) echo $(subst,$/stl, $(SOLARINC))
-
if ( -e ./wntmsci10.pro/misc/build/libwpd-0.8.6 ) mv 
./wntmsci10.pro/misc/build/libwpd-0.8.6 
./wntmsci10.pro/misc/build/libwpd-0.8.6_removeme

rm -rf ./wntmsci10.pro/misc/build/libwpd-0.8.6_removeme
mkdir: cannot create directory `./wntmsci10.pro/misc/': File exists
dmake: Executing shell macro: +$(TYPE) 
$(PRJ)$/$(ROUT)$/misc$/$(TARFILE_NAME).unpack
cd ./wntmsci10.pro/misc/build  ( gunzip -c 
../../../download/libwpd-0.8.6.tar.gz  | tar  -xvf -)  
/usr/bin/touch.exe so_unpacked_wpd

libwpd-0.8.6/
[...]
libwpd-0.8.6/docs/doxygen/header.html.in
make writeable...
cd ./wntmsci10.pro/misc/build  cat ../../../libwpd-0.8.6.diff | tr -d 
\015 | patch -b -p2  /usr/bin/touch.exe so_patched_wpd

patching file libwpd-0.8.6/src/lib/makefile.mk
patching file libwpd-0.8.6/src/lib/WP3VariableLengthGroup.cpp
/usr/bin/touch.exe ./wntmsci10.pro/misc/build/so_configured_wpd
mkdir ./wntmsci10.pro/misc/build/libwpd-0.8.6/src/lib
mkdir: cannot create directory 
`./wntmsci10.pro/misc/build/libwpd-0.8.6/src/lib': File exists
cd ./wntmsci10.pro/misc/build/libwpd-0.8.6/src/lib  dmake 
/usr/bin/touch.exe 
/cygdrive/c/ooo2/libwpd/./wntmsci10.pro/misc/build/so_built_wpd
dmake:  Error code 5, while making 
'../../../../../../wntmsci10.pro/misc/s_WP3UnsupportedFixedLengthGroup.dpcc'
dmake:  
'../../../../../../wntmsci10.pro/misc/s_WP3UnsupportedFixedLengthGroup.dpcc' 
removed.

---* TARGET.MK *---
dmake:  Error code 255, while making 
'./wntmsci10.pro/misc/build/so_built_wpd'

---* tg_merge.mk *---

ERROR: Error 65280 occurred while making /cygdrive/c/ooo2/libwpd


Can you help me?

KAMI

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [dev] equivalent to insert ink comment?

2007-01-17 Thread Mathias Bauer
Jeff Cours wrote:

 Howdy --
 
 I use OO 2.1 Writer to take notes in class.  I'm running it on a Windows 
 Tablet PC.  I would really like the the ability to pop out the stylus 
 and draw a diagram into the middle of my notes.  I currently have 
 ctrl-shift-D bound to insert a frame where I can use the drawing tools 
 to create a diagram, but the drawing tools are too cumbersome to keep up 
 with a professor writing on the board full blast.  Even the freehand 
 drawing tool has to take time to find the endpoints and to all the nifty 
 things that let you grab it and move it around, by which time the prof's 
 moved on to the next thing. 
 
 What I really want is something similar to Word's insert ink comment: 
 a very fast thread that just grabs the mouse position, as long as the 
 button's down, and throws the bits into the frame as a bitmap drawing.  
 Ideally, it should be fast enough to capture written words, though I 
 don't care at all if it can do OCR. It would also be wonderful if it 
 supported the ability to erase (preferably by letting me use the 
 eraser end of the stylus, as some of the tablet-aware software does).
 
 Does anyone know of such a feature, or an extension that might provide 
 that feature?

As you are using Windows you could insert an OLE object with MSPaint. It
should be possible to create a macro that inserts such an object and by
assigning it to a button or shortcut you can insert it pretty fast.

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]



[dev] New Master Workspace for OOo 2.2 Release opened

2007-01-17 Thread Rüdiger Timm

New Master Workspace for OOo 2.2 Release opened
===

OpenOffice.org release 2.2 is approaching, see 
http://wiki.services.openoffice.org/wiki/OOoRelease22


This brings some changes in CWS handling:

*Choosing CWS Release*
--
Owners of child workspaces not meant for the next release should set its 
'Release' field to the next feature release. In this case its OOo 2.3. 
This holds true for child workspaces introducing new features. Only bug 
fix issues with target OOo 2.2 should be fixed in 2.2-Release CWS.



*Choosing Master Workspace*
---
We have opened a new code line to stabilize for OOo 2.2, called OOF680. 
First milestone OOF680 m1 will be available soon. When opening a new 
child workspace for 2.2 Release (see above) OOF680 should be choosen as 
master workspace. For 2.3 bound child workspaces please take SRC680 as 
usual. If in doubt, use SRC680.
In any way release engineering will take care that all CWSs integrated 
for 2.2 additionally get integrated for 2.3, too.



*Approving / Nominating a CWS*
--
Child workspaces for the upcoming release need explicit nomination by a 
project lead or a member of the Release Committee. Status history than 
looks like new - ready for QA - approved by QA - nominated - 
integrated.
Childworkspaces for OOo 2.3, to be integrated into SRC680 only, do not 
know the 'approved by QA' state. QA representatives directly set them to 
'nominated', i.e. we have new - ready for QA - nominated - 
integrated. See

http://www.openoffice.org/servlets/ReadMsg?listName=devmsgNo=18349




A general picture of our current release model and how it relates to 
code lines is given in

http://wiki.services.openoffice.org/wiki/Release_Model
(Please note that the sketch given there correctly describes the 
principle of opening seperate code lines for releases but has incorrect 
dates.)





Rüdiger

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [dev] Renaming #openoffice.org into #dev.openoffice.org?

2007-01-17 Thread Christian Junker

+1

2007/1/17, Pavel Janík [EMAIL PROTECTED]:

Hi,

as you probably know, several people want to do this operation on
freenode.net:

renaming current #openoffice.org channel to #dev.openoffice.org

This should free #openoffice.org (the default guess) channel
afterwards for generic OOo channel, mainly oriented to support our
users.

I'd like to call for vote here to collect some general dev attitude
to this act.

So: do you want to rename the channel? +1 means yes, -1 means no, +0
means What is a channel?




--
Best Regards
Christian Junker

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [dev] Renaming #openoffice.org into #dev.openoffice.org?

2007-01-17 Thread eric b

Hi,

+1 for me : good idea


Regards,
Eric Bachard


Le 17 janv. 07 à 22:31, Pavel Janík a écrit :



I'd like to call for vote here to collect some general dev attitude  
to this act.


So: do you want to rename the channel? +1 means yes, -1 means no,  
+0 means What is a channel?


Please vote in this thread. The deadline (me as a benevolent  
dictator decided ;-) is this Friday, 23:59:59 UTC.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[dev] Re: Renaming #openoffice.org into #dev.openoffice.org?

2007-01-17 Thread Ain Vagula
Pavel Janík wrote:

 Hi,
 
 as you probably know, several people want to do this operation on
 freenode.net:
 
 renaming current #openoffice.org channel to #dev.openoffice.org
 
 This should free #openoffice.org (the default guess) channel
 afterwards for generic OOo channel, mainly oriented to support our
 users.
 
 I'd like to call for vote here to collect some general dev attitude
 to this act.
 
 So: do you want to rename the channel? +1 means yes, -1 means no, +0
 means What is a channel?
 
 Please vote in this thread. The deadline (me as a benevolent dictator
 decided ;-) is this Friday, 23:59:59 UTC.

+1. 
Btw, I suggest also developers to be more active on users channel. Stupid or
too simple questions are rare here, most questions are quite interesting.

ain

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]