On Fri, 11 Jun 2010 18:55:59 +0200
Michael Stahl michael.st...@sun.com wrote:
We did attempt to create non-recursive makefiles for CMake, and
they are less recursive than they once were. However, we found
it impossible to handle implicit dependencies of generated source
files without
Hi list,
playing a bit with hg I found it quite it quite easy to create
extensions. First experiments resulted in the branchmirror extension
which lets you update a set of branch repos (specified by regular
expression) with one command, using not too much bandwidth. You will
find the extension
On Thu, 01 Apr 2010 16:40:11 -0400
Terrence Enger ten...@iseries-guru.com wrote:
Greetings,
What does it take to use, for example, the DBG_ASSERT function defined
in debug.hxx? I have poked around on the wiki without success.
I have added enough #include lines to get the file to compile,
On Wed, 31 Mar 2010 12:52:18 +0200
Rene Engelhard r...@openoffice.org wrote:
a stronger community means actively involving hughe parts of the
community. which you don't. there's still many sun-internal decision
just posed to the community as a fact everyxone has to live with.
Who is you here?
On Wed, 31 Mar 2010 13:52:11 +0200
Rene Engelhard r...@openoffice.org wrote:
How is patch -pX lack of resources? How is telling people how they
need to change stuff to get a patch (which works for everyone else
except Sun and is needed there) finalized to get integrated a resource
problem?
On Wed, 31 Mar 2010 22:10:54 +0200
Sophie sgautier@free.fr wrote:
The unbalanced was between the mail and the disclaimer on the wiki.
Sorry that I didn't explain myself better adding confusion on
something I found important. (BTW I never read Eric Bachard mails
since almost 2 years or
Hi List,
the Wiki Cleanup has been almost completed. There are just seven pages
left in:
http://wiki.services.openoffice.org/wiki/Special:UncategorizedPages
If you can remove those, please do so. Also note the new Guidelines at:
On Sat, 20 Mar 2010 20:45:07 -0400
Rémy Roy remy...@remyroy.com wrote:
I'm using Ubuntu 9.10 with the DEV300 branch. I've having some
troubles building with the PKGFORMAT=installed option. I can build
successfully but in the end my LOCALINSTALLDIR only contains an
openoffice.org directory. It
On Wed, 10 Mar 2010 14:57:12 +0100
Thorsten Behrens t...@openoffice.org wrote:
sure, I buy those. Would then be worthwhile to re-def the types you
listed in terms of their C/std:: counterparts. Can do that.
sal_sChar is indeed unused, sal_uChar not so much (but there should
be a trivial 1:1
On Wed, 10 Mar 2010 15:56:37 +0100
Stephan Bergmann stephan.bergm...@sun.com wrote:
Re wincing at obviousness of matching range: How is that any
different for plain int (with INT_MIN--INT_MAX range) vs., say,
sal_Int32 (with SAL_MIN_INT32--SAL_MAX_INT32 range)?
Because our interfaces consist
On Tue, 16 Feb 2010 00:21:36 +0100
Lukasz Szczygielek lszczygie...@gmail.com wrote:
I have a Linux Fedora 12 64 bit. After a configure and bootstrap and
source LinuxX86-64Env.Set.sh I discovered the problem.
On the page I read that after this steps I should make:
dmake
but then I had:
On Tue, 16 Feb 2010 11:43:41 +0100
Stephan Bergmann stephan.bergm...@sun.com wrote:
On 02/16/10 11:27, bjoern michaelsen - Sun Microsystems - Hamburg
Germany wrote:
For now I just changed the description in the Building Guide to do:
cd instsetoo_native build --all
which is what most
On Fri, 12 Feb 2010 10:30:59 +0200
Rich ric...@nakts.net wrote:
speaking as a user here, not a coder - if software can continue with
operating, it should. yes, it should warn me, but it should run as
long as possible, either allowing me to save the document, copy data
out of it or whatever.
On Fri, 12 Feb 2010 13:12:08 +0200
Rich ric...@nakts.net wrote:
(non-product, i assume ?)
ahem, yes.
if the plan is to use these non-product builds for
developers only, then i stand corrected and have no opinion on the
issue :)
Thats the plan as I understood Stephan (didnt he clarify that
On Fri, 12 Feb 2010 12:43:29 +0100
Malte Timmermann malte.timmerm...@sun.com wrote:
-1 for discussing here whether or not QA should use non-pros, because
it IMHO has absolutely no influence on how assertions should behave.
And if you want QA to use non-pros, they for sure would give up quite
On Fri, 12 Feb 2010 12:34:33 +0100
Christian Lippka christian.lip...@sun.com wrote:
So you see OSL_ASSERTS from your code, but you never see asserts from
code that your code uses. Or things you break with your code in other
places.
Im covering very broad ranges of modules with DEBUG=true, not
On Fri, 12 Feb 2010 13:10:01 +0100
bjoern michaelsen - Sun Microsystems - Hamburg Germany
bjoern.michael...@sun.com wrote:
Current situation:
- assertions might be anything from a informal I didnt expect this
external data to a critical internal state corrupt
Desired situation
On Fri, 12 Feb 2010 14:38:18 +0100
Philipp Lohmann philipp.lohm...@sun.com wrote:
The obvious optimization for that process would be leaving things as
they are and introduce an OSL_ASSERT_ABORT for those who really want
that.
still one would need:
- to get rid of DBG_ASSERT, because it makes
On Fri, 12 Feb 2010 17:31:18 +0100
Christian Lippka christian.lip...@sun.com wrote:
If we make the office crash in non pro than there will be never a
chance to get the qa to work on non pro again.
Depends. If we make the master crash on tests in every milestone, sure.
As said before an aborting
On Tue, 09 Feb 2010 17:12:23 +0100
Svatopluk Bláha svatopluk.bl...@quick.cz wrote:
Now, with which conditions I can obtain access to source code?
Hi Svatopluk,
see
http://wiki.services.openoffice.org/wiki/Documentation/Building_Guide
for getting started.
Best Regards,
Bjoern Michaelsen
On Mon, 14 Dec 2009 15:06:45 +0100
Stephan Bergmann stephan.bergm...@sun.com wrote:
Hi all,
I just embarked on a new project, namely to clean up and consolidate
the various test frameworks and corresponding tests available in the
OOo build environment.
...
Comments on all of this are, of
Hi Lists,
The Build Environment Effort Team(1) has implemented a proof-of-concept
on how to build OpenOffice.org using GNU make. The rationale for this
is explained in this blogpost on GullFOSS:
http://blogs.sun.com/GullFOSS/entry/building_openoffice_org_with_gnu
The Build Environment Effort
On Wed, 02 Dec 2009 09:48:21 +0800
Arron Xiao arron.x...@gmail.com wrote:
I intend to build openoffice source code using VS 2008 C++,
However, I cannot find any resource about it on your web site. Can
you tell me relational link about it or give me some suggestion?
May I ask where you
On Tue, 17 Nov 2009 19:56:42 -0800 (PST)
Ranjeet Jaiswal jaisranj...@yahoo.com wrote:
Hallo sir, I am an engineering graduate from university of Allahabad.
Interested to joining openoffice.org
Please tell me how I can start with you.
Welcome Ranjeet,
it depends on what tasks you want to
On Tue, 17 Nov 2009 10:32:21 +0100
Frank Schoenheit, Sun Microsystems Germany frank.schoenh...@sun.com
wrote:
At least we'd need a makefile-clause for setting a default, /me
thinks.
For instance, for libs exporting the usual three UNO entry points
component_*, I would like to have a make
On Sat, 14 Nov 2009 19:17:40 -0500
Albretch Mueller lbrt...@gmail.com wrote:
I am trying to run config like that (from within a script)
but I an stumbling on some missing perl modules:
[...]
checking for perl... /usr/bin/perl
checking the Perl version... checked (perl 5)
checking for
Hi List,
again some stuff from the Build Environment Effort(1). While figuring
out the way we build libraries with the OpenOffice.org build system it
became apparent that we seem to have way to many redundant ways to set
the visibility of functions. From the top of my head:
- map files
-
Hi List,
While working on the Build Environment Effort(1), we stumbled over the
implicit dependency of all modules generating resource files on
default_images. The resource compiler digs into the default_images
directory for the files specified in the *.src/*.hrc files. However,
since there is no
On Wed, 11 Nov 2009 14:17:04 +0100
Juergen Schmidt juergen.schm...@sun.com wrote:
this can be seen more as a reminder to make use of the IDL tags, see
http://wiki.services.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension
for detailed info.
And while we at it, please also use:
On Tue, 27 Oct 2009 13:04:50 +0100
Christian Lohmaier cl...@openoffice.org wrote:
Pushing the other ones doesn't do any harm besides wasting bandwidth
on a push.
Thats not entirely true. This is the way there is harm by adding
superficial heads to an outgoing repo:
- RelEng expects a cws repo
On Tue, 27 Oct 2009 14:22:31 +0100
Jens-Heiner Rechtien jens-heiner.recht...@sun.com wrote:
Actually, I'm thinking about a hook which will prevent the creation
of new heads on the outgoing repositories. Not yet implemented,
though.
This time, unlike last time, I am against such a hook. ;-) If
On Tue, 27 Oct 2009 14:25:40 +0100
Jens-Heiner Rechtien jens-heiner.recht...@sun.com wrote:
Regarding your idea with reorganizing the pages. I like that :-).
Maybe we could just forward the old pages to the new ones (only the
OOo and Mercurial one, no need to bother with rest).
All pages
Hi List,
I tried to add a bit of structure to to the categories used on the
Openoffice.org Wiki.
I hope the most important ones are now a direct or indirect subcategory
of the MainIndex at:
http://wiki.services.openoffice.org/wiki/Category:MainIndex
Please check, if your category has found a
On Mon, 26 Oct 2009 13:38:44 +0100
Juergen Schmidt juergen.schm...@sun.com wrote:
it seems to be a good start but probably some more main categories
are necessary. But then the question is if we need it at all or if a
reworked main page would help to navigate in and through the wiki.
Without
On Mon, 26 Oct 2009 14:59:28 +0100
Juergen Schmidt juergen.schm...@sun.com wrote:
bjoern michaelsen - Sun Microsystems - Hamburg Germany wrote:
ah i see, but Marketing is so important from my point of view that i
wouldn't have searched under Project. Well but that is my personal
problem
Jens-Heiner Rechtien wrote:
Hi,
I wouldn't call for a complete ban but it looks like one has to be extra
careful. Restructuring should be done in CWS which lives only a very
short time. Best, say, opened on one milestone and integrated in the
next (as first CWS) this would minimize the
Frank Schönheit - Sun Microsystems Germany wrote:
Perhaps a postprocess hook which sends mails to EIS, keeping track of
moved files, and issueing warnings upon integration when some change is
about to be lost?
I fear this is not possible in post-commit, as the info that something
was a move
On 10/20/08 15:05, Thorsten Behrens wrote:
I see. But this surely doesn't apply to all-new files, no?
No (other than that you cannot checkout a file that exists in a working
copy using a different case, but that is to be expected with
caseinsensitive filesystems).
(is there an svn bug filed
Hi list,
since we now have subversion, we might as well use the new features it
provides. I wrote a precommit hook on the weekend that does some
precommit sanity checks:
- It rejects commits changing files in a cws and outside of it (thus
hopefully preventing some accidental commits to a
On 10/20/08 12:56, Frank Schönheit - Sun Microsystems Germany wrote:
... modules ...
Not sure this is needed. AFAIK it is (at least in CVS times it was)
necessary to do other things for adding a new module (announcement to
releng etc.), so just preventing the commit doesn't really solve a
On 10/20/08 12:51, Rene Engelhard wrote:
How should that be possible when you svn switch a complete tree to a cws
(which you should do)?
There's no need for any checks at all, if everybody does what he should
do ;-).
There's no modules anymore but one big tree. That check imho is moot.
On 10/20/08 15:08, Frank Schönheit - Sun Microsystems Germany wrote:
See issue 95199 for my currently prepared (and already implemented)
solution, though a post-commit hook also sounds interesting.
I just tried to add an svn:ignored dir. That works.
If someone does a svn diff in a module, and
On 10/20/08 17:39, Philipp Lohmann wrote:
Hi,
Jens-Heiner Rechtien wrote:
I somehow don't like tying SCM functionality to commit messages, but
that's may be just me.
And should we enforce policy (like tabs vs spaces etc) via the SCM tool?
is there another point where we could actually
On 10/20/08 17:10, Jens-Heiner Rechtien wrote:
there was no need for crucifying yourself, server side we are python
only. Actually we have no perl bindings installed.
If I only had known that before. I like and know Python a lot better.
I think we need to be a bit carefull with pre-commit
On 10/16/08 15:41, Jens-Heiner Rechtien wrote:
[...]
There is another reason to use svn:ignore set in the repo:
There is no way to check if all of us lazy devs really set the stuff in
our local svn config.
Having svn:ignore on the output tree dirs should make it extra hard for
one lazy/tired
On 10/16/08 11:00, Malte Timmermann wrote:
In short: Can we please add the platform-dependent output tree names
as svn:ignore property to all modules?
+1
+1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
On 10/06/08 09:57, Caolán McNamara wrote:
And subversion (like cvs) has a precommit hook that can e.g. reject
files with tabs in them. e.g.
http://wordaligned.org/articles/a-subversion-pre-commit-hook
+1
I would really appreciate such a hook, I just didnt dare to propose this
yet.
Have
47 matches
Mail list logo
