Hi, sorry for the late answer but different things prevented me from continuing with my OOo build experiments. So first of all I would like to thank you all again for your help so far.
Sadly I couldn't really solve my problem with the information you provided. I checked and the CVER environment variable is indeed set to "M1500", so there shouldn't be a problem. Looking at the log files after the build I can also see that some stuff happens with the merge modules Microsoft_VC90_CRT_x86.msm and policy_9_0_Microsoft_VC90_CRT_x86.msm. I can't say that I fully understand how it's supposed to work with these merge modules but I can see a lot of lines indicating "success" in regards to the above mentioned merge modules in the log file and nothing that seems to indicate that something went wrong. Also, after the build, when looking inside the instsetoo_native folder I find the folders wntmsci12.pro\OpenOffice\msi\mergefiles\en-US\gid_Mergemodule_Microsoft_Vc90_Crt_X86 and wntmsci12.pro\OpenOffice\msi\mergefiles\en-US\gid_Mergemodule_Policy_Microsoft_Vc90_Crt_X86 containing a lot of stuff which also to me seems to indicate that at least _something_ happened with these merge modules. So the problem is probably not that the merge modules weren't found or the build didn't do anything with them. Again, I don't fully understand how it's supposed to work, though. Also, looking at the contents of instsetoo_native\wntmsci12.pro\OpenOffice\msi\install\en-US\openofficeorg1.cab I see it contains the following files: msvcm90.dll.30729.01.Microsoft_VC90_CRT_x86.SP.D8D85FD0_537C_3A3A_9BEC_7A1B426637EC msvcp90.dll.30729.01.Microsoft_VC90_CRT_x86.SP.D8D85FD0_537C_3A3A_9BEC_7A1B426637EC msvcr90.dll.30729.01.Microsoft_VC90_CRT_x86.SP.D8D85FD0_537C_3A3A_9BEC_7A1B426637EC So in some form the dlls I'm missing when using my installation set _are_ contained in it. They just aren't installed when I execute the installer. I really don't know where to go from here. If someone could point me in the right direction where the problem could possibly be that would be a great help. Maybe something I can look for in the log files? When comparing my openofficeorg1.cab to one of an installation set downloaded from openoffice.org I noticed that the version of my msvc*90.dll files is greater than the one packaged there. That's probably because I used the merge modules from MS Visual C++ 2008 Express with Service Pack 1. Could the version of Visual C++ 2008 Express I use be a cause of my problem? Any help would be appreciated. Regards, Daniel On Wed, Nov 25, 2009 at 4:34 PM, Oliver Bolte <oliver.bo...@sun.com> wrote: > Ingo Schmidt-Rosbiegal wrote: >> >> On 11/25/09 15:47, Stephan Bergmann wrote: >>> >>> On 11/25/09 15:28, Daniel B. wrote: >>>> >>>> On Fri, Nov 13, 2009 at 3:04 PM, Stephan Bergmann >>>> <stephan.bergm...@sun.com> wrote: >>>>> >>>>> On 11/12/09 14:04, Daniel B. wrote: >>>>>> >>>>>> I'm trying to build OOo on Windows using the instructions from the >>>>>> Building Guide in the wiki >>>>>> >>>>>> (http://wiki.services.openoffice.org/wiki/Documentation/Building_Guide). >>>>>> >>>>>> Everything works fine so far, but I noticed that the installation sets >>>>>> that my build produces are missing the redist-directory that should >>>>>> contain the MS Visual C++ redistributable package (vcredist_x86.exe). >>>>>> Consequently when I install my build on a system that doesn't already >>>>>> have msvcp90.dll and msvcr90.dll installed OOo won't work. Just >>>>>> creating the redist-directory inside the installation set and copying >>>>>> the vcredist_x86.exe file into it doesn't work. My installer doesn't >>>>>> trigger the installation of the Visual C++ redistributables. >>>>>> >>>>>> So, my question is how do I build an installation set which contains >>>>>> the redist-directory with the vcredist_x86.exe file, so that the OOo >>>>>> installation will install the necessary libraries? >>>>>> >>>>>> While searching for an answer I found out that there's an environment >>>>>> variable WITH_VC_REDIST which you can set to TRUE and then the build >>>>>> seems to create the redist directory and tries to copy the >>>>>> vcredist_x86.exe from somewhere but I don't know where the build >>>>>> process expects the necessary files. Can anyone help me out? >>>>> >>>>> My understanding is that in general OOo installation sets on Windows >>>>> bring >>>>> with them the MSVC90 CRT files as .msm files >>>>> (scp2/source/ooo/mergemodules_ooo.scp) and that the additional >>>>> vcredist_x86.exe is only actually used during update installation on >>>>> Vista, >>>>> to work around some specific problem (scp2/source/ooo/vc_redist.scp). >>>> >>>> >>>> Thank you for your reply, Stephan! Looks like I misunderstood the >>>> purpose of the vcredist_x86.exe, then. >>>> >>>> Anyway, the problem remains. The installation set I build still >>>> doesn't install the files msvcp90.dll and msvcr90.dll, so that >>>> OpenOffice.org won't run on a system which hasn't already installed >>>> these files. The normal installer DOES install these files so it must >>>> be some problem with my build but I have no idea what exactly went >>>> wrong. I did copy the .msm files that are mentioned on >>>> >>>> http://wiki.services.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows >>>> to the external/msm90 folder but that's obviously not enough. >>>> Can anyone point me in the right direction what the problem could be? >>> >>> I vaguely remember that whether you are allowed to re-distribute those >>> files depends on the MS compiler version (Express vs. full), so there might >>> be some conditional section in our code base causing the stuff not to be >>> included in your build. Ingo (on cc) probably knows more. >>> >>> -Stephan >> >> Hello, >> >> what means the "normal installer" does install these files? >> In OOo 3.0, OOo 3.1 and OOo 3.2 the msvc runtime libraries are included >> into the product using MS MergeModules (msm files). Additionally there is a >> vcredist_x86.exe, but this is only required for Major Upgrades on Windows >> Vista. Therefore this is probably not required by you. >> Looking into the code in scp2/source/ooo/mergemodules_ooo.scp, you can see >> that the Merge Modules are only included into the product, if "#ifdef M1500" >> is true. >> Oliver (on cc) probably knows more about M1500. >> By the way. We want to remove the MergeModules for OOo 3.3, because they >> are no longer supported by MS. They have problems to deliver patches for >> this files in the MergeModules, because every application that includes this >> MergeModules is responsible for delivering patches for this files. So MS >> cannot deliver patches for their files, if other products include them. >> Therefore we are forced, to add all versions of vcredist into our >> installation sets in the future. And we have to use them always, not only >> for Upgrades on Windows Vista. >> >> Ingo >> > Hi, > > M1500 is a define for the Visual Studio 2008 compiler. > In file set_soenv.in you'll find this code snippet: > > -------------------------------------------------------------- > if ( "@COMEX@" eq "10" ) { # .NET 2003 needs M1310 > $CVER = "M1310"; > $ATL_LIB = $COMPATH.$ds."atlmfc".$ds."lib"; > $ATL_INCLUDE = $COMPATH.$ds."atlmfc".$ds."include"; > $MFC_LIB = ""; > $MFC_INCLUDE = ""; > } elsif ( "@COMEX@" ge "11" ) { # .NET 2005 needs M1400 > if ( "@COMEX@" eq "11" ) { > $CVER = "M1400"; > } elsif ( "@COMEX@" eq "12" ) { > $CVER = "M1500"; > } else { # Unsupported > die "Unsupported value for COMEX variable.\n"; > } > -------------------------------------------------------------- > > HTH > Oliver > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.org > For additional commands, e-mail: dev-h...@openoffice.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
