Re: 'make check' with Windows/MSVC build?
On Thu, 2012-04-12 at 14:11 +0200, Stephan Bergmann wrote: Can't remember any details, but I think I did have a real problem with it before I discovered --disable-linkoo sometime last year Hey ho :-) and recently I remote-debugged something with somebody, and we came to the conclusion that the problem (whatever it was) was due to his use of linkoo. Oddly, I use it exclusively and don't get these problems - though there are some things that are not (yet) linked of course which can cause some grief (particularly if you're not expecting that). And of course you need to source 'ooenv' to get STAR_RESOURCEPATH set [ though strangely things seem to work without that these days ]. Anyhow - well formed bug reports much appreciated :-) ATB, Michael. -- michael.me...@suse.com , Pseudo Engineer, itinerant idiot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: 'make check' with Windows/MSVC build?
On Wed, 2012-04-18 at 11:06 +0100, Michael Meeks wrote: And of course you need to source 'ooenv' to get STAR_RESOURCEPATH set [ though strangely things seem to work without that these days ]. soffice script will source ooenv if it finds it, if you mean that. C. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: 'make check' with Windows/MSVC build?
On 2012-04-11 18:19, Stephan Bergmann wrote: My understanding is that we use classic paths (not starting with \\?) whenever they are short enough, anyway. So the problem cannot be solved with an #if, but (short of abandoning berkeleydb) needs to be worked around by making sure the LO installation is in a location with a short path (so that the paths of any files within the installation that are handed to berkeleydb are also short). git grep db_create says there 5 places within LO where we hand a path to berkelydb. Perhaps in that place we can convert to a 8.3 using the Win32 API GetShortPathName. Or we could unconditionally convert to a very long path (using \\?) ? -- Noel Disclaimer: http://www.peralex.com/disclaimer.html ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: 'make check' with Windows/MSVC build?
On 04/12/2012 10:00 AM, Noel Grandin wrote: On 2012-04-11 18:19, Stephan Bergmann wrote: My understanding is that we use classic paths (not starting with \\?) whenever they are short enough, anyway. So the problem cannot be solved with an #if, but (short of abandoning berkeleydb) needs to be worked around by making sure the LO installation is in a location with a short path (so that the paths of any files within the installation that are handed to berkeleydb are also short). git grep db_create says there 5 places within LO where we hand a path to berkelydb. Perhaps in that place we can convert to a 8.3 using the Win32 API GetShortPathName. Or we could unconditionally convert to a very long path (using \\?) ? My understanding is that berkeleydb does not accept \\? style paths. But feel free to experiment. Stephan ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: 'make check' with Windows/MSVC build?
On Wed, 2012-04-11 at 18:19 +0200, Stephan Bergmann wrote: So the problem cannot be solved with an #if, but (short of abandoning berkeleydb) needs to be worked around by making sure the LO installation is in a location with a short path (so that the paths of any files within the installation that are handed to berkeleydb are also short). Sigh - if berkeleydb is the only problem here, surely we can get rid of it ? :-) I -thought- that we had done so in 3.5 actually; IIRC we were using it for some component cache, where it would have been faster smaller to use the associated text file ;-) but I forget the details. Hmm, Michael. -- michael.me...@suse.com , Pseudo Engineer, itinerant idiot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: 'make check' with Windows/MSVC build?
On Wed, 2012-04-11 at 17:34 +0200, Stephan Bergmann wrote: (And even on Linux, linkoo does not really work, and I'm happy to avoid it via --disable-linkoo. But I do understand that this is not very newbee friendly.) Oh !? we should fix that, is there a bug ? it'd prolly be an easy-hack :-) I believe we killed the black-list for UNO libraries so it should work for them; there is some bug with versioned .so's it seems, so we're missing this little lot: -rwxr-xr-x 1 michael users 231912 Apr 11 17:49 ./program/libcurl.so.4 -rwxr-xr-x 1 michael users 14942632 Apr 11 17:36 ./program/libicudata.so.44.2 -rwxr-xr-x 1 michael users 1785268 Apr 11 17:36 ./program/libicui18n.so.44.2 -rwxr-xr-x 1 michael users 210376 Apr 11 17:36 ./program/libicule.so.44.2 -rwxr-xr-x 1 michael users 1267500 Apr 11 17:36 ./program/libicuuc.so.44.2 -rwxr-xr-x 1 michael users 317620 Apr 11 17:29 ./program/liblcms2.so.2 -rwxr-xr-x 1 michael users 406672 Apr 11 17:57 ./program/libraptor.so.1 -rwxr-xr-x 1 michael users 252788 Apr 11 17:58 ./program/librasqal.so.1 -rwxr-xr-x 1 michael users 240736 Apr 11 17:58 ./program/librdf.so.0 -rwxr-xr-x 1 michael users 248720 Apr 11 17:36 ./program/libxslt.so.1 -rw-r--r-- 1 michael users 752072 Apr 11 18:36 ./share/extensions/pdfimport/pdfimport.uno.so -rwxr-xr-x 1 michael users 108560 Apr 11 17:41 ./ure/lib/libjvmfwk.so.3 -rwxr-xr-x 1 michael users71908 Apr 11 17:41 ./ure/lib/libsunjavaplugin.so -rwxr-xr-x 1 michael users 563620 Apr 11 17:39 ./ure/lib/libuno_cppuhelpergcc3.so.3 -rwxr-xr-x 1 michael users 1311332 Apr 11 17:33 ./ure/lib/libxml2.so.2 But - overall it does a reasonable job - at least for me. ATB, Michael. -- michael.me...@suse.com , Pseudo Engineer, itinerant idiot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: 'make check' with Windows/MSVC build?
On 04/12/2012 11:40 AM, Michael Meeks wrote: On Wed, 2012-04-11 at 17:34 +0200, Stephan Bergmann wrote: (And even on Linux, linkoo does not really work, and I'm happy to avoid it via --disable-linkoo. But I do understand that this is not very newbee friendly.) But - overall it does a reasonable job - at least for me. Can't remember any details, but I think I did have a real problem with it before I discovered --disable-linkoo sometime last year, and recently I remote-debugged something with somebody, and we came to the conclusion that the problem (whatever it was) was due to his use of linkoo. Stephan ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: 'make check' with Windows/MSVC build?
On 04/10/2012 07:06 PM, Michael Stahl wrote: is this ooinstall thing supposed to work on Windows at all? AFAIK it symlinks stuff left and right, and running the result of that can hardly work as native Win32 program? IIUC, it should only use symlinks if used in combination with (default) --enable-linkoo. However, I guess the mechanisms to create a LO installation against which to run the tests (which was always handled slightly differently on Windows, to avoid problems with long pathnames) has been broken with the various changes how to create that LO installation in general (ooinstall). the bigger problem is that this project doesn't seem to have any Windows developers :) Ack. Stephan ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: 'make check' with Windows/MSVC build?
On 2012-04-11 08:48, Stephan Bergmann wrote: the bigger problem is that this project doesn't seem to have any Windows developers :) Ack. It's kind of catch-22. I develop on Windows, but I do my LibreOffice work on Ubuntu running inside a VMWare image, simply because the Windows build was almost permanently broken. The LibreOffice Windows build seems to be more stable these days, but now I'm too lazy to change :-) Disclaimer: http://www.peralex.com/disclaimer.html ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: 'make check' with Windows/MSVC build?
On Wednesday 11 of April 2012, Stephan Bergmann wrote: On 04/10/2012 07:06 PM, Michael Stahl wrote: is this ooinstall thing supposed to work on Windows at all? AFAIK it symlinks stuff left and right, and running the result of that can hardly work as native Win32 program? IIUC, it should only use symlinks if used in combination with (default) --enable-linkoo. (On Linux) $ make cmd cmd='ooinstall /tmp/loinst' $ find /tmp/loinst -type l /tmp/loinst/ure-link /tmp/loinst/sdk/lib/libuno_cppuhelpergcc3.so /tmp/loinst/sdk/lib/libuno_cppu.so /tmp/loinst/sdk/lib/libuno_sal.so /tmp/loinst/sdk/lib/libuno_purpenvhelpergcc3.so /tmp/loinst/sdk/lib/libuno_salhelpergcc3.so /tmp/loinst/ure/bin/regcomp /tmp/loinst/ure/bin/uno That doesn't look like there's any serious blocker problem with symlinks. Are there any other reasons why it shouldn't work on Windows? However, I guess the mechanisms to create a LO installation against which to run the tests (which was always handled slightly differently on Windows, to avoid problems with long pathnames) has been broken with the various changes how to create that LO installation in general (ooinstall). So it can work, it's just slightly broken somewhere at the moment? If that's so, could somebody who understands this stuff have a look? I don't think it should be such a big problem to keep the Windows/MSVC build working, as soon as it builds once. The tinderboxes are now quite reliable and would catch any breakages in the later stages, like they catch build breakages now. I don't see it very differently from the MacOSX/PPC/gcc-4.0.1 build for example. Not that it would make it work magically, of course (I remember I was amused to see some time back the 'oh, master actually build for me on Windows' thread on this list just the very next day after I had spent quite some time getting a number of MSVC issues fixed), but apparently it works for MSVC issues, so it could work for Windows issues as well. the bigger problem is that this project doesn't seem to have any Windows developers :) That would be more likely to change if those potential developers would not have to employ the horrible debug cycle Tor has described. And, BTW, I think linkoo could be modified for Windows, so that it does not create symlinks, but instead it copies a file if the one in solver/ is newer. That would still require 'make dev-install' after every change, but I expect it should be reasonably fast, quite convenient to use, and probably the best we can do. -- Lubos Lunak l.lu...@suse.cz ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: 'make check' with Windows/MSVC build?
On Wed, 2012-04-11 at 14:17 +0200, Lubos Lunak wrote: And, BTW, I think linkoo could be modified for Windows, so that it does not create symlinks, but instead it copies a file if the one in solver/ is newer. Wouldn't it be nice if we could just built into a output install tree in the first place directly rather that stick everything into an intermediate solver/foo out of which we build an install tree at a later stage. C. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: 'make check' with Windows/MSVC build?
Hello, On 10/04/12 20:02, Tor Lillqvist wrote: Presumably not. The way I iterate edit-compile-test on Windows (when I do it, which is not often lately) is to have a normal installation (in a virtual machine), i.e. from an installer, and then manually replace the DLL(s) I am debugging... and replace again after edit/compile... Exactly the same proceeding here, and launching libreoffice and then to attach the debugger to soffice.bin is the most common way to debug. F. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: 'make check' with Windows/MSVC build?
On 04/11/2012 02:17 PM, Lubos Lunak wrote: On Wednesday 11 of April 2012, Stephan Bergmann wrote: However, I guess the mechanisms to create a LO installation against which to run the tests (which was always handled slightly differently on Windows, to avoid problems with long pathnames) has been broken with the various changes how to create that LO installation in general (ooinstall). So it can work, it's just slightly broken somewhere at the moment? If that's so, could somebody who understands this stuff have a look? There's two points to this: Originally, the installation against which the tests run had been produced in a two-step process. First, building instsetoo_native always produced a tgz (or zip, on Windows) archive installation set in addition to what else it was requested to build (rpm, deb, etc.). Second, depending on platform: On non-Windows, building smoketestoo_native unpacked the archive installation set to solver/*/installation once, so that all tests could use it from there. On Windows, running each individual test unpacked the archive installation set into a temp directory (and removed it afterwards). Today, this has been changed completely, with the installation set being built and put into place in one step through ooinstall. So for Windows to work again, first ooinstall needs to be fixed to work on Windows (my understanding is that it does not). Second, as long as long pathnames on Windows are still an issue (and my understanding is that they are, at least for our interaction with the berkeleydb library), it would be advantageous to mimic the original logic, like running ooinstall not once but for each test, instructing it to output into a temp directory. Stephan ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: 'make check' with Windows/MSVC build?
On 04/11/2012 02:24 PM, Caolán McNamara wrote: On Wed, 2012-04-11 at 14:17 +0200, Lubos Lunak wrote: And, BTW, I think linkoo could be modified for Windows, so that it does not create symlinks, but instead it copies a file if the one in solver/ is newer. Wouldn't it be nice if we could just built into a output install tree in the first place directly rather that stick everything into an intermediate solver/foo out of which we build an install tree at a later stage. That should still be considered one of our ultimate goals. (And even on Linux, linkoo does not really work, and I'm happy to avoid it via --disable-linkoo. But I do understand that this is not very newbee friendly.) Stephan ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: 'make check' with Windows/MSVC build?
On 2012-04-11 17:31, Stephan Bergmann wrote: ooinstall needs to be fixed to work on Windows (my understanding is that it does not). Second, as long as long pathnames on Windows are still an issue (and my understanding is that they are, at least for our interaction with the berkeleydb library), it would be advantageous to mimic the original logic, like running ooinstall not Perhaps we can fix just this part, by using an #if WIN32 and converting the paths to the short version before calling BerkelyDB? Then we confine the problem to only the problematic area, and the rest of the build process can stay untainted. Disclaimer: http://www.peralex.com/disclaimer.html ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: 'make check' with Windows/MSVC build?
On 04/11/2012 05:43 PM, Noel Grandin wrote: On 2012-04-11 17:31, Stephan Bergmann wrote: ooinstall needs to be fixed to work on Windows (my understanding is that it does not). Second, as long as long pathnames on Windows are still an issue (and my understanding is that they are, at least for our interaction with the berkeleydb library), it would be advantageous to mimic the original logic, like running ooinstall not Perhaps we can fix just this part, by using an #if WIN32 and converting the paths to the short version before calling BerkelyDB? My understanding is that we use classic paths (not starting with \\?) whenever they are short enough, anyway. So the problem cannot be solved with an #if, but (short of abandoning berkeleydb) needs to be worked around by making sure the LO installation is in a location with a short path (so that the paths of any files within the installation that are handed to berkeleydb are also short). Stephan ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
'make check' with Windows/MSVC build?
Hello, I've tried to do %subj% and it doesn't work for me, neither with my test build [1] nor with a tinderbox where I tried to enable it [2]. Given that this is the primary user platform, I'm rather surprised this doesn't work. Is that just some temporary breakage, or is there a bigger problem? [1] http://pastebin.com/S06cqSX6 [2] http://tinderbox.libreoffice.org/cgi-bin/gunzip.cgi?tree=MASTERfull-log=1334074224.6419 -- Lubos Lunak l.lu...@suse.cz ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: 'make check' with Windows/MSVC build?
On 10/04/12 18:50, Lubos Lunak wrote: Hello, I've tried to do %subj% and it doesn't work for me, neither with my test build [1] nor with a tinderbox where I tried to enable it [2]. Given that this is the primary user platform, I'm rather surprised this doesn't work. Is that just some temporary breakage, or is there a bigger problem? is this ooinstall thing supposed to work on Windows at all? AFAIK it symlinks stuff left and right, and running the result of that can hardly work as native Win32 program? the bigger problem is that this project doesn't seem to have any Windows developers :) ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: 'make check' with Windows/MSVC build?
is this ooinstall thing supposed to work on Windows at all? Presumably not. The way I iterate edit-compile-test on Windows (when I do it, which is not often lately) is to have a normal installation (in a virtual machine), i.e. from an installer, and then manually replace the DLL(s) I am debugging... and replace again after edit/compile... --tml ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
