Re: OpenOffice Windows builds

[Raphael Bircher]

Hi Andrea

Am .03.2017, 08:23 Uhr, schrieb Andrea Pescetti :


Raphael Bircher wrote:

So this means, the buildbot is completely unusable for the 4.1.4 branch.


We never used a buildbot for building releases.

That said, I'm not actually sure about the version of Visual Studio that  
can work for building on Windows. It would help if someone can tell  
Infra.
It's Visual Studio 08. But Infra is not willing to install such old  
version on a new VM. But to be honest, we have to move forward anyway. We  
can't stick with VS 2008 much longer.


The reason for the first build breaker is probably just, that the  
configure can't get the version number of the MSVC. I did some analyses,  
but to dig deeper, I have to install VS 2015 on my own computer.


Regards, Raphael




--
My introduction https://youtu.be/Ln4vly5sxYU

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: OpenOffice Windows builds

[Andrea Pescetti]

Raphael Bircher wrote:

So this means, the buildbot is completely unusable for the 4.1.4 branch.


We never used a buildbot for building releases.

That said, I'm not actually sure about the version of Visual Studio that 
can work for building on Windows. It would help if someone can tell Infra.


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: OpenOffice Windows builds

[Raphael Bircher]

Hi all

Am .03.2017, 04:19 Uhr, schrieb Chris Thistlethwaite :


Greetings,


Infra has been migrating VMs away from our aging systems in OSU and in  
the last week we've moved the buildbot for Windows 7 (bb-win7) to a new  
Windows 10 VM (bb-win10). I've been trying to get all the builds on that  
machine working and ran into some issues with aoo-win7 and aoo-w741k.  
Those two builds require Visual Stuido 2008 and some deprecated build  
tools. We'd like to get those updated to use Visual Studio 2015. Until  
the builds are updated, they are going to continue to fail.



Please refer to the build errors for details  
https://ci.apache.org/builders/aoo-win7/builds/657/steps/configure/logs/stdio


So this means, the buildbot is completely unusable for the 4.1.4 branch. I  
don't know if we use the BB for release. If yes, we have to search for an  
other solution :-(.


For the 4.2.0 it means, tat we have to switch to VisualStudio 2015. Before  
the BB is also completely unusable.


So we have actually just the Linux BB's and a Free BSD? That's no good  
news.


Regards, Raphael



--
My introduction https://youtu.be/Ln4vly5sxYU

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

OpenOffice Windows builds

[Chris Thistlethwaite]

Greetings,


Infra has been migrating VMs away from our aging systems in OSU and in the last 
week we've moved the buildbot for Windows 7 (bb-win7) to a new Windows 10 VM 
(bb-win10). I've been trying to get all the builds on that machine working and 
ran into some issues with aoo-win7 and aoo-w741k. Those two builds require 
Visual Stuido 2008 and some deprecated build tools. We'd like to get those 
updated to use Visual Studio 2015. Until the builds are updated, they are going 
to continue to fail.


Please refer to the build errors for details 
https://ci.apache.org/builders/aoo-win7/builds/657/steps/configure/logs/stdio


-Chris T.

#asfinfra

Re: gnu make port and the build.pl script

[Damjan Jovanovic]

Yes, sadly this is well known, and getting rid of build.pl is the long term
plan:

https://wiki.openoffice.org/wiki/Build_System_Analysis
https://wiki.openoffice.org/wiki/Build_System_Analysis:build.pl_versus_makefile

Which module breaks for you?

Damjan

On Wed, Feb 15, 2017 at 9:34 PM, Peter Kovacs  wrote:

> Hello,
>
> will we get rid of the build.pl script once the gnu make port is over?
>
> just asking, because I then I dont start debugging the script. I have
> realy strange issues.
>
> I run into an compile error with build --all.
>
> Then I switch into the module start again build --all and the module
> builds and delivers flawlessly.
>
> It is very strange behaviour.
>
> Included that the Script produces different results at each run, does not
> give me confidence.
>
> I would very much decomission this perl build tool all together.
>
>
> All the best
> Peter
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

FYI: Deleted some old SUN stuff

[Raphael Bircher]

Hi all,

I found some really old scripts refering to the EIS/CWS stuff. The scripts  
are no longer needed, so I deleted it.


Regards, Raphael

--
My introduction https://youtu.be/Ln4vly5sxYU

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: apple version

[Marcus]

Am 07.03.2017 um 00:00 schrieb Robert William Allen:

i have been trying to down loan your program for  my mac good air, but having 
problem, could you assist me in any manner.

thanks i am a newly so to speak so I’m somewhat ignorant about this all.


when you have questions and/or need hints to solve a problem, then 
please use our user forums:


https://forum.openoffice.org/

Thanks

Marcus


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Peter reports in ;)

[Peter Kovacs]

Hi Damjan,

Damjan Jovanovic  schrieb am Di., 7. März 2017, 01:44:

> On Mon, Mar 6, 2017 at 11:24 PM, Peter Kovacs  wrote:
>
> > Hello all,
> >
> >
> > I just wanted to give some feedback what I am doing.
> >
> > I am working on an alternate build Application, which could replace the
> > Perl one. I have some features in mind like auto document generation
> > (prio1) and signing the endprodukt (after I have the important local
> > functionality of build script.). What I dream of is to beeing able to
> > influence the build logic in an easy stable, sane way.
> >
> > I plan to support dmake and gnumake plus Ant.
> >
> >
> Please read the documentation on our previous attempts to improve the build
> system, so you don't repeat any of the same mistakes:
> https://wiki.openoffice.org/wiki/Build_Environment_Effort


Thanks this will help.

>
>
> Also how does this fit with plans to advance gbuild to replace both dmake
> and build.pl?
>
I have asked if the pl script gets relieved and did not see any answer. So
I assumed that the plan is replace dmake with gmake.
Maybe I missed the answer in this case, I am sorry.

I have made no thoughts if it fits to gbuild or not. However my first steps
are of information gathering steps. I want to see which module has what
Dependency depending on the build logic.
Then I would like to add a simple way to sign the result of the build. And
at last I want to be able to temper with the build script in a visualised
manner. (Since I dislike the need of the effort of defining the build
logic. I am lazy)

So you can think of the whole thing more kind of a Frontend idea. So yes I
can try to avoid any double work.

So is it important not to temper with gbuild strategy?  I don't want any
fights.


> >
> > All the best
> >
> > Peter
> >
>
-- 

Disclaimer: Diese Nachricht stammt aus einem Google Account. Ihre Antwort
wird in der Google Cloud Gespeichert und durch Google Algorythmen zwecks
werbeanaöysen gescannt. Es ist derzeit nicht auszuschließen das ihre
Nachricht auch durch einen NSA Mitarbeiter geprüft wird. Durch
kommunikation mit diesen Account stimmen Sie zu das ihre Mail, ihre
Kontaktdaten und die Termine die Sie mit mir vereinbaren online zu Google
konditionen in der Googlecloud gespeichert wird. Sollten sie dies nicht
wünschen kontaktieren sie mich bitte Umgehend um z.B. alternativen zu
verhandeln.

Re: Access to the OpenOffice Buildbot boxes

[Pedro Giffuni]

Hello;

Just IMHO.. it would be very valuable for our build experts to take a 
look at travis-ci (through github) and getting Coverity back up.


Pedro.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org