Re: Windows build broken.

On 13.5.2024 11.09, Regis Perdreau wrote: Hi, I follow carefully again windows build instruction wiki, but the windows build does not work again. Could you we expect that it will work for everybody not only on developper's computer ? (i know it's sometimes difficult, but if we

Windows build broken.

Hi, I follow carefully again windows build instruction wiki, but the windows build does not work again. Could you we expect that it will work for everybody not only on developper's computer ? (i know it's sometimes difficult, but if we could have some news, it's better) Regards, Régis Perdreau

Re: Seeking help with Windows build using v7.6.1.1

Norton on this machine, so I am aborting this Windows build effort. May try a Linux build to see if I have better luck... On Mon, Sep 4, 2023 at 4:03 PM Noel Grandin wrote: > > I am guessing either > > (a) anti-virus tool > > or > > (b) you are using a different git client and it has munged some line > endings > >

Re: Seeking help with Windows build using v7.6.1.1

I am guessing either (a) anti-virus tool or (b) you are using a different git client and it has munged some line endings

Re: Seeking help with Windows build using v7.6.1.1

On 3.9.2023 20.09, Andrew Richardson wrote: Hello all Firstimer here, trying to set up initial Windows 11 build environment. I have followed the LODE instructions, using Visual Studio 2022 Community edition. I have set my 'dev/core' build tree to the 'libreoffice-7.6.1.1' tag using git checko

Seeking help with Windows build using v7.6.1.1

Hello all Firstimer here, trying to set up initial Windows 11 build environment. I have followed the LODE instructions, using Visual Studio 2022 Community edition. I have set my 'dev/core' build tree to the 'libreoffice-7.6.1.1' tag using git checkout. I am seeing a few issues when doing a clean b

Re: Windows build gets stuck, if parallelism greater than 1

Hi *, On Sat, Nov 20, 2021 at 6:44 PM Ilmari Lauhakangas wrote: > On 20.11.2021 12.03, Ilmari Lauhakangas wrote: > > My mentee is having an issue, where plain make gets stuck in > > It turns out parallel building at full steam works fine on C: drive, so > the problem was having Cygwin in E: drive

Re: Windows build gets stuck, if parallelism greater than 1

On 20.11.2021 12.03, Ilmari Lauhakangas wrote: My mentee is having an issue, where plain make gets stuck in [build ECH] CustomTarget/instsetoo_native/setup/version.ini or [build MOD] instsetoo_native if parallelism is 2 or more. Default would be "-j 8" on his machine. He has 16GB RAM availab

Re: Windows build gets stuck, if parallelism greater than 1

On Sat, 20 Nov 2021 at 13:05, Luboš Luňák wrote: > > But first I'd check if this isn't the recent cygwin problem that was > causing > make getting stuck. > > possibly we should add a configure check for that, it is biting several people

Re: Windows build gets stuck, if parallelism greater than 1

On Saturday 20 of November 2021, Ilmari Lauhakangas wrote: > My mentee is having an issue, where plain make gets stuck in > > [build ECH] CustomTarget/instsetoo_native/setup/version.ini > > or > > [build MOD] instsetoo_native > > if parallelism is 2 or more. Default would be "-j 8" on his machine.

Windows build gets stuck, if parallelism greater than 1

My mentee is having an issue, where plain make gets stuck in [build ECH] CustomTarget/instsetoo_native/setup/version.ini or [build MOD] instsetoo_native if parallelism is 2 or more. Default would be "-j 8" on his machine. He has 16GB RAM available. Windows is on bare metal. Any tips for trou

Re: Windows build problem, access denied

Hi Ilmari Recently I had the opportunity to meet the error in your thread starting message, and it was not solved by using the sn tool as documented (but interestingly on another machine it helped). I added a new section about how I solved it: https://wiki.documentfoundation.org/Development/Buil

Re: Windows build problem, access denied

On 11.10.2021 9.36, Miklos Vajna wrote: I have a note from 2020-05 that some kind of cli_ure access denied problem I had was solved by following the instructions from . Give it a try, perhaps it'll help in your case a

Re: Windows build problem, access denied

