At first glance it looks like it wants what we want, but on second
glance it describes the removal of UNO from OpenOffice, and divide the
Monolithic package we have into 3 packages along the layers. I think it
is what Libre Office has already done. But for sure it will give hints
on the issues
On Fri, Oct 5, 2018 at 8:45 PM George Karalis wrote:
>
> Hello everyone,
>
>
Hi, welcome :)
> Since am new to the project and working on understanding the build process
> this past
> week, I agree with Damjan that the build system needs that overhaul. I
> also agree that
> a MSVC upgrade and a
Those links are in the wrong category then. They refer to OOo not the ODF
Toolkit.
On Sat, Oct 6, 2018 at 3:54 AM Dave Fisher wrote:
>
>
> Sent from my iPhone
>
> > On Oct 5, 2018, at 6:37 PM, Damjan Jovanovic wrote:
> >
> > The links you are looking for are:
> >
Sent from my iPhone
> On Oct 5, 2018, at 6:37 PM, Damjan Jovanovic wrote:
>
> The links you are looking for are:
> https://wiki.openoffice.org/wiki/ODF_Toolkit/Efforts/OOo_without_URE
> https://wiki.openoffice.org/wiki/ODF_Toolkit/Efforts/Three-Layer_OOo
ODF Toolkit is still in the
The links you are looking for are:
https://wiki.openoffice.org/wiki/ODF_Toolkit/Efforts/OOo_without_URE
https://wiki.openoffice.org/wiki/ODF_Toolkit/Efforts/Three-Layer_OOo
Let's leave the split for now. It's not going to help us directly.
On Fri, Oct 5, 2018 at 11:59 PM Peter Kovacs wrote:
>
Hi all,
I am a bit skeptical about the 2 Layer approach. OpenOffice has been
designed in a 3 Layer Architecture. This can be seen here.
https://wiki.openoffice.org/wiki/File:ArchOverview.jpg
As this documentation states the Lower Layer does not only consists of
the UNO Group but also of
Hello everyone,
Since am new to the project and working on understanding the build process this
past
week, I agree with Damjan that the build system needs that overhaul. I also
agree that
a MSVC upgrade and a 64-bit windows build, is of high priority. Changing the
build
system will take
The split wouldn't help us with newer MSVC as such.
What would help us there a lot, is SCons, as SCons supports many MSVC
versions already, including MSVC 2017. It would be so wonderful if we were
on SCons already: not only would we build with a wider range of MSVC
versions, but we would need
Hi Damjan,
I o not understand the MSVC part. If we separate UNO it's own world.
(Independent of the Idea to spin it of into its own project)
will the update of the MSVC be easier?
All the best
Peter
On 10/5/18 10:15 AM, Damjan Jovanovic wrote:
Hi
I now have a few other ideas regarding
Hi
I now have a few other ideas regarding the building story.
The gbuild migration has been extraordinarily long and painful. Sadly I've
had to learn so much about gbuild, and implement so many new features in it
(symlinks, UNO IDL, Ant, bison, flex, now assembly...), that I am getting
good at
10 matches
Mail list logo
