No further Error 1937 installer issues from TB 39 builds, fdo#69601 was
closed WFM -- but don't know if Michael S. has additional work to do yet on
the cli_cppuhelper.dll and other signature mechanism.
But for @ape and @pedro, 32-bit Windows XP sp3 installed and ran today's
2013-10-04_08.16.05
@: V Stuart Foote
Thanks,
LibO-Dev_4.2.0.0.alpha0+ (ID: 050248fea53adb6a14b649c5f84dd69a8faff997,
TinderBox: Win-x86@39, Time: 2013-10-04_08:16:05) started on Windows XP
64-bit sp2 (last update).
--
ape
--
View this message in context:
Hi ape
ape wrote
Look the log file on the page:
http://tinderbox.libreoffice.org/cgi-bin/gunzip.cgi?tree=MASTERfull-log=1379905201.19567
.
Rows 169, 170 and 171 show that Kendy builds TB#39 MSI package for The
Vista OS, Windows-7 and Windows-8:
169 checking for Windows SDK... found
Hi Pedro, *,
Am 23.09.2013 12:16 schrieb Pedro pedl...@gmail.com:
ape wrote
170 configure: WARNING: If a build created with VS 2012 should run on
Windows XP,
171 configure: WARNING: use --with-windows-sdk=7.1A (requires VS 2012
Update 1 or newer).
Ok. The question is why? What is the
Hi Christian
Christian Lohmaier-3 wrote
Ok. The question is why? What is the point of disabling XP suport
It is the contrary - before the change that added the warning, you
couldn't
target XP when using current version of visual studio. Visual studio is
what didn't support XP, the
Michael Stahl-2 wrote
where do you get the idea that support for XP would be dropped from
release builds now? clearly the problem is just a badly configured
tinderbox, perhaps it has the non-updated release VS 2012 installed that
only has the 8.0 sdk.
Let's see: in August there were 3
Michael,
My experiences related to the fact that changes have been made to the code.
These changes improve The LibO-4.2 interact with Windows Explorer 7 and 8. I
would like to make sure that this does not disrupt Windows XP Explorer. But
I can't do it. I think that comprehensive verification is
Trying to work with TB builds of Master for Windows, but have an open but
unconfirmed Bugzilla issue fdo 69601
https://bugs.freedesktop.org/show_bug.cgi?id=69601 .
For recent TB 39 builds of master, I have been receiving MSI Error 1937 on a
Windows 7 Ultimate, sp1 64-bit system. Can use the
V Stuart Foote wrote
The same downloads will install on Wnidows 8 and on Windows 7 Enterprise
sp1 64-bit system. But not on Windows XP where I get the same Error 1937
for same component.
So far it is just on one system for me. But is anyone else having this
issue? Ideas about what could
V Stuart Foote wrote
Has happened with the TB 39 builds for 16, 19, 20, 21 and now 22
September. Last that had actually installed for me on this system was
from 9 September. Checking builds for the 10th, 11th and 15th at the
moment.
TB 39 builds of master for 10th and 11th of September
10 matches
Mail list logo
