> -Original Message-
> From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
> Sent: Saturday, February 6, 2016 11:42
> To: dev@openoffice.apache.org
> Subject: RE: Thoughts on a new build system for AOO
>
> I think there are pathname parsing issues in MingW, although I don't
>
On 02/05/2016 10:32 AM, Damjan Jovanovic wrote:
> Hi
>
> With the recent buildbot saga and Patricia's Windows building nightmare, a
> number of serious issues were highlighted which got me thinking about how
> our build system could be improved.
>
> The problems with building AOO were
Thanks Stephen,
I've been looking at interactionhandler.cxx today and I believe the best way
forward is to take the uui source implementation as a base and then
refactor, replacing all of the XDialog-derived classes with classes that
query for the same information through an interface passed in
Some ideas:
(1) A panel or talk comparing Flex, Cordova, and OpenOffice. There are many
levels to compare. Technology. All three are "code/community" contributions to
the ASF from major companies: Adobe, Oracle and IBM. Cordova is still a
corporate product as Phonegap. Each has "pushed" the
Thanks Fernando,
GYP does look interesting, at a high level. I notice it is hosted at Google
and not completely spun out as an open-source project. Still ...
There is an interesting mention of GYP use of Ninja in hybrid projects, with an
apparently-extraordinary improvement in [incremental]
I think there are pathname parsing issues in MingW, although I don't think
anything is as contorted as with cygWin. These usually arise because of the
shell being used, that then leads them to rewrite command lines when calling a
native utility. It seems that is the top of the slippery slope.
It is now time that folks start looking at right-sized projects that could be
mentored and made available to students participating in Google Summer of Code
(GSoC).
There is also a discussion, as part of community development, on mentoring
generally and finding ways to make opportunities for
Hi again;
Some answers, although this all classifies as "musings" ;).
To damjan:
> AFAIK all make utilities suffer from the recursive make problem, the
> only way gbuild didn't is by using the eval feature in GNU make, and
> it still left a lot to be desired.
Concerning FreeBSD's make,
I installed the Open Office 4.1 thinking I was doing a good thing ---
just adding a processing program that was cheaper than Word. Now
I regret it and I am more than angry. I am furious. Before loading
Open Office 4.1, I had and was using Star Writer (from Sun). I was
using that particular
I agree that an IDE is important - for development. Building the whole of
AOO in an IDE seems impractical and awkward. Eclipse CDT already works well
as an IDE on all platforms (
https://wiki.openoffice.org/wiki/OpenOffice_and_Eclipse) and doesn't need
any special project files generated; with
The linked page includes a reference for a Video on migrating a large
C++ codebase, and a training course whose topics include creating
multiple versions for multiple platforms. That all looks encouraging.
On 2/6/2016 4:11 AM, Carl Marcum wrote:
Hi Damjan,
Have you looked at Gradle for C/C++
On 2/6/16, Fernando Cassia wrote:
>
> https://en.m.wikipedia.org/wiki/GYP_(software)
>
> BSD license, written in Python, used by Chrpmium so Windows should be
> supported too.
>
> If it doesn't help, sorry about that... just wanted to add my $0.02
> FC
I meant Chromium. Sorry
Hi Damjan,
Have you looked at Gradle for C/C++ ?
I don't have experience with it for C/C++or codebases of this size, but
using it for Java and Groovy it is pretty simple and powerful.
It's also Apache licensed :)
[1] http://gradle.org/getting-started-native/
Thanks,
Carl
On 2/5/16, Pedro Giffuni wrote:
> Hi Patricia .. good point about IDE's.
>
> We have a dilemma here:
>
> On one side ~80% of our users are Windows-based so it would certainly
> be ideal to use an environment where we keep both our users and our
> developers in sync. Unfortunately
14 matches
Mail list logo