[tdf-discuss] Re: Compiling in Windows
Sorry for triple posting but I want to congratulate the LibreOffice team for doing one better than OpenOffice. Although the MSVC runtime installer is executed before the actual LO installer, it is now smarter than the OOo options: if there is no need for a runtime update the user is not nagged to close other MSVC currently running. The OOo keeps (at least until 3.3.0rc6) keeps the same options described on a previous post on this topic) Thank you for listening (or reaching the same conclusions...) -- View this message in context: http://nabble.documentfoundation.org/Compiling-in-Windows-tp1792684p1952825.html Sent from the Discuss mailing list archive at Nabble.com. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://www.documentfoundation.org/lists/discuss/ *** All posts to this list are publicly archived for eternity ***
[tdf-discuss] Re: Compiling in Windows
Hi Really - this discussion belongs on the developer list; and the person > who needs to be contributing is the one complaining :-) so - I greatly > welcome your contribution here: there is a lot to do, but it is quite > do-able, and I (and Fridrich + Jesus) would be happy to mentor anyone > wanting to work on that. > Although I'm knowledgeable about this subject (I'm co-author of an Open Source alternate shell for Windows, named Emerge Desktop, which is compiled with MinGW-W64), I couldn't write a line of code even if my life depended on it... I can write Hello World, though... on a keyboard :) Those are excellent news! Thanks, Michael! -- View this message in context: http://nabble.documentfoundation.org/Compiling-in-Windows-tp1792684p1823411.html Sent from the Discuss mailing list archive at Nabble.com. -- Unsubscribe instructions: Email to discuss+h...@documentfoundation.org Posting guidelines: http://netmeister.org/news/learn2quote.html Archive: http://www.documentfoundation.org/lists/discuss/ *** All posts to this list are publicly archived ***
Re: [tdf-discuss] Re: Compiling in Windows
Hi there, On Sun, 2010-10-31 at 04:09 -0700, plino wrote: > In the spirit of Open Source it doesn't make any sense that a closed > source compiler is used. I agree - at least; it should be possible to compile with MINGW, and we're working on that. The big stumbling block, which is also a performance nightmare and pile of cruft - is the '.rdb' file generation - which demands that we dlopen a windows DLL to introspect the components it supports, in order to write the component database for the install set (services.rdb). The good news is Stefan Bergman is re-writing this to use an XML backend and we'll pick that up in the next version. > This means that the script available to compile the Windows version, > requires you to either use the limited free version from Microsoft or to buy > a the full version from them... Right - so at least Jesus has done the work to build with a non-price Microsoft version - which is a big win, > Currently MinGW-W64 is capable of compiling 32 and 64bit binaries... If the > compiler is not up to the task maybe the developers could also contribute to > that project... Really - this discussion belongs on the developer list; and the person who needs to be contributing is the one complaining :-) so - I greatly welcome your contribution here: there is a lot to do, but it is quite do-able, and I (and Fridrich + Jesus) would be happy to mentor anyone wanting to work on that. The hope is that with the new gcc Link Time Optimisation work, we may even be able to get performance and size to the same region as the Microsoft compilers do (which have traditionally produced smaller, faster binaries). HTH, Michael. -- michael.me...@novell.com <><, Pseudo Engineer, itinerant idiot -- Unsubscribe instructions: Email to discuss+h...@documentfoundation.org Posting guidelines: http://netmeister.org/news/learn2quote.html Archive: http://www.documentfoundation.org/lists/discuss/ *** All posts to this list are publicly archived ***
[tdf-discuss] Re: Compiling in Windows
Issue 107217 It is obsolete because it referred to a problem concerning the number of lines in a spreadsheet which has been increased since then (the current version supports 2^20 lines instead of the traditional 2^16) It is ignored because it is not closed. Maybe it could still be fixed to display a warning if someone is brave enough to load a file with more than 2^20 lines... Or better yet, making sure that whatever is the current limit a warning will be issued if the number of lines in the file exceeds the spreadsheet limits (lines and columns!). Obviously this has to apply to all file formats accepted by LO. It doesn't make sense that there is a warning for cvs but not for xlsx or any other... Cheers! -- View this message in context: http://nabble.documentfoundation.org/Compiling-in-Windows-tp1792684p1822014.html Sent from the Discuss mailing list archive at Nabble.com. -- Unsubscribe instructions: Email to discuss+h...@documentfoundation.org Posting guidelines: http://netmeister.org/news/learn2quote.html Archive: http://www.documentfoundation.org/lists/discuss/ *** All posts to this list are publicly archived ***
Re: [tdf-discuss] Re: Compiling in Windows
plino wrote: One of the bugs I reported (which is now obsolete, but still there) caused that a user would loose data ... And the bug has been ignored since then (this was in November 25th 2009) Could you provide the OpenOffice.org issue number? Honestly I can't understand how you can state that the bug is obsolete and at the same time complain it is being ignored, but if it is meaningful it can be solved in LibreOffice or upstream in OpenOffice.org. Best regards, Andrea Pescetti. -- Unsubscribe instructions: Email to discuss+h...@documentfoundation.org Posting guidelines: http://netmeister.org/news/learn2quote.html Archive: http://www.documentfoundation.org/lists/discuss/ *** All posts to this list are publicly archived ***
[tdf-discuss] Re: Compiling in Windows
Actually the trackers did work. Technically. But the people managing it didn't. One of the bugs I reported (which is now obsolete, but still there) caused that a user would loose data without being warned. The bug was raised from the usual P3 level to P2 (meaning it would have to be fixed before the next release) and then the next release had to be released in a rush (never understood why). And the bug has been ignored since then (this was in November 25th 2009) -- View this message in context: http://nabble.documentfoundation.org/Compiling-in-Windows-tp1792684p181.html Sent from the Discuss mailing list archive at Nabble.com. -- Unsubscribe instructions: Email to discuss+h...@documentfoundation.org Posting guidelines: http://netmeister.org/news/learn2quote.html Archive: http://www.documentfoundation.org/lists/discuss/ *** All posts to this list are publicly archived ***
Re: [tdf-discuss] Re: Compiling in Windows
plino wrote: All the developers agree that we should use open source compilers, and this will happen. But it's not ready for production yet, so probably the next few versions for Windows will still be using the Microsoft compilers. It depends on how many people volunteer to work on that. Thank you for your answer. I'm looking forward to a new official build of LO and look forward to the setup of a bug and a feature request tracker. Cheers! It would be wonderful to have a bug and feature request tracker that is more user friendly than that which was used with OOo. I gave up using it because it was so awful. -- Unsubscribe instructions: Email to discuss+h...@documentfoundation.org Posting guidelines: http://netmeister.org/news/learn2quote.html Archive: http://www.documentfoundation.org/lists/discuss/ *** All posts to this list are publicly archived ***
[tdf-discuss] Re: Compiling in Windows
> All the developers agree that we should use open source compilers, and > this will happen. But it's not ready for production yet, so probably > the next few versions for Windows will still be using the Microsoft > compilers. It depends on how many people volunteer to work on that. > Thank you for your answer. I'm looking forward to a new official build of LO and look forward to the setup of a bug and a feature request tracker. Cheers! -- View this message in context: http://nabble.documentfoundation.org/Compiling-in-Windows-tp1792684p1817339.html Sent from the Discuss mailing list archive at Nabble.com. -- Unsubscribe instructions: Email to discuss+h...@documentfoundation.org Posting guidelines: http://netmeister.org/news/learn2quote.html Archive: http://www.documentfoundation.org/lists/discuss/ *** All posts to this list are publicly archived ***
Re: [tdf-discuss] Re: Compiling in Windows
> Which is free (as in beer) for as long as Microsoft wishes. Plus it is no > longer updated and creating a script for VC 2010 requires changes. Finally, > the free VC version does not create x64 builds which I hope LO starts > producing since most (all?) modern CPUs are 64bit... Last week I made the necessary changes to compile LO with VC2010. It still requires some tweaks, but I have a full working build available. You can get the 64 bits compilers in the Windows SDK. In fact the VC Express Editions are not necessary to compile the product, as the Windows SDK also ships them. All the developers agree that we should use open source compilers, and this will happen. But it's not ready for production yet, so probably the next few versions for Windows will still be using the Microsoft compilers. It depends on how many people volunteer to work on that. Cheers, -- Jesús Corrius Document Foundation founding member Skype: jcorrius | Twitter: @jcorrius -- Unsubscribe instructions: Email to discuss+h...@documentfoundation.org Posting guidelines: http://netmeister.org/news/learn2quote.html Archive: http://www.documentfoundation.org/lists/discuss/ *** All posts to this list are publicly archived ***
[tdf-discuss] Re: Compiling in Windows
>Windows version of OOo/LO using the free (as in beer) compiler VC++ 2008 >Express. See >http://wiki.services.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows > >No absurdity involved. Which is free (as in beer) for as long as Microsoft wishes. Plus it is no longer updated and creating a script for VC 2010 requires changes. Finally, the free VC version does not create x64 builds which I hope LO starts producing since most (all?) modern CPUs are 64bit... Apparentely the OOo developers agree with me...This is a quote from the wiki article pointed by Simon; "and although Microsoft is supplying Visual Studio Express edition free of charge for the time being, they may stop to do so in the future. And it may make sense to keep OOo to be buildable with open source tools" So, given the limitations I do think it's absurd -- View this message in context: http://nabble.documentfoundation.org/Compiling-in-Windows-tp1792684p1816683.html Sent from the Discuss mailing list archive at Nabble.com. -- Unsubscribe instructions: Email to discuss+h...@documentfoundation.org Posting guidelines: http://netmeister.org/news/learn2quote.html Archive: http://www.documentfoundation.org/lists/discuss/ *** All posts to this list are publicly archived ***
[tdf-discuss] Re: Compiling in Windows
> Windows version of OOo/LO using the free (as in beer) compiler VC++ 2008 > Express. See > > http://wiki.services.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows > > No absurdity involved. > Which is free (as in beer) for *as long as Microsoft wishes*. Plus it is no longer updated and creating a script for VC 2010 requires changes. Finally, the free VC version does not create x64 builds which I hope LO starts producing since most (all?) modern CPUs are 64bit... Apparentely the OOo developers agree with me...This is a quote from the wiki article pointed by Simon; "and although Microsoft is supplying Visual Studio Express edition free of charge for the time being, they may stop to do so in the future. And it may make sense to keep OOo to be buildable with open source tools" So, given the limitations I do think it's absurd -- View this message in context: http://nabble.documentfoundation.org/Compiling-in-Windows-tp1792684p1816680.html Sent from the Discuss mailing list archive at Nabble.com. -- Unsubscribe instructions: Email to discuss+h...@documentfoundation.org Posting guidelines: http://netmeister.org/news/learn2quote.html Archive: http://www.documentfoundation.org/lists/discuss/ *** All posts to this list are publicly archived ***
Re: [tdf-discuss] Re: Compiling in Windows
Op 31-10-2010 15:20, plino schreef: @Simon, so therefore I should not use Open Source programs because I'm using a closed source OS? When did I ever suggest such a thing? Don't you see how absurd it is to need to BUY a compiler to compile a FREE program? If that were the case, I might, but it isn't. You can compile the Windows version of OOo/LO using the free (as in beer) compiler VC++ 2008 Express. See http://wiki.services.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows No absurdity involved. -- Vriendelijke groet, Simon Brouwer. | http://nl.openoffice.org | http://www.opentaal.org | -- Unsubscribe instructions: Email to discuss+h...@documentfoundation.org Posting guidelines: http://netmeister.org/news/learn2quote.html Archive: http://www.documentfoundation.org/lists/discuss/ *** All posts to this list are publicly archived ***
[tdf-discuss] Re: Compiling in Windows
@Simon, so therefore I should not use Open Source programs because I'm using a closed source OS? Don't you see how absurd it is to need to BUY a compiler to compile a FREE program? Then what is the point if the source is open and I can modify it but can't compile it because I can't afford the compiler??? This has no relation at all to the OS! BTW, read Christian's answer... apparently they do have time... This is the kind of replies that drove me off the OOo QA team. I guess there is more of the same in LO... @Christian, that is the kind of answer I was looking for. Thank you for the links. As I said I can not contribute to the programming part but I'm willing to help in whatever I can. Thanks! -- View this message in context: http://nabble.documentfoundation.org/Compiling-in-Windows-tp1792684p1816453.html Sent from the Discuss mailing list archive at Nabble.com. -- Unsubscribe instructions: Email to discuss+h...@documentfoundation.org Posting guidelines: http://netmeister.org/news/learn2quote.html Archive: http://www.documentfoundation.org/lists/discuss/ *** All posts to this list are publicly archived ***
Re: [tdf-discuss] Re: Compiling in Windows
Op 31-10-2010 12:09, plino schreef: In the spirit of Open Source it doesn't make any sense that a closed source compiler is used. Not any less sense than that a closed source OS is needed to run the program... This means that the script available to compile the Windows version, requires you to either use the limited free version from Microsoft or to buy a the full version from them... Currently MinGW-W64 is capable of compiling 32 and 64bit binaries... If the compiler is not up to the task maybe the developers could also contribute to that project... Sure, why not. They probably have too much time on their hands anyway. -- Vriendelijke groet, Simon Brouwer. | http://nl.openoffice.org | http://www.opentaal.org | -- Unsubscribe instructions: Email to discuss+h...@documentfoundation.org Posting guidelines: http://netmeister.org/news/learn2quote.html Archive: http://www.documentfoundation.org/lists/discuss/ *** All posts to this list are publicly archived ***
[tdf-discuss] Re: Compiling in Windows
In the spirit of Open Source it doesn't make any sense that a closed source compiler is used. This means that the script available to compile the Windows version, requires you to either use the limited free version from Microsoft or to buy a the full version from them... Currently MinGW-W64 is capable of compiling 32 and 64bit binaries... If the compiler is not up to the task maybe the developers could also contribute to that project... I know that traditionally the Open Source community despises Windows users, but probably in numbers they are the largest proportion of OOo (and in the future LO) users Regarding the runtimes, to be honest, I just don't like that I have to close all programs that use the same runtimes in order to be able to install a new one. And after having closed all programs the runtimes are not even updated because I already have the latest version... -- View this message in context: http://nabble.documentfoundation.org/Compiling-in-Windows-tp1792684p1815853.html Sent from the Discuss mailing list archive at Nabble.com. -- Unsubscribe instructions: Email to discuss+h...@documentfoundation.org Posting guidelines: http://netmeister.org/news/learn2quote.html Archive: http://www.documentfoundation.org/lists/discuss/ *** All posts to this list are publicly archived ***
