Hi Benjamin,
If possible, it would be nice to be able to customize your own notes color in
OpenOffice Writer. I hope it would be possible.
already recorded here as a future idea(though I don't see it being
implemented in the near future):
Ok, with the patch and installed SDK 10.4 I get a lot further, now the
next issue is in packimages:
Entering /Software/notes11/packimages/pack
mkout -- version: 1.8
mkdir ../unxmacxi/res/img
/usr/bin/perl /Software/notes11/solenv/bin/image-sort.pl image-sort.lst
Hi Stephan,
What is weird that it is found during configure, but not anymore when
building it. I believe you are building under Snow Leopard as well?
What works for me is to pass CC and CXX not as environment variables to
configure, but as additional arguments,
./configure ... CC=gcc-4.0
Hi,
For your specific problem, I would suggest building with VERBOSE=1 so
that you see the actual compiler command line.
this is it:
gcc -fsigned-char -fmessage-length=0 -malign-natural -c -O2
-fno-strict-aliasing -DENABLE_LAYOUT=0 -DENABLE_LAYOUT_EXPERIMENTAL=0
-I.
not inside MacOSXX86Env.Set.sh.
-Max
Am 08.12.09 04:04, schrieb Stephan Bergmann:
On 12/08/09 10:57, Maximilian Odendahl wrote:
Hi,
For your specific problem, I would suggest building with VERBOSE=1 so
that you see the actual compiler command line.
this is it:
gcc -fsigned-char -fmessage
Hi,
explicitly checks for it)? Otherwise, the -isysroot setting could
explain your problems.
changing isysmaker in solenv/inc/unxmacx.mk as well as configuring with
./configure ... CC=gcc-4.0 CXX=g++-4.0 gets the build going :-)
Not sure if my system is messed up or there are bugs
Hi,
http://www.openoffice.org/issues/show_bug.cgi?id=106059
thanks for your reply, but this is not the issue here.
Be sure your build is using the 4.0 versions of gcc and g++
yes, this is the case.
What is weird that it is found during configure, but not anymore when
building it. I
Hi,
after updating to snow leopard, I can't build OOo anymore, breaks in
soltools:
Compiling: soltools/mkdepend/cppsetup.c
In file included from cppsetup.c:29:
def.h:39:19: error: stdio.h: No such file or directory
def.h:40:20: error: stdlib.h: No such file or directory
def.h:41:20: error:
With an overall positive outcome of the pilot we move over to next
phase: the implementation of a full scale migration to Mercurial. I'll
keep you posted about the details.
Great to hear that! Though I haven't used it in the OOo pilot, I did use
it on some other projects and pilots and I'm
Hi,
1) Try an rebase (cws rebase -m), this failed or was interrupted for
one reason or another
2) Do an svn revert -R . to get rid of all the already merged stuff.
3) Do cws rebase -m again, worked this time.
4) Do a cws rebase -C
suddenly you realize that many new files were not added
Hi,
SVN 1.5.4 is OK.
so any idea why new files were not added during rebase?
-Max
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
Hi,
I wanted to rebase my cws notes9 to m52, but it failed miserably.
What version of svn are you using, I ran into endless misery with
rebasing until I gave up on any recent svn version and rolled back to
the last 1.5.X release of 1.5.6
I'm using 1.5.4, which should be fine according to
Per Eriksson schrieb:
Per Eriksson skrev:
If you upgrade to 1.5.4 does it solve the problem?
well, rebase is already done, so it won't help for this time.
Any smart and easy way to find out all the added files and add them manuell?
-Max
Hi,
I wanted to rebase my cws notes9 to m52, but it failed miserably.
- EIS database was updated with a rebase to m47 instead of m52, can
someone fix that please?
- it seems that I'm missing all new files added somewhere along the
line, e.g. all the patches for redland, new containers and
Hi,
I wanted to rebase my cws notes9 to m52, but it failed miserably.
- EIS database was updated with a rebase to m47 instead of m52, can
someone fix that please?
- it seems that I'm missing all new files added somewhere along the
line, e.g. all the patches for redland, new containers and new
Hi,
looks like svn 1.6.x doesn't play nice with cws.pl, got a bug or two for
this lately. Now I'm wondering myself if it's required to make cws.pl
cope with all the 1.6 stuff, or is it good enough to check for 1.5.[56]
- which are known to work -
As I wrote earlier, I'm using 1.5.4, is this
Probably easiest (= quickest) way to fix is to checkout/upate your
tree to a state prior to the resync-attempt (can use date as
revision), create a patch against the master it was based on at that
time and then use that patch on the new master.
Thanks, will do...
-max
Hi,
I wanted to rebase my cws notes9 to m52, but it failed miserably.
- EIS database was updated with a rebase to m47 instead of m52, can
someone fix that please?
- it seems that I'm missing all new files added somewhere along the
line, e.g. all the patches for redland, new containers and new
Hi,
is there a difference for Solaris on opening files by just looking at
the file ending instead of MIME type?
If I try to open a text file with a different ending than odt for
example, it does not work. But the same thing works fine on e.g. Mac
Best,
Max
Hi,
for 3.1. The result is that OOo 3.1 will be the worst OOo ever from
our POV. It's so broken that it's impossible to use with our app and
our organization (that's over 9000 OOo installations) will have to
completely skip 3.1 and pray for 3.2 to be better.
can you name some of these
Hi,
There are more than the VCLTestTool tests. We have the performance tests
and the UNO API test and the convwatch test. All those are in the
responsibility of the developers. I think only convwatch is not mandatory.
it would be really nice to have all these test also in a cygwin
Hi,
The problem is a bit more complex. The testers and test script writers
do not have any time for writing new test cases for new functionality,
they do not have time to check fixed issues in master, they do not have
time to check code changes in a CWS as much as they should
Maybe it is an
Hi,
I'd prefer a button in EIS run all those tests, resulting in an
overview page, showing you red or green for both the overall status
and every single test. Only then, when you need to manually run a red
test to debug and fix it, you're required to do this on your console -
so, I think this
Hi,
Do you know, how often a CWS returns back to development because of
broken functionality, not fixed issues or process violation?
of course in regards to process violation, nothing would change. I am
talking about e.g crashing issues. If the developer tried it and it does
not crash
Hi,
Also, having seen a lot of misunderstandings (Oh! I though you meant
*this* button, but now I see you meant *that* one!), I think it is a
good idea that somebody who did not fix the issue verifies it. And the
CWS is the the best place for this verification, I'd say.
yes, this is true, so
Hi,
yes, this is true, so would you say we could skip the step from going
from verified to closed, doing this verification again?
I'd say this gives the least pain/loss.
by freeing time for other stuff for QA at the same time.
So maybe this idea can be discussed by the QA Leads as a
Hi Stefan
http://surveys.services.openoffice.org/surveys/index.php?sid=52123lang=en
when I enter my data, I get the message:
The email you used has already been registered
and no link is sent. Someone using my email adress or is the survey not
configured correctly?
Regards
max
Hi again,
and no link is sent. Someone using my email adress or is the survey not
configured correctly?
just after sending I got the other mail, so I guess you added all of us
already. Sorry for the noise
Best regards
Max
Hi again,
and no link is sent. Someone using my email adress or is the survey not
configured correctly?
just after sending I got the other mail, so I guess you added all of us
already. Sorry for the noise
Best regards
Max
Hi,
Please let me know what is the procedure to be a part of it and in what
way i can offer a helping hand.
I would start to look inside the wiki[1] how to get the source code from
svn[2] and how to build the thing on your platform.
Once that is up and running, I would try to dive into
Hi,
I was looking into the code of the Writer module and was wondering if there was
any intent behind the use of XUnoTunnel.
Does someone who is familiar with Writer code has any idea on this?
not sure if everyone of them is reading here as well, I would repost the
same thing on
Hi,
for Windows, see this how to compile and build the office:
http://wiki.services.openoffice.org/wiki/Building_OOo_with_Cygwin_on_Windows
After this worked out, I would try to start with easy bugs, probably
have look at issues with target OOoLater or the ones which interest you.
Here is
Hi,
Tora says he has VMware images for those builds. You can ask him for a
copy.
That sounds nice!
there are also Virtualbox Images with everything included for Ubuntu
http://wiki.services.openoffice.org/wiki/Prepared_Build_Images
Regards
Max
Hi,
had the same problem when building package type archive on linux.
the reason is simple: it happens if $TMP is not set; this causes the wrong
issue: i99106
thanks, this seems to be it
Regards
Max
-
To unsubscribe,
Hi Henning,
did you solve this problem? I now have the same issue building OOO310 m1
non-pro on Mac OS, 10.5, Intel.
Regards
Max
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail:
Hi Albert,
WITH_MOZILLA=NO
sorry, didn't follow the thread, but I am always building with
.. --disable-build-mozilla --disable-mozilla ..
as well as putting the precombiled bundle into moz folder
For Windows builds, this is the best ressource, with this it should work
for sure:
Hi Robert,
Robert Black schrieb:
I was thinking it might be a good time to write a tool that really closes
this gap in the development process. Something simple, like run deliver,
find out what files that it lists belong in the install directory, and copy
them there.
it is always the same
Hi,
just a note if someone will come across the same issue. Just building
svn 1.5.4 from source will not work(at least on MacOS), and you will get
an error message if you try to commit.
You need to configure with --without-sasl to get it to work.
Best regards
Max
Hi Nguyen,
Due to the big size,
new comers will find it very hard to get started with OOo.
Yes, it is true that it is not the easiest project to start with, but
there are a lot of other examples as well, such as smart tags, overline
of text, new notes and improved indexing in Writer,
Hi,
and keeping an easy access for contact information is basically a must. I
think it would be great if there were a program for OpenOffice that is much
like Microsoft Outlook.
Mozilla Tunderbird in combination with Lightning is probably what you
are looking for:
Hi,
I'm interested in helping with #5487[0].
this issue is already assigned to a developer: mod, who implemented the
Notes2 functionality for Writer, and he is surely already working on
that (if not yet finished!);
No, I did not start yet. As far as I know, there is some refactoring
Hi Mathias,
Perhaps we can use that to also fix the problem with certain Windows
editors: they turn line ends of files checked out with Cygwin into
garbage.
if you refer to the issue we had from time to time, I think the cause
was the wrong implementation of the cygwin cvs client and not of
Hi,
From my perspective with active code contributor a people described, who
constantly contribute code to the project under the general rules of the
project, [including SCA, cws-process]
Is this something we can agree on as being an active code contributor for
OpenOffice.org ?
+1
Best
Hi,
Do we have builds
that shows after 3.0 new features. Or this request is too early?
if interested, I could provide you with two different builds including
early implementation of:
* Changes - Comment similar to new notes in the margin
* reply to notes, similar to this mockup:
Hi,
Hopefully out of these discussions we can create a wiki document that
will prevent future windows devs from posting questions like this :)
http://wiki.services.openoffice.org/wiki/Building_OOo_with_Cygwin_on_Windows
Regards
Max
Hi,
You can do the following:
export LOCALINSTALLDIR=/path/to/desired/location
cd root source directory path/instsetoo_native/util
dmake openoffice_en-US PKGFORMAT=installed
then launch OOo from that installed location for your development.
As installation with just running setup.exe on
46 matches
Mail list logo