Hi Ilmari, I have a note from 2020-05 that some kind of cli_ure access denied problem I had was solved by following the instructions from . Give it a try, perhaps it'll help in your case as well. Regards, Miklos

Windows build problem, access denied

Someone I'm mentoring has this build issue on Windows 10. Any ideas? He also had this other permission issue, fixed with the reg add command: https://lists.freedesktop.org/archives/libreoffice/2020-July/085516.html "Käyttö estetty" is access denied in Finnish. error: .NET exception occurred:

Windows build problem: fatal error LNK1181: cannot open input file 'wsock32.lib'

Someone I am onboarding is having this problem. Windows 10 SDK is installed. What concrete steps could be done to remedy the situation? Ilmari $ /opt/lo/bin/make vertbose=t C:/cygwin/opt/lo/bin/make -j 12 -rs -f C:/sources/libo-core/Makefile.gbuild bui ld [build UPK] libassuan-2.5.3.tar.bz2

Re: current master windows build break: sw/source/core/crsr/bookmrk.cxx(721): error C2039: "isMobilePhone" ist kein Member von "comphelper::LibreOfficeKit".

all clear, after another git pull it worked Am 10.05.2020 um 09:15 schrieb Oliver Brinzing: Hi, I tried to build current master but build breaks: Microsoft Visual Studio Professional 2019 - Version 16.5.4 [...] [CXX] sw/source/core/crsr/crstrvl1.cxx [CXX] sw/source/core/crsr/DateFormFieldButt

current master windows build break: sw/source/core/crsr/bookmrk.cxx(721): error C2039: "isMobilePhone" ist kein Member von "comphelper::LibreOfficeKit".

Hi, I tried to build current master but build breaks: Microsoft Visual Studio Professional 2019 - Version 16.5.4 [...] [CXX] sw/source/core/crsr/crstrvl1.cxx [CXX] sw/source/core/crsr/DateFormFieldButton.cxx [CXX] sw/source/core/crsr/DropDownFormFieldButton.cxx [CXX] sw/source/core/crsr/findatt

Re: current master windows build break: ninja: build stopped: subcommand failed.

Hi, I just made a new build and noticed that it was working again: Version: 7.0.0.0.alpha0+ (x64) Build ID: 179bcf810809efb8ec1b4658e5f30d3a75513315 CPU threads: 12; OS: Windows 10.0 Build 18363; UI render: Skia/Vulkan; VCL: win; Locale: de-DE (de_DE); UI-Language: en-US Calc: threaded Regards

Re: current master windows build break: ninja: build stopped: subcommand failed.

Noel Grandin wrote: > At this point I recommend we simply give up and revert the ninja patch, it > is not worth it. > Seconded. I'm still none the wiser why my win32 build crashes python here (and don't even see it on manual builds). Cheers, -- Thorsten signature.asc Description: PGP signature

Re: current master windows build break: ninja: build stopped: subcommand failed.

On 27/03/2020 09:45, Noel Grandin wrote: At this point I recommend we simply give up and revert the ninja patch, it is not worth it. I sympathize with that, for a different reason. I have spent enough time now to fix external/nss' new gyp+ninja build for my needs on Linux and Windows. But w

Re: current master windows build break: ninja: build stopped: subcommand failed.

I have now worked through finding 3 path-related bugs and fixing 2 of them, and there are still more, and I've spent 4 days worth of spare time on it. At this point I recommend we simply give up and revert the ninja patch, it is not worth it. ___ LibreOf

Re: current master windows build break: ninja: build stopped: subcommand failed.

On Thursday 26 of March 2020, Oliver Brinzing wrote: > Hi > > Is there anything I could do to help analyze the problem? > Unfortunately, my knowledge of the build system is limited... Please post the output of 'make Module_nss'. -- Luboš Luňák l.lu...@collabora.com ___

Re: current master windows build break: ninja: build stopped: subcommand failed.

Hi Is there anything I could do to help analyze the problem? Unfortunately, my knowledge of the build system is limited... Best Regards Oliver Am 25.03.2020 um 12:22 schrieb Luboš Luňák: On Wednesday 25 of March 2020, Thorsten Behrens wrote: Luboš Luňák wrote: There's no actual error messa

