Information about work to build 2 with MingGW is at issue 53572, issue 71986, issue 82653, issue 83133 Using vanilla source Information about work to build with MinGW is at issue 24588 however this mostly deals with 1.1 at the moment. MinGW is not supported for building at the moment. Using the Cygwin compiler with the -mno-cygwin switch in theory does the same, but unless one is very careful it is easy to get into a mess when using a Cygwin environment to build pure Win32 binaries. No POSIX emulation layer as Cygwin is involved. MinGW is gcc and GNU binutils targeted for Windows, producing plain Win32 executables. In fact I would guess the config options below will probably work for a vanilla build also ( maybe someone will try that and add any extra info/steps here ). See steps for using this compiler in the Windows#Using ooo-build section below. So, the great news is it's possible to build with a free Microsoft tool-chain. Visual C 2005 Express the FREE (as in free beer) Microsoft compiler is now supported for Windows builds. In the section for the Express compiler, but it hasn't been tested. The other steps should be the same as described The -disable-activex switch in the configure step is not needed for Setting the environment variable WINDOWS_VISTA_PSDK=TRUE will help. When using the Vista SDK Windows#Building_with_Windows_Vista_SDK It may help to set the environment variable PROF_EDITION=TRUEīy hand. The necessary changes for configure haven't been made, yet. Visual Studio Express 2008 with SP1 also works. Note that jdk-1.6 works if you don't want to use 1.4.2. If you run into problems, check your settings in for WINDOWS_VISTA_PSDK, DISABLE_ATL, DISABLE_ACTIVEX with-psdk-home="/cygdrive/c/Program Files/Microsoft SDKs/Windows/v6.1"Ĭonfigure changes have been made now (CWS vq41), available with milestone DEV300_m6 with-asm-home="/cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/Bin" with-frame-home="/cygdrive/c/Program Files/Microsoft SDKs/Windows/v6.1" with-csc-path="/cygdrive/c/WINDOWS/Microsoft.NET/Framework/v3.5" with-midl-path="/cygdrive/c/Program Files/Microsoft SDKs/Windows/v6.1/Bin" with-cl-home="/cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC" configure -disable-build-mozilla -disable-activex -with-win32 The settings for -with-psdk-home are case sensitive!. Windows (not internal) OLE completely and some other functionality. Setting DISABLE_ATL=TRUE after the configure step helps for building but disables The environment variable WINDOWS_VISTA_PSDK=TRUE needs to be set.Ĭurrently OOo isn't completely buildable with Visual Studio 2008 Express and Windows Server 2008 SDKĭue to missing ATL header / libs (these used to be shipped with the 2003 SDK, but the 2003 SDK cannot be used with VS2008). You can find these files in your directory c:\program files\common files\merge modules * Microsoft_VC90_CRT_x86.msm, Microsoft_VC90_DebugCRT_x86.msm, * Platform SDK Redistributable: Dbghelp.dll * or alternatively, the Standard or better version of VS 2008 The compiler has been released in November 2007. See BuildingMSVCStandardįor how to tune the MS IDE into coding OOo efficiently, see this page. Standard does not support optimizations so suddenly these beasts get out in the open. The problem is that OO.o enables /O flags in Professional that conveniently cripples the compiler enough to hide some ugly hacks and bugs that have crept in over the years. You can use the Standard version of Visual Studio to build OpenOffice but there are certain workarounds needed. This is a tag to remove these notes and the page at some future point. NB: These fixes have been rolled into more recent milestones, so you should now be able to happily build using standard. When installing, unless you need them otherwise, there is no need to install the Visual Basic, C#, J#, or. NET 2003 is the official one used to build. The C compiler included in Visual Studio. NET 2005 (including the "Express" version) for the dev300 code line. NET 2003 for all code 2.x code branches and Visual C . While real hackers prefer Free software, if you're forced to build stuff for Windows, this is the place to be.ĭifferent compilers that can or can not be used to build are documented below. Most of this wiki assumes that you'll be using a reasonably current Linux system, as a time saving feature. If it ends up being complete, this notice can be removed! At the moment you'll have to piece together information from other pages with the changes here for doing it on Windows. This is an initial attempt to fill out information for building on Windows. 4.2 ooo-build with Visual C 2005 Express.1 Welcome to OOo development for Windows.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |