Re: building on Windows 10 breaks at guistdio.exe
On 9/20/2016 12:56 AM, John D'Orazio wrote: On Tue, Sep 20, 2016 at 7:50 AM, Ariel Constenla-Haile wrote: On Mon, Sep 19, 2016 at 07:12:29PM -0700, Patricia Shanahan wrote: 4.1.3 does have changes to the language library URLs. Has anyone else done a build that included Italian? His logs say aoo-trunk, so I assume John isn't building branch AOO413. NSIS >= 3.* is only on that branch. In fact I followed the instructions I found at https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7.2C_Windows_8.1.2C_Windows_10 - Check out source from Apache SVN repository svn co https://svn.apache.org/repos/asf/openoffice/trunk aoo-trunk cd aoo-trunk/main So yes I am evidently building from aoo-trunk. I'll update the wiki with the info about NSIS >= 3.* being compatible only with the AOO413 branch. Next person to edit the step-by-step should add a note clarifying the checkout. Specifically, replace "trunk" with "branches/AOO413" to get the 4.1.3 source. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: building on Windows 10 breaks at guistdio.exe
On Tue, Sep 20, 2016 at 7:50 AM, Ariel Constenla-Haile wrote: > On Mon, Sep 19, 2016 at 07:12:29PM -0700, Patricia Shanahan wrote: > > 4.1.3 does have changes to the language library URLs. Has anyone else > done a > > build that included Italian? > > His logs say aoo-trunk, so I assume John isn't building branch AOO413. > NSIS >= 3.* is only on that branch. > > In fact I followed the instructions I found at https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7.2C_Windows_8.1.2C_Windows_10 - Check out source from Apache SVN repository svn co https://svn.apache.org/repos/asf/openoffice/trunk aoo-trunk cd aoo-trunk/main So yes I am evidently building from aoo-trunk. I'll update the wiki with the info about NSIS >= 3.* being compatible only with the AOO413 branch. > Regards > -- > Ariel Constenla-Haile > -- don John R. D'Orazio
Re: building on Windows 10 breaks at guistdio.exe
On Tue, Sep 20, 2016 at 7:44 AM, Ariel Constenla-Haile wrote: > On Tue, Sep 20, 2016 at 03:22:40AM +0200, John D'Orazio wrote: > > I wound up building in stages, since the build was breaking here and > there. > > I just picked it up from where it left off as I fixed things. So I don't > > have a single output... unless there is a log file that collects various > > build stages together into one single output? > > I would also recommend installing as many packages in cygwin as possible > > without going through the extra step of installing lynx or apt-cyg... > While > > that does make the environment more similar to a linux build environment, > > it's still an extra step and I believe it could be indicated as a second > > possibliity. Somewhere in the Step by Step guide I added which packages > to > > choose in the cygwin interface if installing them from the cygwin > > interface. I think installing the packages from the cygwin interface > should > > be indicated as the first step to take when first installing cygwin, > adding > > all the necessary packages along with the first install. > > The only package I couldn't find from the cygwin interface was the Perl > > LWP::UserAgent package, so I installed that using "cpan -i > LWP::UserAgent". > > That is perl-LWP-Protocol-https, please see the updated version of > https://wiki.openoffice.org/wiki/Documentation/Building_ > Guide_AOO#General_Build_Requirements Yes in fact I saw that right after my last message and I've already updated https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7.2C_Windows_8.1.2C_Windows_10 The process indicated in this last page should be a lot cleaner now I believe. > Regards > -- > Ariel Constenla-Haile -- John R. D'Orazio
Re: building on Windows 10 breaks at guistdio.exe
On Mon, Sep 19, 2016 at 07:12:29PM -0700, Patricia Shanahan wrote: > 4.1.3 does have changes to the language library URLs. Has anyone else done a > build that included Italian? His logs say aoo-trunk, so I assume John isn't building branch AOO413. NSIS >= 3.* is only on that branch. Regards -- Ariel Constenla-Haile signature.asc Description: Digital signature
Re: building on Windows 10 breaks at guistdio.exe
On Tue, Sep 20, 2016 at 03:22:40AM +0200, John D'Orazio wrote: > I wound up building in stages, since the build was breaking here and there. > I just picked it up from where it left off as I fixed things. So I don't > have a single output... unless there is a log file that collects various > build stages together into one single output? > I would also recommend installing as many packages in cygwin as possible > without going through the extra step of installing lynx or apt-cyg... While > that does make the environment more similar to a linux build environment, > it's still an extra step and I believe it could be indicated as a second > possibliity. Somewhere in the Step by Step guide I added which packages to > choose in the cygwin interface if installing them from the cygwin > interface. I think installing the packages from the cygwin interface should > be indicated as the first step to take when first installing cygwin, adding > all the necessary packages along with the first install. > The only package I couldn't find from the cygwin interface was the Perl > LWP::UserAgent package, so I installed that using "cpan -i LWP::UserAgent". That is perl-LWP-Protocol-https, please see the updated version of https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO#General_Build_Requirements Regards -- Ariel Constenla-Haile signature.asc Description: Digital signature
Re: building on Windows 10 breaks at guistdio.exe
Sorry, "output" was ambiguous. I'm not interested in the log files at this time, but in the installation files. I want to try to install the result of your build on a Windows 7 machine. On 9/19/2016 6:22 PM, John D'Orazio wrote: I wound up building in stages, since the build was breaking here and there. I just picked it up from where it left off as I fixed things. So I don't have a single output... unless there is a log file that collects various build stages together into one single output? I would also recommend installing as many packages in cygwin as possible without going through the extra step of installing lynx or apt-cyg... While that does make the environment more similar to a linux build environment, it's still an extra step and I believe it could be indicated as a second possibliity. Somewhere in the Step by Step guide I added which packages to choose in the cygwin interface if installing them from the cygwin interface. I think installing the packages from the cygwin interface should be indicated as the first step to take when first installing cygwin, adding all the necessary packages along with the first install. The only package I couldn't find from the cygwin interface was the Perl LWP::UserAgent package, so I installed that using "cpan -i LWP::UserAgent". On Tue, Sep 20, 2016 at 12:25 AM, Patricia Shanahan wrote: Congratulations! I'm about to do a Windows 10 build on a new machine, so please make sure the step-by-step incorporates all that you learned in the process. I have a specific test I would like run. The current release process calls for doing the Windows builds on Windows 7. I am wondering if that is necessary. Could you test your Windows 10 build on a Windows 7 machine? Or send me the output - that may be quicker than waiting for my Windows 10 build to go through. On 9/19/2016 1:46 PM, John D'Orazio wrote: I have now successfully completed the build on Windows 10, and after changing the install path of NSIS to one without spaces, packaging also completed successfully. I have added "Windows 10" alongside "Windows 7" and "Windows 8.1" in the Step by Step guide. On Mon, Sep 19, 2016 at 7:50 PM, Patricia Shanahan wrote: I had installed 64-bit Cygwin installed here before I started on compiling AOO. I hit problems, and had to go to the recommended 32-bit Cygwin. However, things have changed a bit since then, so it may be worth seeing if it works. On 9/19/2016 8:59 AM, John D'Orazio wrote: ... I also read somewhere that maybe using 64 bit cygwin can resolve the occupied addresses and child_fork_process errors. I made an attempt at getting the build environment ready in 64 bit cygwin but configure is complaining about not finding Visual Studio C++, while this does not happen in 32 bit cygwin (I'm passing in the with-cl-home flag so it shouldn't have any problem finding it... I'm reading it has something to do with registry keys, idk I have to look into this better). ... - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: building on Windows 10 breaks at guistdio.exe
4.1.3 does have changes to the language library URLs. Has anyone else done a build that included Italian? On 9/19/2016 6:33 PM, John D'Orazio wrote: I actually did see an error in the packaging phase, but it didn't seem to affect the final output, I still got the setup.exe which worked just fine, and I can open and use soffice.exe just fine after running setup. This is the error I got: ERROR: The following errors occurred in packaging process: 273.923309 : ERROR: D:/NSIS/makensis.exe D:/source/aoo-trunk/main/instsetoo_native/ wntmsci12.pro/Apache_OpenOffice/msi/nsis/it/downloadtemplate.nsi | ! 273.923514 : !include: error in script: "D:/source/aoo-trunk/main/instsetoo_native/ wntmsci12.pro/Apache_OpenOffice/msi/nsis/it\Italian_pack.nsh" on line 10 273.923550 : Error in macro LANGFILE_INCLUDE on macroline 11 273.923588 : Error in macro MUI_LANGUAGE_PACK on macroline 12 273.923619 : Error in script "D:/source/aoo-trunk/main/instsetoo_native/ wntmsci12.pro/Apache_OpenOffice/msi/nsis/it/downloadtemplate.nsi" on line 270 -- aborting creation process Not sure what that might affect. Also, here are my final working configure settings: SDK_PATH="D:\Microsoft_SDKs\Windows\v7.0" ./configure --with-build-version="$(date +"%Y-%m-%d %H:%M:%S (%a, %d %b %Y)")" --with-directx-home="D:\Microsoft_DirectX_SDK_June_2010" --with-frame-home="D:/Microsoft_SDKs/Windows/v7.0" --with-psdk-home="D:/Microsoft_SDKs/Windows/v7.0" --with-midl-path="D:/Microsoft_SDKs/Windows/v7.0/bin" --with-ant-home="/cygdrive/d/apache-ant/apache-ant-1.9.7" --with-nsis-path="D:/NSIS" --with-jdk-home="C:/PROGRA~2/Java/JDK18~1.0_7" --with-csc-path="C:/Windows/Microsoft.NET/Framework/v3.5" --with-cl-home="C:/PROGRA~2/MI1DCA~1.0/VC" --with-asm-home="C:/PROGRA~2/MI1DCA~1.0/VC/bin" --with-mozilla-build="/cygdrive/d/mozilla-build" --with-atl-include-dir=/cygdrive/c/WinDDK/7600.16385.1/inc/atl71 --with-atl-lib-dir=/cygdrive/c/WinDDK/7600.16385.1/lib/ATL/i386 --with-mfc-include-dir=/cygdrive/c/WinDDK/7600.16385.1/inc/mfc42 --with-mfc-lib-dir=/cygdrive/c/WinDDK/7600.16385.1/lib/Mfc/i386 --with-dmake-url=" http://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2"; --with-epm-url=" https://sourceforge.net/projects/oooextras.mirror/files/epm-3.7.tar.gz"; --without-junit --without-stlport --enable-win-x64-shellext --enable-wiki-publisher --enable-category-b --enable-bundled-dictionaries --with-lang="en-US it" For those cases where I couldn't customize the install path, I used the cygpath tool to get the shortened path as suggested on this page https://wiki.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows#configure (e.g. cygpath -m -s "C:\Path With Spaces\That Needs Shortening"). On Tue, Sep 20, 2016 at 3:22 AM, John D'Orazio < john.dora...@cappellaniauniroma3.org> wrote: I wound up building in stages, since the build was breaking here and there. I just picked it up from where it left off as I fixed things. So I don't have a single output... unless there is a log file that collects various build stages together into one single output? I would also recommend installing as many packages in cygwin as possible without going through the extra step of installing lynx or apt-cyg... While that does make the environment more similar to a linux build environment, it's still an extra step and I believe it could be indicated as a second possibliity. Somewhere in the Step by Step guide I added which packages to choose in the cygwin interface if installing them from the cygwin interface. I think installing the packages from the cygwin interface should be indicated as the first step to take when first installing cygwin, adding all the necessary packages along with the first install. The only package I couldn't find from the cygwin interface was the Perl LWP::UserAgent package, so I installed that using "cpan -i LWP::UserAgent". On Tue, Sep 20, 2016 at 12:25 AM, Patricia Shanahan wrote: Congratulations! I'm about to do a Windows 10 build on a new machine, so please make sure the step-by-step incorporates all that you learned in the process. I have a specific test I would like run. The current release process calls for doing the Windows builds on Windows 7. I am wondering if that is necessary. Could you test your Windows 10 build on a Windows 7 machine? Or send me the output - that may be quicker than waiting for my Windows 10 build to go through. On 9/19/2016 1:46 PM, John D'Orazio wrote: I have now successfully completed the build on Windows 10, and after changing the install path of NSIS to one without spaces, packaging also completed successfully. I have added "Windows 10" alongside "Windows 7" and "Windows 8.1" in the Step by Step guide. On Mon, Sep 19, 2016 at 7:50 PM, Patricia Shanahan wrote: I
Re: building on Windows 10 breaks at guistdio.exe
I actually did see an error in the packaging phase, but it didn't seem to affect the final output, I still got the setup.exe which worked just fine, and I can open and use soffice.exe just fine after running setup. This is the error I got: ERROR: The following errors occurred in packaging process: 273.923309 : ERROR: D:/NSIS/makensis.exe D:/source/aoo-trunk/main/instsetoo_native/ wntmsci12.pro/Apache_OpenOffice/msi/nsis/it/downloadtemplate.nsi | ! 273.923514 : !include: error in script: "D:/source/aoo-trunk/main/instsetoo_native/ wntmsci12.pro/Apache_OpenOffice/msi/nsis/it\Italian_pack.nsh" on line 10 273.923550 : Error in macro LANGFILE_INCLUDE on macroline 11 273.923588 : Error in macro MUI_LANGUAGE_PACK on macroline 12 273.923619 : Error in script "D:/source/aoo-trunk/main/instsetoo_native/ wntmsci12.pro/Apache_OpenOffice/msi/nsis/it/downloadtemplate.nsi" on line 270 -- aborting creation process Not sure what that might affect. Also, here are my final working configure settings: SDK_PATH="D:\Microsoft_SDKs\Windows\v7.0" ./configure --with-build-version="$(date +"%Y-%m-%d %H:%M:%S (%a, %d %b %Y)")" --with-directx-home="D:\Microsoft_DirectX_SDK_June_2010" --with-frame-home="D:/Microsoft_SDKs/Windows/v7.0" --with-psdk-home="D:/Microsoft_SDKs/Windows/v7.0" --with-midl-path="D:/Microsoft_SDKs/Windows/v7.0/bin" --with-ant-home="/cygdrive/d/apache-ant/apache-ant-1.9.7" --with-nsis-path="D:/NSIS" --with-jdk-home="C:/PROGRA~2/Java/JDK18~1.0_7" --with-csc-path="C:/Windows/Microsoft.NET/Framework/v3.5" --with-cl-home="C:/PROGRA~2/MI1DCA~1.0/VC" --with-asm-home="C:/PROGRA~2/MI1DCA~1.0/VC/bin" --with-mozilla-build="/cygdrive/d/mozilla-build" --with-atl-include-dir=/cygdrive/c/WinDDK/7600.16385.1/inc/atl71 --with-atl-lib-dir=/cygdrive/c/WinDDK/7600.16385.1/lib/ATL/i386 --with-mfc-include-dir=/cygdrive/c/WinDDK/7600.16385.1/inc/mfc42 --with-mfc-lib-dir=/cygdrive/c/WinDDK/7600.16385.1/lib/Mfc/i386 --with-dmake-url=" http://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2"; --with-epm-url=" https://sourceforge.net/projects/oooextras.mirror/files/epm-3.7.tar.gz"; --without-junit --without-stlport --enable-win-x64-shellext --enable-wiki-publisher --enable-category-b --enable-bundled-dictionaries --with-lang="en-US it" For those cases where I couldn't customize the install path, I used the cygpath tool to get the shortened path as suggested on this page https://wiki.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows#configure (e.g. cygpath -m -s "C:\Path With Spaces\That Needs Shortening"). On Tue, Sep 20, 2016 at 3:22 AM, John D'Orazio < john.dora...@cappellaniauniroma3.org> wrote: > I wound up building in stages, since the build was breaking here and > there. I just picked it up from where it left off as I fixed things. So I > don't have a single output... unless there is a log file that collects > various build stages together into one single output? > I would also recommend installing as many packages in cygwin as possible > without going through the extra step of installing lynx or apt-cyg... While > that does make the environment more similar to a linux build environment, > it's still an extra step and I believe it could be indicated as a second > possibliity. Somewhere in the Step by Step guide I added which packages to > choose in the cygwin interface if installing them from the cygwin > interface. I think installing the packages from the cygwin interface should > be indicated as the first step to take when first installing cygwin, adding > all the necessary packages along with the first install. > The only package I couldn't find from the cygwin interface was the Perl > LWP::UserAgent package, so I installed that using "cpan -i LWP::UserAgent". > > > On Tue, Sep 20, 2016 at 12:25 AM, Patricia Shanahan wrote: > >> Congratulations! I'm about to do a Windows 10 build on a new machine, so >> please make sure the step-by-step incorporates all that you learned in the >> process. >> >> I have a specific test I would like run. The current release process >> calls for doing the Windows builds on Windows 7. I am wondering if that is >> necessary. Could you test your Windows 10 build on a Windows 7 machine? Or >> send me the output - that may be quicker than waiting for my Windows 10 >> build to go through. >> >> >> On 9/19/2016 1:46 PM, John D'Orazio wrote: >> >>> I have now successfully completed the build on Windows 10, and after >>> changing the install path of NSIS to one without spaces, packaging also >>> completed successfully. I have added "Windows 10" alongside "Windows 7" >>> and >>> "Windows 8.1" in the Step by Step guide. >>> >>> On Mon, Sep 19, 2016 at 7:50 PM, Patricia Shanahan wrote: >>> >>> I had installed 64-bit Cygwin installed here before I
Re: building on Windows 10 breaks at guistdio.exe
I wound up building in stages, since the build was breaking here and there. I just picked it up from where it left off as I fixed things. So I don't have a single output... unless there is a log file that collects various build stages together into one single output? I would also recommend installing as many packages in cygwin as possible without going through the extra step of installing lynx or apt-cyg... While that does make the environment more similar to a linux build environment, it's still an extra step and I believe it could be indicated as a second possibliity. Somewhere in the Step by Step guide I added which packages to choose in the cygwin interface if installing them from the cygwin interface. I think installing the packages from the cygwin interface should be indicated as the first step to take when first installing cygwin, adding all the necessary packages along with the first install. The only package I couldn't find from the cygwin interface was the Perl LWP::UserAgent package, so I installed that using "cpan -i LWP::UserAgent". On Tue, Sep 20, 2016 at 12:25 AM, Patricia Shanahan wrote: > Congratulations! I'm about to do a Windows 10 build on a new machine, so > please make sure the step-by-step incorporates all that you learned in the > process. > > I have a specific test I would like run. The current release process calls > for doing the Windows builds on Windows 7. I am wondering if that is > necessary. Could you test your Windows 10 build on a Windows 7 machine? Or > send me the output - that may be quicker than waiting for my Windows 10 > build to go through. > > > On 9/19/2016 1:46 PM, John D'Orazio wrote: > >> I have now successfully completed the build on Windows 10, and after >> changing the install path of NSIS to one without spaces, packaging also >> completed successfully. I have added "Windows 10" alongside "Windows 7" >> and >> "Windows 8.1" in the Step by Step guide. >> >> On Mon, Sep 19, 2016 at 7:50 PM, Patricia Shanahan wrote: >> >> I had installed 64-bit Cygwin installed here before I started on compiling >>> AOO. I hit problems, and had to go to the recommended 32-bit Cygwin. >>> >>> However, things have changed a bit since then, so it may be worth seeing >>> if it works. >>> >>> On 9/19/2016 8:59 AM, John D'Orazio wrote: >>> ... >>> >>> I also read somewhere that maybe using 64 bit cygwin can resolve the occupied addresses and child_fork_process errors. I made an attempt at getting the build environment ready in 64 bit cygwin but configure is complaining about not finding Visual Studio C++, while this does not happen in 32 bit cygwin (I'm passing in the with-cl-home flag so it shouldn't have any problem finding it... I'm reading it has something to do with registry keys, idk I have to look into this better). ... >>> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >>> >>> >> >> > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- John R. D'Orazio
Re: building on Windows 10 breaks at guistdio.exe
Congratulations! I'm about to do a Windows 10 build on a new machine, so please make sure the step-by-step incorporates all that you learned in the process. I have a specific test I would like run. The current release process calls for doing the Windows builds on Windows 7. I am wondering if that is necessary. Could you test your Windows 10 build on a Windows 7 machine? Or send me the output - that may be quicker than waiting for my Windows 10 build to go through. On 9/19/2016 1:46 PM, John D'Orazio wrote: I have now successfully completed the build on Windows 10, and after changing the install path of NSIS to one without spaces, packaging also completed successfully. I have added "Windows 10" alongside "Windows 7" and "Windows 8.1" in the Step by Step guide. On Mon, Sep 19, 2016 at 7:50 PM, Patricia Shanahan wrote: I had installed 64-bit Cygwin installed here before I started on compiling AOO. I hit problems, and had to go to the recommended 32-bit Cygwin. However, things have changed a bit since then, so it may be worth seeing if it works. On 9/19/2016 8:59 AM, John D'Orazio wrote: ... I also read somewhere that maybe using 64 bit cygwin can resolve the occupied addresses and child_fork_process errors. I made an attempt at getting the build environment ready in 64 bit cygwin but configure is complaining about not finding Visual Studio C++, while this does not happen in 32 bit cygwin (I'm passing in the with-cl-home flag so it shouldn't have any problem finding it... I'm reading it has something to do with registry keys, idk I have to look into this better). ... - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: building on Windows 10 breaks at guistdio.exe
I have now successfully completed the build on Windows 10, and after changing the install path of NSIS to one without spaces, packaging also completed successfully. I have added "Windows 10" alongside "Windows 7" and "Windows 8.1" in the Step by Step guide. On Mon, Sep 19, 2016 at 7:50 PM, Patricia Shanahan wrote: > I had installed 64-bit Cygwin installed here before I started on compiling > AOO. I hit problems, and had to go to the recommended 32-bit Cygwin. > > However, things have changed a bit since then, so it may be worth seeing > if it works. > > On 9/19/2016 8:59 AM, John D'Orazio wrote: > ... > >> I also read somewhere that maybe using 64 bit cygwin can resolve the >> occupied addresses and child_fork_process errors. I made an attempt at >> getting the build environment ready in 64 bit cygwin but configure is >> complaining about not finding Visual Studio C++, while this does not >> happen >> in 32 bit cygwin (I'm passing in the with-cl-home flag so it shouldn't >> have >> any problem finding it... I'm reading it has something to do with registry >> keys, idk I have to look into this better). >> > ... > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- John R. D'Orazio
Re: building on Windows 10 breaks at guistdio.exe
I had installed 64-bit Cygwin installed here before I started on compiling AOO. I hit problems, and had to go to the recommended 32-bit Cygwin. However, things have changed a bit since then, so it may be worth seeing if it works. On 9/19/2016 8:59 AM, John D'Orazio wrote: ... I also read somewhere that maybe using 64 bit cygwin can resolve the occupied addresses and child_fork_process errors. I made an attempt at getting the build environment ready in 64 bit cygwin but configure is complaining about not finding Visual Studio C++, while this does not happen in 32 bit cygwin (I'm passing in the with-cl-home flag so it shouldn't have any problem finding it... I'm reading it has something to do with registry keys, idk I have to look into this better). ... - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: building on Windows 10 breaks at guistdio.exe
I installed some more things in my build environment such as the Windows Drive Kit and I enabled the atl flags. I cleaned the whole build and started over again with new config and using the multiprocessor and multi threading capability, and have now made it close to the end of the build. Only the last instsetoo_native module remains. This last module is not completing, I keep getting perl child_fork_process issues with address already busy etc. I've been trying with solutions I'm finding online with a dash rebaseall, haven't succeeded yet but will attempt again shortly. I also read somewhere that maybe using 64 bit cygwin can resolve the occupied addresses and child_fork_process errors. I made an attempt at getting the build environment ready in 64 bit cygwin but configure is complaining about not finding Visual Studio C++, while this does not happen in 32 bit cygwin (I'm passing in the with-cl-home flag so it shouldn't have any problem finding it... I'm reading it has something to do with registry keys, idk I have to look into this better). On Sep 18, 2016 20:05, "Patricia Shanahan" wrote: > Please excuse the delay responding - I put it aside hoping that someone > with more knowledge would respond, and then got involved in other things. > > One possibility is that solver/420/wntmsci12.pro/xml/ was partially built > due to an earlier failure. I suggest deleting solver/420/wntmsci12.pro > and trying again. > > On 9/15/2016 5:52 AM, John D'Orazio wrote: > >> Patricia you are correct, after a few more attempts the desktop module did >> build successfully. Now I'm up to the postprocess module, with this error: >> >> Entering /cygdrive/d/source/aoo-trunk/main/postprocess/packcomponents >> >> dmake: Error: -- `/cygdrive/d/source/aoo-trunk/main/solver/420/ >> wntmsci12.pro/xml/chartcontroller.component' not found, and can't be made >> >> 1 module(s): >> postprocess >> need(s) to be rebuilt >> >> Reason(s): >> >> ERROR: error 65280 occurred while making >> /cygdrive/d/source/aoo-trunk/main/postprocess/packcomponents >> >> When you have fixed the errors in that module you can resume the build by >> running: >> >> build --all:postprocess >> >> >> Any ideas on this "chartcontroller.component"? >> >> >> On Wed, Sep 14, 2016 at 11:58 PM, John D'Orazio < >> john.dora...@cappellaniauniroma3.org> wrote: >> >> If it can be of any use to understand better the problem, I'm using this >>> configuration: >>> >>> SDK_PATH="D:\Microsoft_SDKs\Windows\v7.0" >>> >>> ./configure --with-frame-home="$SDK_PATH" --with-psdk-home="$SDK_PATH" >>> --with-midl-path="$SDK_PATH/bin" --with-directx-home="D:\ >>> Microsoft_DirectX_SDK_June_2010" --with-ant-home="/cygdrive/d/a >>> pache-ant/apache-ant-1.9.7" >>> --with-jdk-home="C:\Program Files (x86)\Java\jdk1.8.0_73" >>> --with-csc-path="C:\Windows\Microsoft.NET\Framework\v3.5" >>> --with-dmake-url="http://sourceforge.net/projects/ >>> oooextras.mirror/files/dmake-4.12.tar.bz2" --with-epm-url="http://www. >>> msweet.org/files/project2/epm-3.7-source.tar.gz" --disable-pch >>> --disable-atl --disable-activex --without-junit >>> >>> >>> On Wed, Sep 14, 2016 at 9:39 PM, John D'Orazio >> cappellaniauniroma3.org> wrote: >>> >>> So I've taken courage thanks also to the work done by Patricia Shanahan on building OpenOffice in Windows 7 and Windows 8.1. I'm using Windows 10, and I've sorted through the first few obstacles and my build has now been running for 5-6 hours without any trouble. Until now that is. It just broke while building "guistdio.exe" in the desktop module. I'm not really seeing much information that can help me though, can any pick out what the trouble might be? Here is the last part of the build output: Compiling: desktop/test/deployment/active/active_native.cxx Making:test_deployment_active.lib Making:module definition file active_native.uno.def Making:itest_deployment_active_t1.lib lib -machine:IX86 @D:/cygwin/tmp/mktDdH6P Microsoft (R) Library Manager Version 9.00.30729.01 Copyright (C) Microsoft Corporation. All rights reserved. -out:../../../wntmsci12.pro/lib/itest_deployment_active_t1.lib -def:../../../wntmsci12.pro/misc/active_native.uno.def Creating library ../../../wntmsci12.pro/lib/ite st_deployment_active_t1.lib and object ../../../wntmsci12.pro/lib/ite st_deployment_active_t1.exp Making:active_native.uno.dll Microsoft (R) Windows (R) Resource Compiler Version 6.1.7600.16385 Copyright (C) Microsoft Corporation. All rights reserved. Microsoft (R) Incremental Linker Version 9.00.30729.01 Copyright (C) Microsoft Corporation. All rights reserved. /MAP /OPT:NOREF -safeseh -nxcompat -dynamicbase -NODEFAULTLIB -RELEASE -DEBUG -INCREMENTAL:NO /SUBSYSTEM:CONSOLE /DLL -out:../../../ wntmsci12.pro/bin/active_native.uno.dll -map:../../../wntmsci12.pro/mi sc/activ
Re: building on Windows 10 breaks at guistdio.exe
Please excuse the delay responding - I put it aside hoping that someone with more knowledge would respond, and then got involved in other things. One possibility is that solver/420/wntmsci12.pro/xml/ was partially built due to an earlier failure. I suggest deleting solver/420/wntmsci12.pro and trying again. On 9/15/2016 5:52 AM, John D'Orazio wrote: Patricia you are correct, after a few more attempts the desktop module did build successfully. Now I'm up to the postprocess module, with this error: Entering /cygdrive/d/source/aoo-trunk/main/postprocess/packcomponents dmake: Error: -- `/cygdrive/d/source/aoo-trunk/main/solver/420/ wntmsci12.pro/xml/chartcontroller.component' not found, and can't be made 1 module(s): postprocess need(s) to be rebuilt Reason(s): ERROR: error 65280 occurred while making /cygdrive/d/source/aoo-trunk/main/postprocess/packcomponents When you have fixed the errors in that module you can resume the build by running: build --all:postprocess Any ideas on this "chartcontroller.component"? On Wed, Sep 14, 2016 at 11:58 PM, John D'Orazio < john.dora...@cappellaniauniroma3.org> wrote: If it can be of any use to understand better the problem, I'm using this configuration: SDK_PATH="D:\Microsoft_SDKs\Windows\v7.0" ./configure --with-frame-home="$SDK_PATH" --with-psdk-home="$SDK_PATH" --with-midl-path="$SDK_PATH/bin" --with-directx-home="D:\ Microsoft_DirectX_SDK_June_2010" --with-ant-home="/cygdrive/d/apache-ant/apache-ant-1.9.7" --with-jdk-home="C:\Program Files (x86)\Java\jdk1.8.0_73" --with-csc-path="C:\Windows\Microsoft.NET\Framework\v3.5" --with-dmake-url="http://sourceforge.net/projects/ oooextras.mirror/files/dmake-4.12.tar.bz2" --with-epm-url="http://www. msweet.org/files/project2/epm-3.7-source.tar.gz" --disable-pch --disable-atl --disable-activex --without-junit On Wed, Sep 14, 2016 at 9:39 PM, John D'Orazio wrote: So I've taken courage thanks also to the work done by Patricia Shanahan on building OpenOffice in Windows 7 and Windows 8.1. I'm using Windows 10, and I've sorted through the first few obstacles and my build has now been running for 5-6 hours without any trouble. Until now that is. It just broke while building "guistdio.exe" in the desktop module. I'm not really seeing much information that can help me though, can any pick out what the trouble might be? Here is the last part of the build output: Compiling: desktop/test/deployment/active/active_native.cxx Making:test_deployment_active.lib Making:module definition file active_native.uno.def Making:itest_deployment_active_t1.lib lib -machine:IX86 @D:/cygwin/tmp/mktDdH6P Microsoft (R) Library Manager Version 9.00.30729.01 Copyright (C) Microsoft Corporation. All rights reserved. -out:../../../wntmsci12.pro/lib/itest_deployment_active_t1.lib -def:../../../wntmsci12.pro/misc/active_native.uno.def Creating library ../../../wntmsci12.pro/lib/ite st_deployment_active_t1.lib and object ../../../wntmsci12.pro/lib/ite st_deployment_active_t1.exp Making:active_native.uno.dll Microsoft (R) Windows (R) Resource Compiler Version 6.1.7600.16385 Copyright (C) Microsoft Corporation. All rights reserved. Microsoft (R) Incremental Linker Version 9.00.30729.01 Copyright (C) Microsoft Corporation. All rights reserved. /MAP /OPT:NOREF -safeseh -nxcompat -dynamicbase -NODEFAULTLIB -RELEASE -DEBUG -INCREMENTAL:NO /SUBSYSTEM:CONSOLE /DLL -out:../../../ wntmsci12.pro/bin/active_native.uno.dll -map:../../../wntmsci12.pro/mi sc/active_native.uno.map ../../../wntmsci12.pro/lib/ite st_deployment_active_t1.exp ../../../wntmsci12.pro/slo/active_native.obj ../../../wntmsci12.pro/slo/active_native.uno_version.obj icppuhelper.lib icppu.lib isal.lib msvcrt.lib msvcprt.lib uwinapi.lib kernel32.lib user32.lib oldnames.lib ../../../wntmsci12.pro/misc/active_native.uno.res linking ../../../wntmsci12.pro/bin/active_native.uno.dll.manifest ... Making:all_test_deployment_active.dpslo mkdir.exe -p ../../../wntmsci12.pro/misc/test_deployment_active/ /bin/rm -f ../../../wntmsci12.pro/misc/test_deployment_active/active_ja va.jar /bin/rm -f -r ../../../wntmsci12.pro/misc/te st_deployment_active/active_java.jar-zip mkdir.exe ../../../wntmsci12.pro/misc/test_deployment_active/active_ja va.jar-zip mkdir.exe -p ../../../wntmsci12.pro/misc/test_deployment_active/active_ja va.jar-zip/META-INF \ ../../../wntmsci12.pro/misc/test_deployment_active/active_ja va.jar-zip/com/sun/star/comp/test/deployment/active_java cp MANIFEST.MF ../../../wntmsci12.pro/misc/te st_deployment_active/active_java.jar-zip/META-INF/ cp ../../../wntmsci12.pro/class/com/sun/star/comp/test/deployme nt/active_java/Dispatch.class ../../../wntmsci12.pro/class/c om/sun/star/comp/test/deployment/active_java/Provider.class ../../../ wntmsci12.pro/class/com/sun/star/comp/test/deployme nt/active_java/Services.class \ ../../../wntmsci12.pro/misc/test_deployment_active/active_ja va.jar-zip/com/sun/star/comp/test/deployment/ac
Re: building on Windows 10 breaks at guistdio.exe
Patricia you are correct, after a few more attempts the desktop module did build successfully. Now I'm up to the postprocess module, with this error: Entering /cygdrive/d/source/aoo-trunk/main/postprocess/packcomponents dmake: Error: -- `/cygdrive/d/source/aoo-trunk/main/solver/420/ wntmsci12.pro/xml/chartcontroller.component' not found, and can't be made 1 module(s): postprocess need(s) to be rebuilt Reason(s): ERROR: error 65280 occurred while making /cygdrive/d/source/aoo-trunk/main/postprocess/packcomponents When you have fixed the errors in that module you can resume the build by running: build --all:postprocess Any ideas on this "chartcontroller.component"? On Wed, Sep 14, 2016 at 11:58 PM, John D'Orazio < john.dora...@cappellaniauniroma3.org> wrote: > If it can be of any use to understand better the problem, I'm using this > configuration: > > SDK_PATH="D:\Microsoft_SDKs\Windows\v7.0" > > ./configure --with-frame-home="$SDK_PATH" --with-psdk-home="$SDK_PATH" > --with-midl-path="$SDK_PATH/bin" --with-directx-home="D:\ > Microsoft_DirectX_SDK_June_2010" > --with-ant-home="/cygdrive/d/apache-ant/apache-ant-1.9.7" > --with-jdk-home="C:\Program Files (x86)\Java\jdk1.8.0_73" > --with-csc-path="C:\Windows\Microsoft.NET\Framework\v3.5" > --with-dmake-url="http://sourceforge.net/projects/ > oooextras.mirror/files/dmake-4.12.tar.bz2" --with-epm-url="http://www. > msweet.org/files/project2/epm-3.7-source.tar.gz" --disable-pch > --disable-atl --disable-activex --without-junit > > > On Wed, Sep 14, 2016 at 9:39 PM, John D'Orazio cappellaniauniroma3.org> wrote: > >> So I've taken courage thanks also to the work done by Patricia Shanahan >> on building OpenOffice in Windows 7 and Windows 8.1. I'm using Windows 10, >> and I've sorted through the first few obstacles and my build has now been >> running for 5-6 hours without any trouble. Until now that is. It just broke >> while building "guistdio.exe" in the desktop module. I'm not really seeing >> much information that can help me though, can any pick out what the trouble >> might be? Here is the last part of the build output: >> >> Compiling: desktop/test/deployment/active/active_native.cxx >> Making:test_deployment_active.lib >> Making:module definition file active_native.uno.def >> Making:itest_deployment_active_t1.lib >> lib -machine:IX86 @D:/cygwin/tmp/mktDdH6P >> Microsoft (R) Library Manager Version 9.00.30729.01 >> Copyright (C) Microsoft Corporation. All rights reserved. >> >> -out:../../../wntmsci12.pro/lib/itest_deployment_active_t1.lib >> -def:../../../wntmsci12.pro/misc/active_native.uno.def >>Creating library ../../../wntmsci12.pro/lib/ite >> st_deployment_active_t1.lib and object ../../../wntmsci12.pro/lib/ite >> st_deployment_active_t1.exp >> Making:active_native.uno.dll >> Microsoft (R) Windows (R) Resource Compiler Version 6.1.7600.16385 >> Copyright (C) Microsoft Corporation. All rights reserved. >> >> Microsoft (R) Incremental Linker Version 9.00.30729.01 >> Copyright (C) Microsoft Corporation. All rights reserved. >> >> /MAP /OPT:NOREF -safeseh -nxcompat -dynamicbase -NODEFAULTLIB -RELEASE >> -DEBUG -INCREMENTAL:NO /SUBSYSTEM:CONSOLE /DLL -out:../../../ >> wntmsci12.pro/bin/active_native.uno.dll -map:../../../wntmsci12.pro/mi >> sc/active_native.uno.map ../../../wntmsci12.pro/lib/ite >> st_deployment_active_t1.exp ../../../wntmsci12.pro/slo/active_native.obj >> ../../../wntmsci12.pro/slo/active_native.uno_version.obj icppuhelper.lib >> icppu.lib isal.lib msvcrt.lib msvcprt.lib uwinapi.lib kernel32.lib >> user32.lib oldnames.lib ../../../wntmsci12.pro/misc/active_native.uno.res >> linking ../../../wntmsci12.pro/bin/active_native.uno.dll.manifest ... >> Making:all_test_deployment_active.dpslo >> mkdir.exe -p ../../../wntmsci12.pro/misc/test_deployment_active/ >> /bin/rm -f ../../../wntmsci12.pro/misc/test_deployment_active/active_ja >> va.jar >> /bin/rm -f -r ../../../wntmsci12.pro/misc/te >> st_deployment_active/active_java.jar-zip >> mkdir.exe ../../../wntmsci12.pro/misc/test_deployment_active/active_ja >> va.jar-zip >> mkdir.exe -p ../../../wntmsci12.pro/misc/test_deployment_active/active_ja >> va.jar-zip/META-INF \ >> ../../../wntmsci12.pro/misc/test_deployment_active/active_ja >> va.jar-zip/com/sun/star/comp/test/deployment/active_java >> cp MANIFEST.MF ../../../wntmsci12.pro/misc/te >> st_deployment_active/active_java.jar-zip/META-INF/ >> cp ../../../wntmsci12.pro/class/com/sun/star/comp/test/deployme >> nt/active_java/Dispatch.class ../../../wntmsci12.pro/class/c >> om/sun/star/comp/test/deployment/active_java/Provider.class ../../../ >> wntmsci12.pro/class/com/sun/star/comp/test/deployme >> nt/active_java/Services.class \ >> ../../../wntmsci12.pro/misc/test_deployment_active/active_ja >> va.jar-zip/com/sun/star/comp/test/deployment/active_java/ >> cd ../../../wntmsci12.pro/misc/test_deployment_active/active_java.jar-zip >> && zip ../active_java.jar \ >> META
Re: building on Windows 10 breaks at guistdio.exe
If it can be of any use to understand better the problem, I'm using this configuration: SDK_PATH="D:\Microsoft_SDKs\Windows\v7.0" ./configure --with-frame-home="$SDK_PATH" --with-psdk-home="$SDK_PATH" --with-midl-path="$SDK_PATH/bin" --with-directx-home="D:\Microsoft_DirectX_SDK_June_2010" --with-ant-home="/cygdrive/d/apache-ant/apache-ant-1.9.7" --with-jdk-home="C:\Program Files (x86)\Java\jdk1.8.0_73" --with-csc-path="C:\Windows\Microsoft.NET\Framework\v3.5" --with-dmake-url=" http://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2"; --with-epm-url="http://www.msweet.org/files/project2/epm-3.7-source.tar.gz"; --disable-pch --disable-atl --disable-activex --without-junit On Wed, Sep 14, 2016 at 9:39 PM, John D'Orazio < john.dora...@cappellaniauniroma3.org> wrote: > So I've taken courage thanks also to the work done by Patricia Shanahan on > building OpenOffice in Windows 7 and Windows 8.1. I'm using Windows 10, and > I've sorted through the first few obstacles and my build has now been > running for 5-6 hours without any trouble. Until now that is. It just broke > while building "guistdio.exe" in the desktop module. I'm not really seeing > much information that can help me though, can any pick out what the trouble > might be? Here is the last part of the build output: > > Compiling: desktop/test/deployment/active/active_native.cxx > Making:test_deployment_active.lib > Making:module definition file active_native.uno.def > Making:itest_deployment_active_t1.lib > lib -machine:IX86 @D:/cygwin/tmp/mktDdH6P > Microsoft (R) Library Manager Version 9.00.30729.01 > Copyright (C) Microsoft Corporation. All rights reserved. > > -out:../../../wntmsci12.pro/lib/itest_deployment_active_t1.lib > -def:../../../wntmsci12.pro/misc/active_native.uno.def >Creating library ../../../wntmsci12.pro/lib/ > itest_deployment_active_t1.lib and object ../../../wntmsci12.pro/lib/ > itest_deployment_active_t1.exp > Making:active_native.uno.dll > Microsoft (R) Windows (R) Resource Compiler Version 6.1.7600.16385 > Copyright (C) Microsoft Corporation. All rights reserved. > > Microsoft (R) Incremental Linker Version 9.00.30729.01 > Copyright (C) Microsoft Corporation. All rights reserved. > > /MAP /OPT:NOREF -safeseh -nxcompat -dynamicbase -NODEFAULTLIB -RELEASE > -DEBUG -INCREMENTAL:NO /SUBSYSTEM:CONSOLE /DLL -out:../../../ > wntmsci12.pro/bin/active_native.uno.dll -map:../../../wntmsci12.pro/ > misc/active_native.uno.map ../../../wntmsci12.pro/lib/ > itest_deployment_active_t1.exp ../../../wntmsci12.pro/slo/ > active_native.obj ../../../wntmsci12.pro/slo/active_native.uno_version.obj > icppuhelper.lib icppu.lib isal.lib msvcrt.lib msvcprt.lib uwinapi.lib > kernel32.lib user32.lib oldnames.lib ../../../wntmsci12.pro/misc/ > active_native.uno.res > linking ../../../wntmsci12.pro/bin/active_native.uno.dll.manifest ... > Making:all_test_deployment_active.dpslo > mkdir.exe -p ../../../wntmsci12.pro/misc/test_deployment_active/ > /bin/rm -f ../../../wntmsci12.pro/misc/test_deployment_active/active_ > java.jar > /bin/rm -f -r ../../../wntmsci12.pro/misc/test_deployment_active/active_ > java.jar-zip > mkdir.exe ../../../wntmsci12.pro/misc/test_deployment_active/active_ > java.jar-zip > mkdir.exe -p ../../../wntmsci12.pro/misc/test_deployment_active/active_ > java.jar-zip/META-INF \ > ../../../wntmsci12.pro/misc/test_deployment_active/active_ > java.jar-zip/com/sun/star/comp/test/deployment/active_java > cp MANIFEST.MF ../../../wntmsci12.pro/misc/test_deployment_active/active_ > java.jar-zip/META-INF/ > cp ../../../wntmsci12.pro/class/com/sun/star/comp/test/ > deployment/active_java/Dispatch.class ../../../wntmsci12.pro/class/ > com/sun/star/comp/test/deployment/active_java/Provider.class ../../../ > wntmsci12.pro/class/com/sun/star/comp/test/deployment/active_java/ > Services.class \ > ../../../wntmsci12.pro/misc/test_deployment_active/active_ > java.jar-zip/com/sun/star/comp/test/deployment/active_java/ > cd ../../../wntmsci12.pro/misc/test_deployment_active/active_java.jar-zip > && zip ../active_java.jar \ > META-INF/MANIFEST.MF com/sun/star/comp/test/ > deployment/active_java/Dispatch.class com/sun/star/comp/test/ > deployment/active_java/Provider.class com/sun/star/comp/test/ > deployment/active_java/Services.class > adding: META-INF/MANIFEST.MF (deflated 9%) > adding: com/sun/star/comp/test/deployment/active_java/Dispatch.class > (deflated 54%) > adding: com/sun/star/comp/test/deployment/active_java/Provider.class > (deflated 52%) > adding: com/sun/star/comp/test/deployment/active_java/Services.class > (deflated 54%) > /bin/rm -f ../../../wntmsci12.pro/misc/active.oxt > /bin/rm -f -r ../../../wntmsci12.pro/misc/test_deployment_active/active. > oxt-zip > mkdir.exe ../../../wntmsci12.pro/misc/test_deployment_active/active. > oxt-zip > mkdir.exe -p ../../../wntmsci12.pro/misc/test_deployment_active/active. > oxt-zip/META-INF > sed -e 's|@PATH@|active_native.uno
Re: building on Windows 10 breaks at guistdio.exe
I've never seen this failure before. The only suggestion I can make is to retry. That sometimes fixes failed builds. On 9/14/2016 12:39 PM, John D'Orazio wrote: ... dmake: '../../../wntmsci12.pro/bin/guistdio.exe' removed. 1 module(s): desktop need(s) to be rebuilt Reason(s): ERROR: error 65280 occurred while making /cygdrive/d/source/aoo-trunk/main/desktop/win32/source/guistdio When you have fixed the errors in that module you can resume the build by running: build --all:desktop Do I perhaps need to enable a verbose output to have more information to go on? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
building on Windows 10 breaks at guistdio.exe
So I've taken courage thanks also to the work done by Patricia Shanahan on building OpenOffice in Windows 7 and Windows 8.1. I'm using Windows 10, and I've sorted through the first few obstacles and my build has now been running for 5-6 hours without any trouble. Until now that is. It just broke while building "guistdio.exe" in the desktop module. I'm not really seeing much information that can help me though, can any pick out what the trouble might be? Here is the last part of the build output: Compiling: desktop/test/deployment/active/active_native.cxx Making:test_deployment_active.lib Making:module definition file active_native.uno.def Making:itest_deployment_active_t1.lib lib -machine:IX86 @D:/cygwin/tmp/mktDdH6P Microsoft (R) Library Manager Version 9.00.30729.01 Copyright (C) Microsoft Corporation. All rights reserved. -out:../../../wntmsci12.pro/lib/itest_deployment_active_t1.lib -def:../../../wntmsci12.pro/misc/active_native.uno.def Creating library ../../../ wntmsci12.pro/lib/itest_deployment_active_t1.lib and object ../../../ wntmsci12.pro/lib/itest_deployment_active_t1.exp Making:active_native.uno.dll Microsoft (R) Windows (R) Resource Compiler Version 6.1.7600.16385 Copyright (C) Microsoft Corporation. All rights reserved. Microsoft (R) Incremental Linker Version 9.00.30729.01 Copyright (C) Microsoft Corporation. All rights reserved. /MAP /OPT:NOREF -safeseh -nxcompat -dynamicbase -NODEFAULTLIB -RELEASE -DEBUG -INCREMENTAL:NO /SUBSYSTEM:CONSOLE /DLL -out:../../../ wntmsci12.pro/bin/active_native.uno.dll -map:../../../ wntmsci12.pro/misc/active_native.uno.map ../../../ wntmsci12.pro/lib/itest_deployment_active_t1.exp ../../../ wntmsci12.pro/slo/active_native.obj ../../../ wntmsci12.pro/slo/active_native.uno_version.obj icppuhelper.lib icppu.lib isal.lib msvcrt.lib msvcprt.lib uwinapi.lib kernel32.lib user32.lib oldnames.lib ../../../wntmsci12.pro/misc/active_native.uno.res linking ../../../wntmsci12.pro/bin/active_native.uno.dll.manifest ... Making:all_test_deployment_active.dpslo mkdir.exe -p ../../../wntmsci12.pro/misc/test_deployment_active/ /bin/rm -f ../../../ wntmsci12.pro/misc/test_deployment_active/active_java.jar /bin/rm -f -r ../../../ wntmsci12.pro/misc/test_deployment_active/active_java.jar-zip mkdir.exe ../../../ wntmsci12.pro/misc/test_deployment_active/active_java.jar-zip mkdir.exe -p ../../../ wntmsci12.pro/misc/test_deployment_active/active_java.jar-zip/META-INF \ ../../../ wntmsci12.pro/misc/test_deployment_active/active_java.jar-zip/com/sun/star/comp/test/deployment/active_java cp MANIFEST.MF ../../../ wntmsci12.pro/misc/test_deployment_active/active_java.jar-zip/META-INF/ cp ../../../ wntmsci12.pro/class/com/sun/star/comp/test/deployment/active_java/Dispatch.class ../../../ wntmsci12.pro/class/com/sun/star/comp/test/deployment/active_java/Provider.class ../../../ wntmsci12.pro/class/com/sun/star/comp/test/deployment/active_java/Services.class \ ../../../ wntmsci12.pro/misc/test_deployment_active/active_java.jar-zip/com/sun/star/comp/test/deployment/active_java/ cd ../../../wntmsci12.pro/misc/test_deployment_active/active_java.jar-zip && zip ../active_java.jar \ META-INF/MANIFEST.MF com/sun/star/comp/test/deployment/active_java/Dispatch.class com/sun/star/comp/test/deployment/active_java/Provider.class com/sun/star/comp/test/deployment/active_java/Services.class adding: META-INF/MANIFEST.MF (deflated 9%) adding: com/sun/star/comp/test/deployment/active_java/Dispatch.class (deflated 54%) adding: com/sun/star/comp/test/deployment/active_java/Provider.class (deflated 52%) adding: com/sun/star/comp/test/deployment/active_java/Services.class (deflated 54%) /bin/rm -f ../../../wntmsci12.pro/misc/active.oxt /bin/rm -f -r ../../../ wntmsci12.pro/misc/test_deployment_active/active.oxt-zip mkdir.exe ../../../wntmsci12.pro/misc/test_deployment_active/active.oxt-zip mkdir.exe -p ../../../ wntmsci12.pro/misc/test_deployment_active/active.oxt-zip/META-INF sed -e 's|@PATH@|active_native.uno.dll|g' \ -e 's|@PLATFORM@|windows_x86|g' < manifest.xml \ > ../../../ wntmsci12.pro/misc/test_deployment_active/active.oxt-zip/META-INF/manifest.xml cp description.xml Addons.xcu ProtocolHandler.xcu ../../../ wntmsci12.pro/bin/active_native.uno.dll \ ../../../wntmsci12.pro/misc/test_deployment_active/active_java.jar active_python.py \ ../../../wntmsci12.pro/misc/test_deployment_active/active.oxt-zip/ cd ../../../wntmsci12.pro/misc/test_deployment_active/active.oxt-zip && zip ../../active.oxt \ META-INF/manifest.xml description.xml Addons.xcu ProtocolHandler.xcu \ active_native.uno.dll active_java.jar active_python.py adding: META-INF/manifest.xml (deflated 58%) adding: description.xml (deflated 50%) adding: Addons.xcu (deflated 67%) adding: ProtocolHandler.xcu (deflated 61%) adding: active_native.uno.dll (deflated 58%) adding: active_java.jar (deflated 13%) adding: active_python.py (