Re: current master windows build break: ninja: build stopped: subcommand failed.

Hi Is there anything I could do to help analyze the problem? Unfortunately, my knowledge of the build system is limited... Best Regards Oliver Am 25.03.2020 um 12:22 schrieb Luboš Luňák: On Wednesday 25 of March 2020, Thorsten Behrens wrote: Luboš Luňák wrote: There's no actual error messa

Re: current master windows build break: ninja: build stopped: subcommand failed.

On Wednesday 25 of March 2020, Thorsten Behrens wrote: > Luboš Luňák wrote: > > There's no actual error message in this short output. > > Possibly the same error: > > https://paste.debian.net/1136485/ No. The original problem is ninja build failing for whatever reason. In your case python crash

Re: current master windows build break: ninja: build stopped: subcommand failed.

Luboš Luňák wrote: > There's no actual error message in this short output. > Possibly the same error: https://paste.debian.net/1136485/ Any further diagnostics needed? The above fails consistently on win32. Cheers, -- Thorsten signature.asc Description: PGP signature ___

Re: current master windows build break: ninja: build stopped: subcommand failed.

On Tuesday 24 of March 2020, Oliver Brinzing wrote: > Hi, > > I tried to build current master but build breaks always (even after a clean > and new configure - see below) with: > > [...] > Hinweis: Einlesen der Datei: C:\Program Files (x86)\Microsoft Visual > Studio\2019\Professional\VC\Tools\MSV

Re: current master windows build break: ninja: build stopped: subcommand failed.

Same problem here. Something in ninja or gyp does not like it when you build from anything other than the C: drive. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice

current master windows build break: ninja: build stopped: subcommand failed.

or explicit CFLAGS... no checking for explicit CXXFLAGS... no checking for explicit OBJCFLAGS... no checking for explicit OBJCXXFLAGS... no checking for explicit LDFLAGS... no checking whether build target is Release Build... no checking whether to sign windows build... no checking for gawk... gawk ch

Re: Proposal to update default Windows build chain to Visual Studio 2019

