Oliver Bolte wrote:
> Hi,
> 
> the port for Visual Studio 2005 Express (CWS obo05) has been integrated
> and will be available with milestone m186 (SRC680).
> 
> Known limits:
> * ActiveX Control isn't supported due to missing ATL/MFC support

You have to use
  --disable-activex
or the build will fail at one point.

> * .NET (CLI) bridge doesn't work with Framework 2.0 (see issue #69457#)
> 
> Build requirements (free download):
> * Compiler
> * Platform SDK
> * Patch in the header "Microsoft Platform SDK/include/atl/atlwin.h"
>   (Line 1753):
>     - for(i = 0; i < m_aChainEntry.GetSize(); i++)
>     + for(int i = 0; i < m_aChainEntry.GetSize(); i++)
> * Framework SDK 2.0

You also need (--with-asm-home):
  * A Microsoft assembler

> 
> Many thanks to Volker Quetschke (changes in configure, QA),
> Daniel Boelzle (fix for UNO bridge) and Helge Delfs (QA).

Erm, I should elaborate a little on the configure part. Automatic compiler
detection is not yet implemented (I wanted to file an issue for Michael M.
once this CWS was integrated) so I better show what configure switches might
be useful. I used:

$ ./configure --with-use-shell=bash \
  --with-directx-home="/cygdrive/c/Program Files/Microsoft DirectX 9.0 SDK 
(April 2005)" \
  --with-cl-home="/cygdrive/c/Program Files/Microsoft Visual Studio 8/VC" \
  --disable-activex \
  --with-midl-path="/cygdrive/c/Program Files/Microsoft Platform SDK/Bin" \
  --with-asm-home=/cygdrive/c/mas/bin/win98 \
  --with-jdk-home=/cygdrive/c/j2sdk1.4.2_05 \
  --with-ant-home=/cygdrive/c/apache-ant-1.6.5 \
  --with-csc-path=/cygdrive/c/WINDOWS/Microsoft.NET/Framework/v2.0.50727 \
  --with-nsis-path=/cygdrive/c/PROGRA~1/NSIS

Note that --with-csc-path must point to a Framework 2 csc!

> Have fun!

Indeed :)

      Volker

-- 
= http://wiki.services.openoffice.org/wiki/Debug_Build_Problems  =
PGP/GPG key  (ID: 0x9F8A785D)  available  from  wwwkeys.de.pgp.net
key-fingerprint 550D F17E B082 A3E9 F913  9E53 3D35 C9BA 9F8A 785D

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to