On 8 Oct, Matthias Seidel wrote:
> Hi Don,
>
> Am 08.10.19 um 01:16 schrieb Don Lewis:
>> On 7 Oct, Matthias Seidel wrote:
>>> I will start a test tomorrow...
>>>
>>> With both versions installed I can use --with-nasm-home to switch
>>> between them.
>> According to the NASM docs, it looks like
Hi Don,
Am 08.10.19 um 01:16 schrieb Don Lewis:
> On 7 Oct, Matthias Seidel wrote:
>> I will start a test tomorrow...
>>
>> With both versions installed I can use --with-nasm-home to switch
>> between them.
> According to the NASM docs, it looks like the bitness of NASM doesn't
> make a differenc
On 7 Oct, Matthias Seidel wrote:
> I will start a test tomorrow...
>
> With both versions installed I can use --with-nasm-home to switch
> between them.
According to the NASM docs, it looks like the bitness of NASM doesn't
make a difference. THe bitness of the assembler is governed by the
outpu
I will start a test tomorrow...
With both versions installed I can use --with-nasm-home to switch
between them.
Matthias
Am 07.10.19 um 23:08 schrieb Don Lewis:
> On 7 Oct, Matthias Seidel wrote:
>> Hi Don,
>>
>> Thanks for that!
>>
>> Since NASM is now needed for Windows: If I install the 64bi
On 7 Oct, Matthias Seidel wrote:
> Hi Don,
>
> Thanks for that!
>
> Since NASM is now needed for Windows: If I install the 64bit version,
> will it produce 32bit code?
I wuuld think so, but I don't know for sure and have no way to test it.
-
a commit to branch trunk
> in repository https://gitbox.apache.org/repos/asf/openoffice.git
>
>
> The following commit(s) were added to refs/heads/trunk by this push:
> new fccc850 Upgrade openssl to version 1.0.2t. This requires NASM to
> build on Windows.
> fccc850
Am 17.05.19 um 00:27 schrieb Patricia Shanahan:
>
>
> On 5/16/2019 3:23 PM, Matthias Seidel wrote:
>> Hi Patricia,
>>
>> Am 17.05.19 um 00:17 schrieb Patricia Shanahan:
>>>
>>>
>>> On 5/15/2019 8:06 PM, Damjan Jovanovic wrote:
On Thu, May 16, 2019 at 4:45 AM Patricia Shanahan
wrote:
On 5/16/2019 3:23 PM, Matthias Seidel wrote:
Hi Patricia,
Am 17.05.19 um 00:17 schrieb Patricia Shanahan:
On 5/15/2019 8:06 PM, Damjan Jovanovic wrote:
On Thu, May 16, 2019 at 4:45 AM Patricia Shanahan wrote:
"Install Microsoft Windows SDK for Windows 7 and .NET Framework 3.5.
SP1
(rec
Hi Patricia,
Am 17.05.19 um 00:17 schrieb Patricia Shanahan:
>
>
> On 5/15/2019 8:06 PM, Damjan Jovanovic wrote:
>> On Thu, May 16, 2019 at 4:45 AM Patricia Shanahan wrote:
>>
>>> "Install Microsoft Windows SDK for Windows 7 and .NET Framework 3.5.
>>> SP1
>>> (recommended by Microsoft. Note: lat
On 5/15/2019 8:06 PM, Damjan Jovanovic wrote:
On Thu, May 16, 2019 at 4:45 AM Patricia Shanahan wrote:
"Install Microsoft Windows SDK for Windows 7 and .NET Framework 3.5. SP1
(recommended by Microsoft. Note: later versions of the Windows SDK will
not work. AOO can not be built with MSVC 20
On 5/15/2019 8:06 PM, Damjan Jovanovic wrote:
On Thu, May 16, 2019 at 4:45 AM Patricia Shanahan wrote:
"Install Microsoft Windows SDK for Windows 7 and .NET Framework 3.5. SP1
(recommended by Microsoft. Note: later versions of the Windows SDK will
not work. AOO can not be built with MSVC 20
On Thu, May 16, 2019 at 4:45 AM Patricia Shanahan wrote:
> "Install Microsoft Windows SDK for Windows 7 and .NET Framework 3.5. SP1
> (recommended by Microsoft. Note: later versions of the Windows SDK will
> not work. AOO can not be built with MSVC 2010 or 2012 - MSVC 2008 is
> needed and is foun
"Install Microsoft Windows SDK for Windows 7 and .NET Framework 3.5. SP1
(recommended by Microsoft. Note: later versions of the Windows SDK will
not work. AOO can not be built with MSVC 2010 or 2012 - MSVC 2008 is
needed and is found in the Windows 7 SDK)"
Both the links given for installing t
Thanks. I'll try that next.
On 10/18/2016 7:30 PM, John D'Orazio wrote:
Not sure if this will fix but I myself found that avoiding paths with
spaces can fix a number of errors. So I had the Windows SDK installed to a
custom path where I substituted spaces with underscores. Then in my
configure s
Not sure if this will fix but I myself found that avoiding paths with
spaces can fix a number of errors. So I had the Windows SDK installed to a
custom path where I substituted spaces with underscores. Then in my
configure script I have:
SDK_PATH="D:\Microsoft_SDKs\Windows\v7.0"
As for the JDK ho
15 matches
Mail list logo