Documentation/Building Guide/Building on Windows - Revision history

Sancho at 17:36, 18 September 2011

2011-09-18T17:36:47Z

Sancho at 10:44, 6 September 2011

2011-09-06T10:44:50Z

Sancho at 09:14, 6 September 2011

2011-09-06T09:14:02Z

Sancho at 17:05, 25 August 2011

2011-08-25T17:05:17Z

Sancho at 07:16, 22 August 2011

2011-08-22T07:16:24Z

Admin: 1 версия

2011-05-20T14:45:29Z

1 версия

Can't load revision 13623

@@ Line 10: / Line 10: @@
 = Overview =
-{{Template:Documentation/Windows| This document explains how to build the OpenOffice.org source code on Windows systems.}}
+{{DocWindows| This document explains how to build the OpenOffice.org source code on Windows systems.}}
 For building OpenOffice.org Cygwin is needed, a Windows program that emulates a complete Unix command line environment. To use this document you need to be familiar with a command line, but you need not to be a UNIX shell wizard.

@@ Line 84: / Line 84: @@
 |-
 | optional: [http://nsis.sourceforge.net/ Nullsoft Scriptable Install System (NSIS)]<ref name="Foot5">{{Note|If NSIS is available, a self contained Windows installer is created in addition to the MSI installer files.}}
-{{Template:Documentation/Caution|It used to be that newer version of NSIS broke the build (see {{Bug|85657}}), but it seems that it now works for NSIS up to 2.3.7.}}</ref>
+{{Caution|It used to be that newer version of NSIS broke the build (see {{Bug|85657}}), but it seems that it now works for NSIS up to 2.3.7.}}</ref>
+|
 |-
 | optional: [http://msdn.microsoft.com/directx/directxdownloads/ Microsoft DirectX SDK]<ref name="Foot6"> {{Note|If you don't want to download it you can disable DirectX support in the configuration step (<code>--disable-directx</code>).}}
-{{Template:Documentation/Caution|Current (as of 2008/01) versions of the DirectX9 SDK and Windows Platform SDK do not fit to each other. To be able to build with DirextX enabled, you need to patch one file in the Platform SDK. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID2743771 for details.}}
+{{Caution|Current (as of 2008/01) versions of the DirectX9 SDK and Windows Platform SDK do not fit to each other. To be able to build with DirextX enabled, you need to patch one file in the Platform SDK. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID2743771 for details.}}
-{{Template:Documentation/Caution|Do not use a DirectX10 SDK!}}</ref>
+{{Caution|Do not use a DirectX10 SDK!}}</ref>
+|
 |}
@@ Line 106: / Line 106: @@
 Go to http://www.cygwin.com/ and download and install the current version.
-{{Template:Documentation/Caution|Make sure that you keep the filetype set to “Unix/binary”.}}
+{{Caution|Make sure that you keep the filetype set to “Unix/binary”.}}
-{{Template:Documentation/Caution|Make sure that the PATH variable in your cygwin shell does not contain any blanks and quotes, otherwise configure will not work}}
+{{Caution|Make sure that the PATH variable in your cygwin shell does not contain any blanks and quotes, otherwise configure will not work}}
 === required additional packages ===
@@ Line 164: / Line 164: @@
 If this command is executed the first time CPAN will ask for configuration. Choose autoconfiguration.
-{{Template:Documentation/Caution|Please note that CPAN is not able to deal with usernames containing spaces. To work around this fact, when CPAN asks you to specify the ''CPAN build and cache directory'', change the default suggestion to <tt>/cpan</tt>.}}
+{{Caution|Please note that CPAN is not able to deal with usernames containing spaces. To work around this fact, when CPAN asks you to specify the ''CPAN build and cache directory'', change the default suggestion to <tt>/cpan</tt>.}}
 At the end the CPAN shell appeared and is ready to accept commands for installations. Each module is installed by typing <code>install $MODULENAME</code>. The modules that must be installed are:
@@ Line 179: / Line 179: @@
 {{Note|The last three modules are only needed if you want to use the cws tooling. These tools are necessary if you want to create and maintain your own [http://wiki.services.openoffice.org/wiki/CWS Child Workspaces] or if you want to build one of them. I recommend to install them anyway as sooner or later you want to work on a child workspace.}}
-{{Template:Documentation/Caution|I got an error message from CPAN somewhat like the following:
+{{Caution|I got an error message from CPAN somewhat like the following:
 <pre>C:\cygwin\bin\perl.exe: *** unable to remap C:\cygwin\bin\cygiconv-2.dll to same
 address as parent(0x7C0000) != 0x7D0000</pre>
 To fix this, I had to exit the Cygwin shell, run cmd.exe, then type "c:\cygwin\bin\ash.exe" to start the minimal shell, then type <code>/bin/rebaseall</code>. Then CPAN worked when I ran it again.}}
-{{Template:Documentation/Caution| I got another error when cygwin was performing <tt>make install</tt>:
+{{Caution| I got another error when cygwin was performing <tt>make install</tt>:
 <pre>ERROR: Can't create '/usr/bin'; Do not have write permissions on '/usr/bin'</pre>
 I can actually write to /usr/bin; however when I do <tt>ls -ld /usr/bin</tt>, cygwin reports no write permission; and <tt>chmod u+w /usr/bin</tt> gives <tt>Permission denied</tt>.  This causes the install process to fail when it checks permissions. As a kludge, I installed vim, and edited line 368 of /usr/lib/perl5/5.10/ExtUtils/Install.pm, replacing this:
@@ Line 194: / Line 194: @@
 = Full Builds =
-{{Template:Documentation/Caution| Use a short absolute directory name to store OpenOffice.org source, such as <tt>C:\ooo</tt>. Otherwise, there are weird issues during the building of the <tt>postprocess</tt> module, because the command line length of some build actions is too long: <pre> 1 [main] perl 1972 C:\cygwin\bin\perl.exe: *** fatal error - fork: can't reserve memory for stack 0x83C840 - 0x840000,
+{{Caution| Use a short absolute directory name to store OpenOffice.org source, such as <tt>C:\ooo</tt>. Otherwise, there are weird issues during the building of the <tt>postprocess</tt> module, because the command line length of some build actions is too long: <pre> 1 [main] perl 1972 C:\cygwin\bin\perl.exe: *** fatal error - fork: can't reserve memory for stack 0x83C840 - 0x840000,
 Win32 error 487
   </pre>}}
@@ Line 248: / Line 248: @@
 ==== configure settings tips ====
-{{Template:Documentation/Caution|Make sure that the <code>PATH</code> variable in your cygwin shell does not contain any blanks and quotes.}}
+{{Caution|Make sure that the <code>PATH</code> variable in your cygwin shell does not contain any blanks and quotes.}}
-{{Template:Documentation/Caution|Paths might have problems with spaces. Install requirements into pathes without them. Alternatively, feel free to install the various packages using the default path containing spaces and then use the mixed short path for the configure stage. The mixed short path can be obtained using Cygwin's cygpath tool, eg:
+{{Caution|Paths might have problems with spaces. Install requirements into pathes without them. Alternatively, feel free to install the various packages using the default path containing spaces and then use the mixed short path for the configure stage. The mixed short path can be obtained using Cygwin's cygpath tool, eg:
 <pre>$ cygpath -m -s "c:\Program Files\Microsoft Visual Studio 9.0\VC"
   c:/PROGRA~1/MICROS~1.0/VC</pre>
 The <code>with-psdk-home</code> setting needs a case-sensitive path name. I recommend to use case-sensitive usage in all cases - it's good to get used to case sensitivity if you are going to work with Cygwin.}}
-{{Template:Documentation/Caution|Beware of using <code>/c/</code> instead of <code>/cygdrive/c/</code>.}}
+{{Caution|Beware of using <code>/c/</code> instead of <code>/cygdrive/c/</code>.}}
-{{Template:Documentation/Caution|Avoid trailing slashes in configure parameters. They sure cause problems for <code>--with-psdk-home</code>.}}
+{{Caution|Avoid trailing slashes in configure parameters. They sure cause problems for <code>--with-psdk-home</code>.}}
 {{Note|Paths to dependencies might be different for your installation. The pathes containing "msvc" and "msdk" should be self-explanatory.}}
 {{Tip|There are a number of options that you can use with the configure script. To display these options, type the following command:
 <pre>./configure --help</pre>}}
 {{Tip|If you run into problems with early DEV300 releases, check your settings in winenv.set.sh for <code>WINDOWS_VISTA_PSDK</code> to be set <code>TRUE</code>. This is important if <code>configure</code> fails to detect the Windows platform SDK version correctly. The detection failure results from the way how configure searches for the Vista PSDK in older releases: it will be found only if it is installed into the default location.}}
-{{Template:Documentation/Caution|If you run into problems compiling on an "Express Edition" (such as <tt>Cannot open include files: 'atlbase.h': No such files or directory</tt>), check your settings in winenv.set.sh for <code>DISABLE_ATL</code>, <code>DISABLE_ACTIVEX</code>: all have to be set <code>TRUE</code>. Visual Studio Express compilers do not contain everything needed to build the OOo ActiveX control, OLE automation and native Windows OLE support, so disable support for them via <code>--disable-atl --disable-activex</code>. A "complete" Visual Studio (no “Express” version) is not limited in that way.}}
+{{Caution|If you run into problems compiling on an "Express Edition" (such as <tt>Cannot open include files: 'atlbase.h': No such files or directory</tt>), check your settings in winenv.set.sh for <code>DISABLE_ATL</code>, <code>DISABLE_ACTIVEX</code>: all have to be set <code>TRUE</code>. Visual Studio Express compilers do not contain everything needed to build the OOo ActiveX control, OLE automation and native Windows OLE support, so disable support for them via <code>--disable-atl --disable-activex</code>. A "complete" Visual Studio (no “Express” version) is not limited in that way.}}
 {{Tip|As DirectX is not needed for most developers, its SDK consumes a lot of disk space and is prone to incompatibilities I recommend to build without DirecX support by using <code>--disable-directx</code> as shown above. Otherwise you have to provide the path to the SDK in <code>--with-directx-home</code>.}}
 {{Tip|OOo uses some Mozilla components. It is not possible to build them from the sources using the Visual Studio 2005 compiler. Disabling the Mozilla components with <code>--disable-mozilla</code> completely currently does might not work due to a bug in the module dependencies.}}
@@ Line 327: / Line 327: @@
   build && deliver
-A simple <code>build</code> in <code>$SRC_ROOT/instsetoo_native</code> will recreate the installation sets, provided all other modules have already been build.<ref name="Foot9">{{Documentation/Caution|<code>build --all</code> would rebuild changed/missing files. However, it does not check for incompatible modules. If unsure, use <code>build --from --prepare</code>.}}</ref>
+A simple <code>build</code> in <code>$SRC_ROOT/instsetoo_native</code> will recreate the installation sets, provided all other modules have already been build.<ref name="Foot9">{{Caution|<code>build --all</code> would rebuild changed/missing files. However, it does not check for incompatible modules. If unsure, use <code>build --from --prepare</code>.}}</ref>
 = Building a Module with Debug Information =
@@ Line 364: / Line 364: @@
 If you set the environment variable <code>nodep</code> to <code>TRUE</code>, then dependendy information files are not created - the build finishes faster.
-{{Template:Documentation/Caution|But only enable that on a clean build. Once you have built OOo and then made modifications, unset the variable again to be on the safe side.}}
+{{Caution|But only enable that on a clean build. Once you have built OOo and then made modifications, unset the variable again to be on the safe side.}}
 '''NO_HIDS'''

@@ Line 14: / Line 14: @@
 For building OpenOffice.org Cygwin is needed, a Windows program that emulates a complete Unix command line environment. To use this document you need to be familiar with a command line, but you need not to be a UNIX shell wizard.
-{{Template:Documentation/Tip|If you have never used a Unix shell, you might want to take a look at the [http://tldp.org/LDP/GNU-Linux-Tools-Summary/html/index.html shell introduction at TLDP].}}
+{{Tip|If you have never used a Unix shell, you might want to take a look at the [http://tldp.org/LDP/GNU-Linux-Tools-Summary/html/index.html shell introduction at TLDP].}}
 {{Note|<code>$SRC_ROOT</code> will denote the directory in which the source code of OpenOffice.org is stored.}}
-{{Template:Documentation/Tip|You are advised to check the release notes for the release you are building to inform yourself about changes since previous releases.}}
+{{Tip|You are advised to check the release notes for the release you are building to inform yourself about changes since previous releases.}}
 = Requirements =
@@ Line 96: / Line 96: @@
 === adding required files to the build tree ===
-{{Template:Documentation/Tip|Some of the files can be found in a suitable OOo installation set also, so you can save the download by “stealing” it from your OOo installation.}}
+{{Tip|Some of the files can be found in a suitable OOo installation set also, so you can save the download by “stealing” it from your OOo installation.}}
 {{Note|OOo uses some Mozilla libraries. Building the corresponding sources is only possible with the VC2003 compiler so you have to use precompiled libraries that require the msvx71 libraries mentioned above. On Windows the Mozilla libraries are needed only for Mozilla address book support. Unfortunately a bug in the module dependencies makes it necessary that the Mozilla libaries are used anyway as otherwise building the module <tt>xmlsecurity</tt> fails (see below).}}
@@ Line 256: / Line 256: @@
 {{Template:Documentation/Caution|Avoid trailing slashes in configure parameters. They sure cause problems for <code>--with-psdk-home</code>.}}
 {{Note|Paths to dependencies might be different for your installation. The pathes containing "msvc" and "msdk" should be self-explanatory.}}
-{{Template:Documentation/Tip|There are a number of options that you can use with the configure script. To display these options, type the following command:
+{{Tip|There are a number of options that you can use with the configure script. To display these options, type the following command:
 <pre>./configure --help</pre>}}
-{{Template:Documentation/Tip|If you run into problems with early DEV300 releases, check your settings in winenv.set.sh for <code>WINDOWS_VISTA_PSDK</code> to be set <code>TRUE</code>. This is important if <code>configure</code> fails to detect the Windows platform SDK version correctly. The detection failure results from the way how configure searches for the Vista PSDK in older releases: it will be found only if it is installed into the default location.}}
+{{Tip|If you run into problems with early DEV300 releases, check your settings in winenv.set.sh for <code>WINDOWS_VISTA_PSDK</code> to be set <code>TRUE</code>. This is important if <code>configure</code> fails to detect the Windows platform SDK version correctly. The detection failure results from the way how configure searches for the Vista PSDK in older releases: it will be found only if it is installed into the default location.}}
 {{Template:Documentation/Caution|If you run into problems compiling on an "Express Edition" (such as <tt>Cannot open include files: 'atlbase.h': No such files or directory</tt>), check your settings in winenv.set.sh for <code>DISABLE_ATL</code>, <code>DISABLE_ACTIVEX</code>: all have to be set <code>TRUE</code>. Visual Studio Express compilers do not contain everything needed to build the OOo ActiveX control, OLE automation and native Windows OLE support, so disable support for them via <code>--disable-atl --disable-activex</code>. A "complete" Visual Studio (no “Express” version) is not limited in that way.}}
-{{Template:Documentation/Tip|As DirectX is not needed for most developers, its SDK consumes a lot of disk space and is prone to incompatibilities I recommend to build without DirecX support by using <code>--disable-directx</code> as shown above. Otherwise you have to provide the path to the SDK in <code>--with-directx-home</code>.}}
+{{Tip|As DirectX is not needed for most developers, its SDK consumes a lot of disk space and is prone to incompatibilities I recommend to build without DirecX support by using <code>--disable-directx</code> as shown above. Otherwise you have to provide the path to the SDK in <code>--with-directx-home</code>.}}
-{{Template:Documentation/Tip|OOo uses some Mozilla components. It is not possible to build them from the sources using the Visual Studio 2005 compiler. Disabling the Mozilla components with <code>--disable-mozilla</code> completely currently does might not work due to a bug in the module dependencies.}}
+{{Tip|OOo uses some Mozilla components. It is not possible to build them from the sources using the Visual Studio 2005 compiler. Disabling the Mozilla components with <code>--disable-mozilla</code> completely currently does might not work due to a bug in the module dependencies.}}
-{{Template:Documentation/Tip|If you experiment with the newest sources, mind that it can happen sometimes that <code>configure.in</code> was updated, but it was forgotten to update configure too. The configure script itself is created from <code>configure.in</code> using the <code>autoreconf</code> command. The perl script <code>set_soenv</code> is created when you run configure from <code>set_soenv.in</code>.}}
+{{Tip|If you experiment with the newest sources, mind that it can happen sometimes that <code>configure.in</code> was updated, but it was forgotten to update configure too. The configure script itself is created from <code>configure.in</code> using the <code>autoreconf</code> command. The perl script <code>set_soenv</code> is created when you run configure from <code>set_soenv.in</code>.}}
-{{Template:Documentation/Tip|csc.exe comes from the <code>c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322</code> directory, you might need <code>--with-csc-path</code>.}}
+{{Tip|csc.exe comes from the <code>c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322</code> directory, you might need <code>--with-csc-path</code>.}}
-{{Template:Documentation/Tip|If you fail to getting together a working installation of Cygwin, one possibility is to use a known-to-work combination of Cygwin packages, i.e. a direct copy of some other user's Cygwin tree. [[User:TorLillqvist]] has such a tree (from late 2006) zipped up at http://download.go-oo.org/tstnvl/tml/tml-cygwin.zip . Don't hesitate to ask for advice if necessary.}}
+{{Tip|If you fail to getting together a working installation of Cygwin, one possibility is to use a known-to-work combination of Cygwin packages, i.e. a direct copy of some other user's Cygwin tree. [[User:TorLillqvist]] has such a tree (from late 2006) zipped up at http://download.go-oo.org/tstnvl/tml/tml-cygwin.zip . Don't hesitate to ask for advice if necessary.}}
 == bootstrap ==
@@ Line 300: / Line 300: @@
 There are some special things in the way how OOo builds its modules. Every module has an “output” folder (with some subfolders for the different kinds of generated output) that is created the first time a build is done in the module. The name of this folder is “wntmsci10.pro” for builds with MSVC++2003, “wntmsci11.pro” for builds with MSVC++2005 and "wntmsci12.pro" for builds with MSVC++2008 (for the meaning of the "pro" extension see below). After a successful build of a module some of the generated files are copied to the output folder of the “solver” module by executing a tool called “deliver” (this is automatically called by build --all for each of the modules). Other modules will take these “delivered” files (header files, libraries etc.) to resolve their dependencies. The content of the solver module will also be used to pack the installation sets in the final step.
-{{Template:Documentation/Tip|Using some not quite latest cygwin releases (1.5.18/1.5.19) can lead to tcsh freezing in places - the build will appear to hang. You can fix this by running ''ls /proc/$nnn/fd'' where $nnn is the number of the process. Or just run
+{{Tip|Using some not quite latest cygwin releases (1.5.18/1.5.19) can lead to tcsh freezing in places - the build will appear to hang. You can fix this by running ''ls /proc/$nnn/fd'' where $nnn is the number of the process. Or just run
 <pre>ls /proc/*/fd</pre>
 to "unhang" the process. See {{Bug|51560}} for more info...}}
@@ Line 339: / Line 339: @@
 Drop the newly created binaries into an existing installation. Building an installation set with them will not help, as binaries are stripped on packing by default.
-{{Template:Documentation/Tip|For details, see [[Windows Debugging]].}}
+{{Tip|For details, see [[Windows Debugging]].}}
 = Finding the Installation Sets =
 After a successful build you will find the OOo installation set in
@@ Line 347: / Line 347: @@
 “instsetoo_native” is the module that packs the installation set.
-{{Documentation/Tip|If you already have a version of OOo installed you can install your freshly built version in parallel by installing it with setup /a that just unpacks all files without any system registration.}}
+{{Tip|If you already have a version of OOo installed you can install your freshly built version in parallel by installing it with setup /a that just unpacks all files without any system registration.}}
 = Tips And Tricks =

@@ Line 16: / Line 16: @@
 {{Template:Documentation/Tip|If you have never used a Unix shell, you might want to take a look at the [http://tldp.org/LDP/GNU-Linux-Tools-Summary/html/index.html shell introduction at TLDP].}}
-{{Template:Documentation/Note|<code>$SRC_ROOT</code> will denote the directory in which the source code of OpenOffice.org is stored.}}
+{{Note|<code>$SRC_ROOT</code> will denote the directory in which the source code of OpenOffice.org is stored.}}
 {{Template:Documentation/Tip|You are advised to check the release notes for the release you are building to inform yourself about changes since previous releases.}}
@@ Line 46: / Line 46: @@
 | (default)
 |-
-| [http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-9BE5-FA919850BDBF&displaylang=en Windows SDK for Windows Server 2008]<ref name="Foot1">{{Template:Documentation/Note|This also supported on Vista. This is either a DVD image or a net installer. You can either mount the DVD with a suitable tool, burn it do a DVD or use tools like winrar that can extract files from ISO files directly. You don't need to install samples or documentation (saves a lot of disk space). It will also install the .NET Framework 3.5 SDK.
+| [http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-9BE5-FA919850BDBF&displaylang=en Windows SDK for Windows Server 2008]<ref name="Foot1">{{Note|This also supported on Vista. This is either a DVD image or a net installer. You can either mount the DVD with a suitable tool, burn it do a DVD or use tools like winrar that can extract files from ISO files directly. You don't need to install samples or documentation (saves a lot of disk space). It will also install the .NET Framework 3.5 SDK.
 It might be best to install the Windows SDK into the default directory, and if not that into one without capital letters in the path. I used D:\Dev\Win_SDK\ and received some linking errors in the Python module (see {{Bug|88568}}).}}</ref>
+|
@@ Line 53: / Line 53: @@
 | external/gdiplus
 |-
-| Only for OOo2.x but due to {{Bug|88652}} in configure still needed for 3.x: [http://download.microsoft.com/download/b/7/5/b75eace3-00e2-4aa0-9a6f-0b6882c71642/unicows.exe unicows.dll from (Microsoft Layer for Unicode)]<ref name="Foot2"> {{Template:Documentation/Note|unicows.dll is available from the Microsoft site and needs to be saved to $SRC_ROOT/external/unicows. Microsoft seems to enjoy changing the exact location of this file. You may have to search Microsoft's website.}}</ref>
+| Only for OOo2.x but due to {{Bug|88652}} in configure still needed for 3.x: [http://download.microsoft.com/download/b/7/5/b75eace3-00e2-4aa0-9a6f-0b6882c71642/unicows.exe unicows.dll from (Microsoft Layer for Unicode)]<ref name="Foot2"> {{Note|unicows.dll is available from the Microsoft site and needs to be saved to $SRC_ROOT/external/unicows. Microsoft seems to enjoy changing the exact location of this file. You may have to search Microsoft's website.}}</ref>
 | external/unicows
 |-
-| [http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=CD1FC4B2-0885-47F4-AF45-7FD5E14DB6C0 dbghelp.dll]<ref name="Foot3">{{Template:Documentation/Note|dbghelp.dll is available from the Microsoft site and needs to be saved to $SRC_ROOT/external/dbghelp. Microsoft seems to enjoy changing the exact location of this file. You may have to search Microsoft's website.}}</ref>
+| [http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=CD1FC4B2-0885-47F4-AF45-7FD5E14DB6C0 dbghelp.dll]<ref name="Foot3">{{Note|dbghelp.dll is available from the Microsoft site and needs to be saved to $SRC_ROOT/external/dbghelp. Microsoft seems to enjoy changing the exact location of this file. You may have to search Microsoft's website.}}</ref>
 | external/dbghelp
 |-
@@ Line 68: / Line 68: @@
 | external/msvcp90
 |-
-| for 2008 compiler starting with DEV300m23: Microsoft_VC90_CRT_x86.msm and policy_9_0_Microsoft_VC90_CRT_x86.msm for non debug builds and Microsoft_VC90_DebugCRT_x86.msm and policy_9_0_Microsoft_VC90_DebugCRT_x86.msm for debug builds<ref name="Foot4"> {{Template:Documentation/Note|You can find these files in your directory c:\program files\common files\merge modules}}</ref>
+| for 2008 compiler starting with DEV300m23: Microsoft_VC90_CRT_x86.msm and policy_9_0_Microsoft_VC90_CRT_x86.msm for non debug builds and Microsoft_VC90_DebugCRT_x86.msm and policy_9_0_Microsoft_VC90_DebugCRT_x86.msm for debug builds<ref name="Foot4"> {{Note|You can find these files in your directory c:\program files\common files\merge modules}}</ref>
 . These merge modules are available in VS08 Express Edition and VS08 Professional Edtion. All *.msm files are located at c:\Program Files\Common Files\Merge Module.
 | external/msm90
@@ Line 83: / Line 83: @@
 | external/msvcp71
 |-
-| optional: [http://nsis.sourceforge.net/ Nullsoft Scriptable Install System (NSIS)]<ref name="Foot5">{{Template:Documentation/Note|If NSIS is available, a self contained Windows installer is created in addition to the MSI installer files.}}
+| optional: [http://nsis.sourceforge.net/ Nullsoft Scriptable Install System (NSIS)]<ref name="Foot5">{{Note|If NSIS is available, a self contained Windows installer is created in addition to the MSI installer files.}}
 {{Template:Documentation/Caution|It used to be that newer version of NSIS broke the build (see {{Bug|85657}}), but it seems that it now works for NSIS up to 2.3.7.}}</ref>
+|
 |-
-| optional: [http://msdn.microsoft.com/directx/directxdownloads/ Microsoft DirectX SDK]<ref name="Foot6"> {{Template:Documentation/Note|If you don't want to download it you can disable DirectX support in the configuration step (<code>--disable-directx</code>).}}
+| optional: [http://msdn.microsoft.com/directx/directxdownloads/ Microsoft DirectX SDK]<ref name="Foot6"> {{Note|If you don't want to download it you can disable DirectX support in the configuration step (<code>--disable-directx</code>).}}
 {{Template:Documentation/Caution|Current (as of 2008/01) versions of the DirectX9 SDK and Windows Platform SDK do not fit to each other. To be able to build with DirextX enabled, you need to patch one file in the Platform SDK. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID2743771 for details.}}
@@ Line 98: / Line 98: @@
 {{Template:Documentation/Tip|Some of the files can be found in a suitable OOo installation set also, so you can save the download by “stealing” it from your OOo installation.}}
-{{Template:Documentation/Note|OOo uses some Mozilla libraries. Building the corresponding sources is only possible with the VC2003 compiler so you have to use precompiled libraries that require the msvx71 libraries mentioned above. On Windows the Mozilla libraries are needed only for Mozilla address book support. Unfortunately a bug in the module dependencies makes it necessary that the Mozilla libaries are used anyway as otherwise building the module <tt>xmlsecurity</tt> fails (see below).}}
+{{Note|OOo uses some Mozilla libraries. Building the corresponding sources is only possible with the VC2003 compiler so you have to use precompiled libraries that require the msvx71 libraries mentioned above. On Windows the Mozilla libraries are needed only for Mozilla address book support. Unfortunately a bug in the module dependencies makes it necessary that the Mozilla libaries are used anyway as otherwise building the module <tt>xmlsecurity</tt> fails (see below).}}
-{{Template:Documentation/Note|The default cygwin version offered on http://www.cygwin.com/ now is 1.7.x. For current milestones it is recommended to use this version as it fixes the .dll remapping probelm (see below) and is required for builds on Windows 7. If you need to build old versions of the source code, check out http://www.cygwin.com/win-9x.html}}
+{{Note|The default cygwin version offered on http://www.cygwin.com/ now is 1.7.x. For current milestones it is recommended to use this version as it fixes the .dll remapping probelm (see below) and is required for builds on Windows 7. If you need to build old versions of the source code, check out http://www.cygwin.com/win-9x.html}}
 = Installation and Preparation of Build Tools =
@@ Line 139: / Line 139: @@
 ** wget
-{{Template:Documentation/Note|The installer will automatically check and download some more packages needed by thosed listed here. The whole process takes roughly 20 minutes.}}
+{{Note|The installer will automatically check and download some more packages needed by thosed listed here. The whole process takes roughly 20 minutes.}}
 === breaking links to executables ===
@@ Line 177: / Line 177: @@
 CPAN will detect if a selected module depends on other modules and it will offer to download them also. As explained please just confirm this.
-{{Template:Documentation/Note|The last three modules are only needed if you want to use the cws tooling. These tools are necessary if you want to create and maintain your own [http://wiki.services.openoffice.org/wiki/CWS Child Workspaces] or if you want to build one of them. I recommend to install them anyway as sooner or later you want to work on a child workspace.}}
+{{Note|The last three modules are only needed if you want to use the cws tooling. These tools are necessary if you want to create and maintain your own [http://wiki.services.openoffice.org/wiki/CWS Child Workspaces] or if you want to build one of them. I recommend to install them anyway as sooner or later you want to work on a child workspace.}}
 {{Template:Documentation/Caution|I got an error message from CPAN somewhat like the following:
@@ Line 255: / Line 255: @@
 {{Template:Documentation/Caution|Beware of using <code>/c/</code> instead of <code>/cygdrive/c/</code>.}}
 {{Template:Documentation/Caution|Avoid trailing slashes in configure parameters. They sure cause problems for <code>--with-psdk-home</code>.}}
-{{Template:Documentation/Note|Paths to dependencies might be different for your installation. The pathes containing "msvc" and "msdk" should be self-explanatory.}}
+{{Note|Paths to dependencies might be different for your installation. The pathes containing "msvc" and "msdk" should be self-explanatory.}}
 {{Template:Documentation/Tip|There are a number of options that you can use with the configure script. To display these options, type the following command:
 <pre>./configure --help</pre>}}
@@ Line 271: / Line 271: @@
   ./bootstrap
-{{Template:Documentation/Note|1=Starting with DEV300m77, the sources for external modules (e.g. libxml2) were moved out of the source repository. The bootstrap step will now create a directory called "ext_sources" beside the repository and populate it with the required file via HTTP.
+{{Note|1=Starting with DEV300m77, the sources for external modules (e.g. libxml2) were moved out of the source repository. The bootstrap step will now create a directory called "ext_sources" beside the repository and populate it with the required file via HTTP.
 If need to change that behavior, checkout the configure switches
   --with-external-tar=<TARFILE PATH>  : Specify path to tarfiles manually
@@ Line 278: / Line 278: @@
 == setting the enviroment ==
-When the configure script has been run successfully a file <code>winenv.Set.sh</code> was created<ref name="Foot7">{{Template:Documentation/Note|When you want to use tcsh instead of bash, you will need to use the file <code>winenv.Set</code> instead:
+When the configure script has been run successfully a file <code>winenv.Set.sh</code> was created<ref name="Foot7">{{Note|When you want to use tcsh instead of bash, you will need to use the file <code>winenv.Set</code> instead:
 <pre> source winenv.Set
   rehash</pre>
@@ Line 288: / Line 288: @@
 == starting the build ==
-Build the software by typing the following in <code>$SRC_ROOT</code><ref name="Foot8">{{Template:Documentation/Note|You can also run:
+Build the software by typing the following in <code>$SRC_ROOT</code><ref name="Foot8">{{Note|You can also run:
 <pre>make</pre>
 but GNU/make will just start dmake. You can also run the following in the <code>instetoo_native</code> module:
@@ Line 310: / Line 310: @@
 * incompatible
 Only do compatible partial builds if you know exactly what you are doing.
-{{Documentation/Note|For more information, see [[Compatible Builds]].}}
+{{Note|For more information, see [[Compatible Builds]].}}
 == rebuilding from a module (incompatible build) ==
@@ Line 421: / Line 421: @@
 = See Also =
-{{Template:Documentation/Note|For more information on building OOo on Windows see:
+{{Note|For more information on building OOo on Windows see:
 * [[Building on Windows (older releases)]]
 * [[CPAN_install| Perl modules installation with CPAN]]

← Older revision		Revision as of 07:16, 22 August 2011
Line 5:		Line 5:

	{{DISPLAYTITLE:Building on Windows}}		{{DISPLAYTITLE:Building on Windows}}
−	~~[[Category:Windows]]~~

	__TOC__		__TOC__