On 13/02/2020 11:12, Noel Grandin wrote: I propose that we updated our Windows builders to use VS2019 and make that our new preferred baseline. Any specific version of VS 2019? Especially regarding C++ conformance, they typically ship improvements in minor updates (though it doesn't look lik

Proposal to update default Windows build chain to Visual Studio 2019

/build tools: (*) AddressSanitizer support for projects compiled with MSVC on Windows. (*) Build throughput improvements, including the way the linker handles File I/O, and link time in PDB type merging and creation (*) Lots of C++ conformance fixes and improvements, including some C++20

Re: windows: build issue

hi Dmitriy, On 24.01.19 08:59, Dmitriy Shilin wrote: Morning guys! I've been trying to rebuild all modules from the latest master but have the following build error: c:\sources\libreoffice\workdir\unpackedtarball\lcms2\include\lcms2.h(67): fatal error C1083: Cannot open include file: 'stdio.h

Re: Windows Build - LNK1651 error in external/nss

Hi Olivier, You got the same as me http://document-foundation-mail-archive.969070.n3.nabble.com/fatal-error-LNK1561-on-nss-Visual-Studio-2017-td4256601.html There's just a typo, it's 1561, not 1651 Julien -- Sent from: http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.

Windows Build - LNK1651 error in external/nss

Hi My build breaks with the following message: LINK : fatal error LNK1561: pontos de entrada devem ser definidos make[3]: *** [../../coreconf/rules.mk:243: out/util_gtest.exe] Error 2 make[3]: Leaving directory 'C:/cygwin/home/olivier/lode/dev/core/workdir/UnpackedTarball/nss/nss/gtests/util_gtes

windows: build issue

Morning guys! I've been trying to rebuild all modules from the latest master but have the following build error: ``` [PKS] UIConfig/modules/simpress Microsoft (R) Build Engine version 15.9.21+g9802d43bc3 for .NET Framework Copyright (C) Microsoft Corporation. All rights reserved. Build started 1

Re: Windows build failure - C1076 / C1060

seems to be resolved, was able to build: Version: 6.3.0.0.alpha0+ (x64) Build ID: 21b81b07b01e4482a80ced8dcdf48c480031c3c8 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; Locale: de-DE (de_DE); UI-Language: en-US Calc: threaded Am 15.12.2018 um 11:18 schrieb Oliver Brinzing: Hi

Windows build failure - C1076 / C1060

Hi, trying to build master today on windows (vs 2017 15.9.3) breaks with: [CXX] sc/source/ui/view/reffact.cxx [CXX] sc/source/ui/view/scextopt.cxx [CXX] sc/source/ui/view/select.cxx [CXX] sc/source/ui/view/selectionstate.cxx [CXX] sc/source/ui/view/spelldialog.cxx [CXX] sc/source/ui/view/spellen

Re: Windows build failure - C2131: expression did not evaluate to a constant

On 04/12/2018 14:18, Kaganski Mike wrote: Reported that to https://developercommunity.visualstudio.com/content/problem/398218/c2131-error-with-stdarray-and-stdmake-integer-sequ.html. As noted there, I have discovered the code to succeed if I replace 256 to any number up to 234. So lets revert

Re: Windows build failure - C2131: expression did not evaluate to a constant

On 04.12.2018 14:18, Kaganski Mike wrote: > On 04.12.2018 14:17, Kaganski Mike wrote: >> >> I have just pulled, and I confirm this with 64-bit build, with VS >> version 15.9.3. >> > > I mean, I confirm that with my version of compiler, the problem is > reproducible. > _

Re: Windows build failure - C2131: expression did not evaluate to a constant

On 04.12.2018 14:17, Kaganski Mike wrote: > > I have just pulled, and I confirm this with 64-bit build, with VS > version 15.9.3. > I mean, I confirm that with my version of compiler, the problem is reproducible. ___ LibreOffice mailing list LibreOffi

Re: Windows build failure - C2131: expression did not evaluate to a constant

On 04.12.2018 10:37, Stephan Bergmann wrote: > > Our recently-bumped MSVC baseline is Visual Studio 2017 version 15.7 > (the "version 15.7" suffix is important, there are many different > releases of Visual Studio 2017, with ever-increasing C++ standard > compliance).  That should be enforced b

Re: Windows build failure - C2131: expression did not evaluate to a constant

On 04/12/2018 02:54, Luke Benes wrote: After commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=644188bf7f3a Compute (un-)premultiply_table at compile time I'm seeing the following build failure on Windows 32-bit release build: D:/core/vcl/source/bitmap/BitmapTools.cxx(1078):

Re: Windows build failure - C2131: expression did not evaluate to a constant

On 04.12.2018 9:30, Noel Grandin wrote: > > >> I'm seeing the following build failure on Windows 32-bit release build: >> D:/core/vcl/source/bitmap/BitmapTools.cxx(1078): error C2131: >> expression did not evaluate to a constant >> D:/core/vcl/source/bitmap/BitmapTools.cxx(1097): error C2131: >

Re: Windows build failure - C2131: expression did not evaluate to a constant

I'm seeing the following build failure on Windows 32-bit release build: D:/core/vcl/source/bitmap/BitmapTools.cxx(1078): error C2131: expression did not evaluate to a constant D:/core/vcl/source/bitmap/BitmapTools.cxx(1097): error C2131: expression did not evaluate to a constant make[1]: ***

Windows build failure - C2131: expression did not evaluate to a constant

After commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=644188bf7f3a Compute (un-)premultiply_table at compile time I'm seeing the following build failure on Windows 32-bit release build: D:/core/vcl/source/bitmap/BitmapTools.cxx(1078): error C2131: expression did not evaluate

Re: 64-bit Windows build failure after MSVC Update

On 20/08/18 21:01, Luke Benes wrote: After I updated from MSVC 15.7.6 to 15.8.1, I started seeing the following build failure: [build CXX] sc/source/ui/docshell/docsh8.cxx c:\core\sc\source\ui\docshell\docsh8.cxx(996) : error C2220: warning treated as error - no 'object' file generated c:\core

64-bit Windows build failure after MSVC Update

After I updated from MSVC 15.7.6 to 15.8.1, I started seeing the following build failure: [build CXX] sc/source/ui/docshell/docsh8.cxx c:\core\sc\source\ui\docshell\docsh8.cxx(996) : error C2220: warning treated as error - no 'object' file generated c:\core\sc\source\ui\docshell\docsh8.cxx(996)

Re: 64-bit Windows build failure: 'this' pointer for member, may not be aligned 8 as expected by the constructor

I confirmed your 2nd attempt was the fix. After reverting: https://cgit.freedesktop.org/libreoffice/core/commit/?id=4f13f8dd the error came back. The workaround code is ugly. If you're certain the logic is the same, you want to revert it and disable the warning TODO to enable them with future

Re: 64-bit Windows build failure: 'this' pointer for member, may not be aligned 8 as expected by the constructor

On Fri, 2018-08-03 at 04:02 +, Luke Benes wrote: > Actually, it seems fixed now. I just did a clean 64-bit release > build, and it succeeded without any errors. > > Was this a real issue or just a quirk in the compiler? Seeing as no other compiler was complaining I assume so. ___

Re: 64-bit Windows build failure: 'this' pointer for member, may not be aligned 8 as expected by the constructor

Actually, it seems fixed now. I just did a clean 64-bit release build, and it succeeded without any errors. Was this a real issue or just a quirk in the compiler? Thank Caolán! ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lis

Re: 64-bit Windows build failure: 'this' pointer for member, may not be aligned 8 as expected by the constructor

On Tue, 2018-07-31 at 03:48 +, Luke Benes wrote: > Caolán, > Sorry to report that: > > https://cgit.freedesktop.org/libreoffice/core/commit/?id=397c2e67 I suppose https://cgit.freedesktop.org/libreoffice/core/commit/?id=4f13f8ddeebca1 de9fd30f0aae71e3f84383656a made no difference either ?

Re: 64-bit Windows build failure: 'this' pointer for member, may not be aligned 8 as expected by the constructor

Caolán, Sorry to report that: https://cgit.freedesktop.org/libreoffice/core/commit/?id=397c2e67 Does not clear the warning. The build is failing with the same error. >From tinderbox Win-x86_64_42: https://tinderbox.libreoffice.org/cgi-bin/gunzip.cgi?tree=MASTER&brief-log=1533004201.27570 32-bi

Re: 64-bit Windows build failure: 'this' pointer for member, may not be aligned 8 as expected by the constructor

On Sun, 2018-07-29 at 22:23 +, Luke Benes wrote: > I can confirm reverting: > > https://cgit.freedesktop.org/libreoffice/core/commit/?id=8b8fb4ac > > Fixes this issue, allowing the build to succeed. Maybe https://cgit.freedesktop.org/libreoffice/core/commit/?id=397c2e67 e6614f87e408432f63956

Re: 64-bit Windows build failure: 'this' pointer for member, may not be aligned 8 as expected by the constructor

I can confirm reverting: https://cgit.freedesktop.org/libreoffice/core/commit/?id=8b8fb4ac Fixes this issue, allowing the build to succeed. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/li

64-bit Windows build failure: 'this' pointer for member, may not be aligned 8 as expected by the constructor

Both my own builds and the 64-bit Win tinderbox @42 are now failing with the following error: [build CXX] sw/source/filter/ww8/ww8scan.cxx C:/core/sw/source/filter/ww8/ww8scan.cxx(8445): error C2220: warning treated as error - no 'object' file generated C:/core/sw/source/filter/ww8/ww8scan.cx

Re: [global-libreoffice-ci] Daily Screenshot Build on Windows - Build # 410 - Failure!

On 31/05/18 16:59, Stephan Bergmann wrote: CppunitTest_sc_screenshots (executed as part of `make screenshot`) reliably fails on Windows (but is known to work on other platforms) since the below build, so one of the commits listed is likely the culprit.  The failure is always C:/cygwin/home/td

Re: [global-libreoffice-ci] Daily Screenshot Build on Windows - Build # 410 - Failure!

ce.org wrote: Daily Screenshot Build on Windows - Build # 410 - Failure: Changes for Build #410 [j.carl43] Fix typos [Julien Nabet] Fix typo [Miklos Vajna] tdf#117505 RTF export: fix incorrect header distance for first/follow [Miklos Vajna] find-unneeded-includes: Make the output user frie

Re: Windows Build Query

> On 6 Nov 2016, at 07:07, Noel Grandin wrote: > > are you sure you have gawk installed? > > More generally, did you follow the instructions here: > https://wiki.documentfoundation.org/Development/BuildingOnWindows > We sugge

Re: Windows Build Query

are you sure you have gawk installed? More generally, did you follow the instructions here: https://wiki.documentfoundation.org/Development/BuildingOnWindows ​ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/m

Re: Windows Build Query

do point me to this. Thank you in advance. Jason From: LibreOffice on behalf of Christian Lohmaier Sent: 10 October 2016 10:26 To: Jason Marshall Cc: libreoffice@lists.freedesktop.org Subject: Re: Windows Build Query Hi Jason, On Sun, Oct 9, 2016 at 1:11 PM,

Re: Windows Build Query

Hi Jason, On Sun, Oct 9, 2016 at 1:11 PM, Jason Marshall wrote: > […] > I then run the following command within the directory '/cygdrive/c/cygwin': > > /opt/lo/bin/make you need to run make from with the same directory where you ran autogen.sh from. That can be the source-directory or another di

Fw: Windows Build Query

From: Jason Marshall Sent: 09 October 2016 11:11 To: libreoffice@lists.freedesktop.org Subject: Windows Build Query Dear Sir/ Madam I am attempting to build on a 32 bit Windows 7 platform. I have successfully configured the build using the following

Windows Build Query

Dear Sir/ Madam I am attempting to build on a 32 bit Windows 7 platform. I have successfully configured the build using the following command: /cygdrive/c/sources/libo-core/autogen.sh \ --with-external-tar=/cygdrive/c/sources/lo-externalsrc \ --with-junit=/cygdrive/c/sources/junit-4.10.jar \

[Bug 97562] refresh windows build system

https://bugs.documentfoundation.org/show_bug.cgi?id=97562 jan iversen changed: What|Removed |Added Whiteboard||ToBeReviewed -- You are receiving

[Bug 97560] refresh windows build system

https://bugs.documentfoundation.org/show_bug.cgi?id=97560 jan iversen changed: What|Removed |Added Whiteboard||ToBeReviewed -- You are receiving

[Bug 97564] refresh windows build system

https://bugs.documentfoundation.org/show_bug.cgi?id=97564 jan iversen changed: What|Removed |Added Whiteboard||ToBeReviewed -- You are receiving

[Bug 97559] refresh windows build system

https://bugs.documentfoundation.org/show_bug.cgi?id=97559 jan iversen changed: What|Removed |Added Whiteboard||ToBeReviewed -- You are receiving

[Bug 97556] resurrect windows build system

https://bugs.documentfoundation.org/show_bug.cgi?id=97556 jan iversen changed: What|Removed |Added Whiteboard||ToBeReviewed -- You are receiving

[Bug 97557] resurrect windows build system

https://bugs.documentfoundation.org/show_bug.cgi?id=97557 jan iversen changed: What|Removed |Added Whiteboard||ToBeReviewed -- You are receiving

[Bug 97563] refresh windows build system

https://bugs.documentfoundation.org/show_bug.cgi?id=97563 jan iversen changed: What|Removed |Added Whiteboard||ToBeReviewed -- You are receiving

[Bug 97556] resurrect windows build system

https://bugs.documentfoundation.org/show_bug.cgi?id=97556 jan iversen changed: What|Removed |Added CC||libreoffice@lists.freedeskt

[Bug 97564] refresh windows build system

https://bugs.documentfoundation.org/show_bug.cgi?id=97564 jan iversen changed: What|Removed |Added CC||libreoffice@lists.freedeskt

[Bug 97563] refresh windows build system

https://bugs.documentfoundation.org/show_bug.cgi?id=97563 jan iversen changed: What|Removed |Added CC||libreoffice@lists.freedeskt

[Bug 97562] refresh windows build system

https://bugs.documentfoundation.org/show_bug.cgi?id=97562 jan iversen changed: What|Removed |Added CC||libreoffice@lists.freedeskt

[Bug 97560] refresh windows build system

https://bugs.documentfoundation.org/show_bug.cgi?id=97560 jan iversen changed: What|Removed |Added CC||libreoffice@lists.freedeskt

[Bug 97557] resurrect windows build system

https://bugs.documentfoundation.org/show_bug.cgi?id=97557 jan iversen changed: What|Removed |Added CC||libreoffice@lists.freedeskt

[Bug 97559] refresh windows build system

https://bugs.documentfoundation.org/show_bug.cgi?id=97559 jan iversen changed: What|Removed |Added CC||libreoffice@lists.freedeskt

Re: Gerrit Windows build: what configure should I use at home?

On 07/17/2015 07:24 PM, Norbert Thiebaud wrote: thanks, I used that without symbols or other debug settings, just to see how it goes. What I use for the jenkins slave-bot is lode: https://wiki.documentfoundation.org/Development/lode assuming you already have a cygwin environment, then cygwi

Re: Gerrit Windows build: what configure should I use at home?

> > > thanks, I used that without symbols or other debug settings, just to see how > it goes. What I use for the jenkins slave-bot is lode: https://wiki.documentfoundation.org/Development/lode assuming you already have a cygwin environment, then git clone git://gerrit.libreoffice.org/lode cd lod

Re: Gerrit Windows build: what configure should I use at home?

On 07/16/2015 01:58 PM, Ashod Nakashian wrote: You are looking for autogen.sh. Look at a log on Jenkins (not Gerrit) and find the parameters passed to unfortunately, on the build log that failed me, of which I couldn't tell why, the autogen.sh line is nowhere to be seen: http://ci.libreoffi

Re: Gerrit Windows build: what configure should I use at home?

You are looking for autogen.sh. Look at a log on Jenkins (not Gerrit) and find the parameters passed to autogen.sh. You'd need to customize a couple of them (junit and ant, which you must download and place somewhere on your system and give the path to autogen.sh). For reference, here is mine (it

Gerrit Windows build: what configure should I use at home?

Hi all, I'd like to prepare home a Win7 machine to build LibO with a configure script as the one used by gerrit builds. What will it be the most current configure to use? Looking at the log available, it seems that a prepared set of shell variable is used, what configure generated it? Tha

Re: Windows build time: 50% longer....

On Wed, Jun 17, 2015 at 2:56 AM, Stephan Bergmann wrote: > On 06/17/2015 09:31 AM, Norbert Thiebaud wrote: >> >> On Wed, Jun 17, 2015 at 2:10 AM, Stephan Bergmann >> wrote: >>> >>> On 06/17/2015 01:58 AM, Norbert Thiebaud wrote: most likely candidate is prolly: 9b06d36571

Re: Windows build time: 50% longer....

On 06/17/2015 09:31 AM, Norbert Thiebaud wrote: On Wed, Jun 17, 2015 at 2:10 AM, Stephan Bergmann wrote: On 06/17/2015 01:58 AM, Norbert Thiebaud wrote: most likely candidate is prolly: 9b06d36571bbfa2d722f36610375e7cd24be81a7 reenable JunitTest_dbaccess_complex part RowSet ...which shoul

Re: Windows build time: 50% longer....

On Wed, Jun 17, 2015 at 2:10 AM, Stephan Bergmann wrote: > On 06/17/2015 01:58 AM, Norbert Thiebaud wrote: >> >> most likely candidate is prolly: >> >> 9b06d36571bbfa2d722f36610375e7cd24be81a7 reenable >> JunitTest_dbaccess_complex part RowSet > > > ...which should be easy to verify with "time mak

Re: Windows build time: 50% longer....

On 06/17/2015 01:58 AM, Norbert Thiebaud wrote: most likely candidate is prolly: 9b06d36571bbfa2d722f36610375e7cd24be81a7 reenable JunitTest_dbaccess_complex part RowSet ...which should be easy to verify with "time make JunitTest_dbaccess_complex" vs. "git revert 9b06d36571bbfa2d722f36610375

Windows build time: 50% longer....

On Windows we use to build on tb65 in 30 minutes flat. for example http://ci.libreoffice.org/job/lo_gerrit_master/Gerrit=Gerrit,Platform=Windows/2776/ or http://ci.libreoffice.org/job/lo_gerrit_master/Gerrit=Gerrit,Platform=Windows/2769/ but currently on master this is more ~45 minutes That

Re: broken windows build

Hey, On Mon, Feb 16, 2015 at 2:38 PM, Eike Rathke wrote: > Hi Markus, > > On Saturday, 2015-02-14 20:30:57 +0100, Markus Mohrhard wrote: > > > I just disabled the test for now but please move it to > > subsequent_filters-test. > > Yeah, who would had thought of it.. ;-) > Thanks for the interim

