Hi,
with integration of cws unowinregcross (and therefore in m181) we have a
new build requirement: mingw32. See issue 49178.
It is used for building unowinreg.dll (because using random binaries out
of CVS is bad(tm)).
So you need to install mingw32; IIRC mingw32 has binaries; if not, you
also c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rene Engelhard wrote:
> with integration of cws unowinregcross (and therefore in m181) we have a
> new build requirement: mingw32. See issue 49178.
^ 49718
Regards,
Rene
-BEGIN PGP SIGNATURE-
Ve
Rene Engelhard wrote:
> Hi,
>
> with integration of cws unowinregcross (and therefore in m181) we have a
> new build requirement: mingw32. See issue 49178.
This is not completely true, since m181 and only for non-Windows targets
there is the possibility to either install mingw32 or to copy unowin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Volker Quetschke wrote:
> Windows "builders" are *unaffected*.
See $SUBJECT.
"[...] !Windows [...]"
> /me repeats this to prevent some confusion that Windows builds now require
> mingw.
I didn't say anything else.
> Actually the configure message
On Mon, Aug 07, 2006 at 09:32:39AM +0200, Rene Engelhard wrote:
> Volker Quetschke wrote:
> > Windows "builders" are *unaffected*.
> [...]
> > Actually the configure message should mention the download/copy part.
>
> No. (Had that discussion already on IRC...)
Well, the "discussion" on IRC basic
Christian Lohmaier wrote:
> On Mon, Aug 07, 2006 at 09:32:39AM +0200, Rene Engelhard wrote:
>> Volker Quetschke wrote:
>>> Windows "builders" are *unaffected*.
>> [...]
>>> Actually the configure message should mention the download/copy part.
>> No. (Had that discussion already on IRC...)
Not wit
Am Montag, 7. August 2006 14:09 schrieb Christian Lohmaier:
> On Mon, Aug 07, 2006 at 09:32:39AM +0200, Rene Engelhard wrote:
> > Volker Quetschke wrote:
> > > Windows "builders" are *unaffected*.
> > [...]
> > > Actually the configure message should mention the download/copy part.
> >
> > No. (H
Hi Rene,
On Mon, Aug 07, 2006 at 02:13:43PM +0200, Rene Engelhard wrote:
> Am Montag, 7. August 2006 14:09 schrieb Christian Lohmaier:
> > On Mon, Aug 07, 2006 at 09:32:39AM +0200, Rene Engelhard wrote:
> > > Volker Quetschke wrote:
> > > > Windows "builders" are *unaffected*.
> > > [...]
> > > >
Could someone give pointers to the roots of this whole issue?
Why were we checking in a win32 dll into CVS and why do *nix builders
have to care?
Kai
On 8/7/06, Christian Lohmaier <[EMAIL PROTECTED]> wrote:
Hi Rene,
On Mon, Aug 07, 2006 at 02:13:43PM +0200, Rene Engelhard wrote:
> Am Montag,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Volker Quetschke wrote:
> > Well, the "discussion" on IRC basically was you stating: "I did not add
> > the URL on purpose and don't want to add it" (paraphrased)
>
> That's a thorough discussion! Because your (debians) opinion is against
> this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kai Backman wrote:
> Could someone give pointers to the roots of this whole issue?
> Why were we checking in a win32 dll into CVS and why do *nix builders
The SDK contains unowinreg.dll, a JNI library needed for deploying
Java programs developed with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rene Engelhard wrote:
> Hi,
>
> Volker Quetschke wrote:
> > > Well, the "discussion" on IRC basically was you stating: "I did not add
> > > the URL on purpose and don't want to add it" (paraphrased)
> >
> > That's a thorough discussion! Because your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Volker Quetschke wrote:
> Rene Engelhard wrote:
> > Hi,
> >
> > with integration of cws unowinregcross (and therefore in m181) we have a
> > new build requirement: mingw32. See issue 49178.
>
> This is not completely true, since m181 and only for non
Moin!
Rene Engelhard wrote:
> Rene Engelhard wrote:
>>> Hi,
>>>
>>> Volker Quetschke wrote:
> Well, the "discussion" on IRC basically was you stating: "I did not add
> the URL on purpose and don't want to add it" (paraphrased)
That's a thorough discussion! Because your (debians) opini
Rene Engelhard wrote:
> Volker Quetschke wrote:
>>> Rene Engelhard wrote:
Hi,
with integration of cws unowinregcross (and therefore in m181) we have a
new build requirement: mingw32. See issue 49178.
>>> This is not completely true, since m181 and only for non-Windows targets
>>
Am Dienstag, 8. August 2006 05:48 schrieb Volker Quetschke:
> Mentioning the possibility of a download of that dll as alternative to
> installing
> the mingw package would be nice for the "builder" that just got bitten by this
> configure problem.
Done in cws configure19.
Regards,
Rene
--
.'
Kai Backman wrote:
Could someone give pointers to the roots of this whole issue?
Why were we checking in a win32 dll into CVS and why do *nix builders
have to care?
I communicate my opinion of the whole thing in the issue already. But
again, the unowinreg.dll is used by the UNO simple bootstra
Rene Engelhard wrote:
Hi,
with integration of cws unowinregcross (and therefore in m181) we have a
new build requirement: mingw32. See issue 49178.
That should read "See issue 49718", I assume.
It is used for building unowinreg.dll (because using random binaries out
of CVS is bad(tm)).
Sor
On 17/08/2006, at 7:06 PM, Jürgen Schmidt wrote:
The whole issue came from some extreme views and i like the comment
from Volker
the extreme view can be correct. Sun takes an extreme position on
JCA, and it is also correct that any open source project should be
built from sources.
ji
Stephan Bergmann wrote:
Rene Engelhard wrote:
Hi,
with integration of cws unowinregcross (and therefore in m181) we have a
new build requirement: mingw32. See issue 49178.
That should read "See issue 49718", I assume.
It is used for building unowinreg.dll (because using random binaries out
Jim Watson wrote:
On 17/08/2006, at 7:06 PM, Jürgen Schmidt wrote:
The whole issue came from some extreme views and i like the comment
from Volker
the extreme view can be correct. Sun takes an extreme position on JCA,
and it is also correct that any open source project should be built fro
Am Donnerstag, 17. August 2006 11:27 schrieb Stephan Bergmann:
> - We have some OOo source files in odk/source/unowinreg/win/ from which
> a Windows DLL is built, and that Windows DLL is needed on all platforms,
> not just Windows.
Right.
> - On SRC680m180 and earlier, the DLL resulting from th
The work Rene has done with the cross compilation is great, but I
think we need to minimize the number of -required- external
dependencies.
Here is my suggestion for a solution:
- Check unowinreg.dll back into the repository and use it by default
without recompilation on all platforms.
- Include
Rene Engelhard wrote:
Am Donnerstag, 17. August 2006 11:27 schrieb Stephan Bergmann:
- We have some OOo source files in odk/source/unowinreg/win/ from which
a Windows DLL is built, and that Windows DLL is needed on all platforms,
not just Windows.
Right.
- On SRC680m180 and earlier, the DLL
Kai Backman wrote:
The work Rene has done with the cross compilation is great, but I
think we need to minimize the number of -required- external
dependencies.
Here is my suggestion for a solution:
- Check unowinreg.dll back into the repository and use it by default
without recompilation on all p
Kai Backman wrote:
The work Rene has done with the cross compilation is great, but I
think we need to minimize the number of -required- external
dependencies.
Here is my suggestion for a solution:
- Check unowinreg.dll back into the repository and use it by default
without recompilation on all p
Am Donnerstag, 17. August 2006 15:51 schrieb Stephan Bergmann:
> >> person is required to also check in a new odk/bin/win/unowinreg.dll
> >> (i.e., do a build on Windows to obtain the new DLL and then check it
> >> in). The rationale for the checked-in DLL is that it is difficult or
> >> imposs
Am Donnerstag, 17. August 2006 16:12 schrieb Stephan Bergmann:
> This suggestion looks fine with me, I would even agree to a setup where
> recompilation is on by default on those platforms where it is known to
> work without additional prerequisites (e.g., wntmsci10). (I too think
That's statu
Hi,
Am Donnerstag, 17. August 2006 16:15 schrieb Jürgen Schmidt:
> Kai Backman wrote:
> > The work Rene has done with the cross compilation is great, but I
> > think we need to minimize the number of -required- external
> > dependencies.
> >
> > Here is my suggestion for a solution:
> > - Check u
Rene Engelhard wrote:
Hi,
Am Donnerstag, 17. August 2006 16:15 schrieb Jürgen Schmidt:
Kai Backman wrote:
The work Rene has done with the cross compilation is great, but I
think we need to minimize the number of -required- external
dependencies.
Here is my suggestion for a solution:
- Check u
Hi,
Kai Backman wrote:
The work Rene has done with the cross compilation is great, but I
think we need to minimize the number of -required- external
dependencies.
Here is my suggestion for a solution:
- Check unowinreg.dll back into the repository and use it by default
without recompilation on
On Thu, Aug 17, 2006 at 03:42:39PM +0200, Kai Backman wrote:
>
> Here is my suggestion for a solution:
> - Check unowinreg.dll back into the repository and use it by default
> without recompilation on all platforms.
+1
> - Include a configure switch that forces recompilation of the DLL. On
> win
32 matches
Mail list logo
