Re: [tdf-discuss] Re: Compiling in Windows

2010-11-01 Thread Andrea Pescetti
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

[tdf-discuss] Re: Compiling in Windows

2010-11-01 Thread plino
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

Re: [tdf-discuss] Re: Compiling in Windows

2010-11-01 Thread Michael Meeks
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

[tdf-discuss] Re: Compiling in Windows

2010-11-01 Thread plino
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

[tdf-discuss] Re: Compiling in Windows

2010-10-31 Thread plino
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

Re: [tdf-discuss] Re: Compiling in Windows

2010-10-31 Thread Simon Brouwer
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

[tdf-discuss] Re: Compiling in Windows

2010-10-31 Thread plino
@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

Re: [tdf-discuss] Re: Compiling in Windows

2010-10-31 Thread Simon Brouwer
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

Re: [tdf-discuss] Re: Compiling in Windows

2010-10-31 Thread Jesús Corrius
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

Re: [tdf-discuss] Re: Compiling in Windows

2010-10-31 Thread Robert Derman
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.

[tdf-discuss] Re: Compiling in Windows

2010-10-31 Thread plino
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