Re: broken windows build

Hi Markus, On Saturday, 2015-02-14 20:30:57 +0100, Markus Mohrhard wrote: > I just disabled the test for now but please move it to > subsequent_filters-test. Yeah, who would had thought of it.. ;-) Thanks for the interim fix, Jan is working on a solution. Eike -- LibreOffice Calc developer.

broken windows build

Hey guys, just a short reminder that you can't add any test that tries to import files to ucalc. Ucalc can't load the filter code and misses a number of services that are necessary to import files. This was responsible on Windows for the crash in ucalc. I just disabled the test for now but please

Re: broken windows build

On Tue, Feb 10, 2015 at 11:32 AM, Stephan Bergmann wrote: > > Maybe the tooling's output can be improved so that it becomes more apparent > in that what > actually happened was that "make" was killed upon a timeout. timing out from the

Re: broken windows build

On 02/10/2015 08:50 AM, Norbert Thiebaud wrote: since most likely http://ci.libreoffice.org/job/lo_tb_master_win/506/ one of the four patches involved there seems to cause the windows build to break and enter a cpu-loop in make, which cause a timeout... which does not apparently properly kill

broken windows build

since most likely http://ci.libreoffice.org/job/lo_tb_master_win/506/ one of the four patches involved there seems to cause the windows build to break and enter a cpu-loop in make, which cause a timeout... which does not apparently properly kill make, and therefore the tcp-server is hung too and

