On Thu, 2012-04-12 at 14:11 +0200, Stephan Bergmann wrote:
Can't remember any details, but I think I did have a real problem with
it before I discovered --disable-linkoo sometime last year
Hey ho :-)
and recently I remote-debugged something with somebody, and we came
to the
On Wed, 2012-04-18 at 11:06 +0100, Michael Meeks wrote:
And of course you need to source 'ooenv' to get STAR_RESOURCEPATH set
[ though strangely things seem to work without that these days ].
soffice script will source ooenv if it finds it, if you mean that.
C.
On 2012-04-11 18:19, Stephan Bergmann wrote:
My understanding is that we use classic paths (not starting with
\\?) whenever they are short enough, anyway. So the problem cannot
be solved with an #if, but (short of abandoning berkeleydb) needs to
be worked around by making sure the LO
On 04/12/2012 10:00 AM, Noel Grandin wrote:
On 2012-04-11 18:19, Stephan Bergmann wrote:
My understanding is that we use classic paths (not starting with
\\?) whenever they are short enough, anyway. So the problem cannot
be solved with an #if, but (short of abandoning berkeleydb) needs to
be
On Wed, 2012-04-11 at 18:19 +0200, Stephan Bergmann wrote:
So the problem cannot be
solved with an #if, but (short of abandoning berkeleydb) needs to be
worked around by making sure the LO installation is in a location with a
short path (so that the paths of any files within the
On Wed, 2012-04-11 at 17:34 +0200, Stephan Bergmann wrote:
(And even on Linux, linkoo does not really work, and I'm happy to avoid
it via --disable-linkoo. But I do understand that this is not very
newbee friendly.)
Oh !? we should fix that, is there a bug ? it'd prolly be an
On 04/12/2012 11:40 AM, Michael Meeks wrote:
On Wed, 2012-04-11 at 17:34 +0200, Stephan Bergmann wrote:
(And even on Linux, linkoo does not really work, and I'm happy to avoid
it via --disable-linkoo. But I do understand that this is not very
newbee friendly.)
But - overall it does a
On 04/10/2012 07:06 PM, Michael Stahl wrote:
is this ooinstall thing supposed to work on Windows at all? AFAIK it
symlinks stuff left and right, and running the result of that can hardly
work as native Win32 program?
IIUC, it should only use symlinks if used in combination with (default)
On 2012-04-11 08:48, Stephan Bergmann wrote:
the bigger problem is that this project doesn't seem to have any Windows
developers :)
Ack.
It's kind of catch-22.
I develop on Windows, but I do my LibreOffice work on Ubuntu running
inside a VMWare image, simply because the Windows build
On Wednesday 11 of April 2012, Stephan Bergmann wrote:
On 04/10/2012 07:06 PM, Michael Stahl wrote:
is this ooinstall thing supposed to work on Windows at all? AFAIK it
symlinks stuff left and right, and running the result of that can hardly
work as native Win32 program?
IIUC, it should
On Wed, 2012-04-11 at 14:17 +0200, Lubos Lunak wrote:
And, BTW, I think linkoo could be modified for Windows, so that it does not
create symlinks, but instead it copies a file if the one in solver/ is newer.
Wouldn't it be nice if we could just built into a output install tree in
the first
Hello,
On 10/04/12 20:02, Tor Lillqvist wrote:
Presumably not. The way I iterate edit-compile-test on Windows (when I
do it, which is not often lately) is to have a normal installation (in
a virtual machine), i.e. from an installer, and then manually replace
the DLL(s) I am debugging... and
On 04/11/2012 02:17 PM, Lubos Lunak wrote:
On Wednesday 11 of April 2012, Stephan Bergmann wrote:
However, I guess the mechanisms to create a LO installation against
which to run the tests (which was always handled slightly differently on
Windows, to avoid problems with long pathnames) has been
On 04/11/2012 02:24 PM, Caolán McNamara wrote:
On Wed, 2012-04-11 at 14:17 +0200, Lubos Lunak wrote:
And, BTW, I think linkoo could be modified for Windows, so that it does not
create symlinks, but instead it copies a file if the one in solver/ is newer.
Wouldn't it be nice if we could just
On 2012-04-11 17:31, Stephan Bergmann wrote:
ooinstall needs to be fixed to work on Windows (my understanding is
that it does not). Second, as long as long pathnames on Windows are
still an issue (and my understanding is that they are, at least for
our interaction with the berkeleydb
On 04/11/2012 05:43 PM, Noel Grandin wrote:
On 2012-04-11 17:31, Stephan Bergmann wrote:
ooinstall needs to be fixed to work on Windows (my understanding is
that it does not). Second, as long as long pathnames on Windows are
still an issue (and my understanding is that they are, at least for
Hello,
I've tried to do %subj% and it doesn't work for me, neither with my test
build [1] nor with a tinderbox where I tried to enable it [2]. Given that
this is the primary user platform, I'm rather surprised this doesn't work. Is
that just some temporary breakage, or is there a bigger
On 10/04/12 18:50, Lubos Lunak wrote:
Hello,
I've tried to do %subj% and it doesn't work for me, neither with my test
build [1] nor with a tinderbox where I tried to enable it [2]. Given that
this is the primary user platform, I'm rather surprised this doesn't work. Is
that just some
is this ooinstall thing supposed to work on Windows at all?
Presumably not. The way I iterate edit-compile-test on Windows (when I
do it, which is not often lately) is to have a normal installation (in
a virtual machine), i.e. from an installer, and then manually replace
the DLL(s) I am
19 matches
Mail list logo