Re: Calc on recent Windows build has horrible repaint problem.

On Wed, Oct 22, 2014 at 5:03 PM, Kohei Yoshida wrote: > Hi there, > > So, I just built from the master branch on Windows, launched Calc and > shocked in horror... > > I've attached a screenshot of what I see. Here, I opened a new Calc > document, clicked a few cells, and select a range... > > Any

Re: Calc on recent Windows build has horrible repaint problem.

On Wed, 2014-10-22 at 17:20 -0700, Robinson Tryon wrote: > Sounds like you've encountered this bug: > https://bugs.freedesktop.org/show_bug.cgi?id=84854 > "Calc issues with screen drawing(all Windows and 32-bit Linux)" This one indeeds sounds like the problem I'm seeing. Kohei __

Re: Calc on recent Windows build has horrible repaint problem.

On Wed, 2014-10-22 at 17:20 -0700, Robinson Tryon wrote: > Lemme guess -- you're on a 32bit machine? Nope. I'm on 64-bit Windows. But we only have a 32-bit version for Windows. Kohei ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org htt

Calc on recent Windows build has horrible repaint problem.

Hi there, So, I just built from the master branch on Windows, launched Calc and shocked in horror... I've attached a screenshot of what I see. Here, I opened a new Calc document, clicked a few cells, and select a range... Anybody with any clue? Kohei ___

Re: My Windows build is much slower than Linux build. Any way to speed up?

On Mon, Dec 23, 2013 at 04:15:30PM +0100, Bjoern Michaelsen wrote: > Finally, Michael Stahl is considering moving gbuild to work on a native > windows > GNU make without the cygwin wrapper. But that likely is quite a bit of work. FWIW, to not sabotage that goal it would be wise to try to restrict

Re: My Windows build is much slower than Linux build. Any way to speed up?

> You can disable link time optimisation with a configure option, But surely any kind of optimisation (link-time or just source-file-compile-time) is mainly done when preparing code to actually deliver to users (including alpha, beta, and release candidate builds). And does it really matte

  1   2   3   >