Re: Renaming README.Win32
Jean-Marc Lasgouttes wrote:
> Andre> On Tue, Nov 30, 2004 at 10:29:34AM +0100, Jean-Marc Lasgouttes
> Andre> wrote:
>>> I would be willing to remove them if I had a good explanation of
>>> the trade off involved. I understand they got removed from
>>> 1.4.0cvs, but then they used to be a gain when they got added. Does
>>> that mean that only old compilers had a use for it?
>
> Andre> Someone (Lars or I...) did some comparison a while ago and the
> Andre> outcome was that it was not worthwhile (anymore).
>
> Yes, I found the thread, and it says that even with 2.95 there is no
> difference.
>
> How do I write a script to remove them? Angus?
It was quite complex actually. Anyway, I think that the attached will do
the trick. Use it something like:
$ for file in src/*.[Ch]
do
sed -f pragma.sed trial.sed > tmp
cmp -s $file tmp || {
diff -u $file tmp
mv -i tmp $file
}
done
I've tested it with buffer.[Ch], which do contain the #pragma line within a
#ifdef __GNUG__
...
#endif
block and with BoostFormat.h, which contains stuff other than #pragma
within this block. It works in both cases.
In all cases, the loop will ask you if you wish to overwrite the file, so
it should be perfectly safe. So long as you remain awake...
--
Angus/^[ ]*\#[ ]*ifdef[]\{1,\}__GNUG__/{
:loop
# If we're not at the end of the script.
$!{
# Grab a new line of data and delete everything up
# to the embedded newline
N
s/.*\n//
# If this is the end of the #if ... #endif block
/^[ ]*\#[ ]*endif/{
# Move the contents of the hold space into the pattern space.
# Empty the hold.
s/.*//
x
s/^\n//
# If the pattern space is not empty, then wrap it in
# #ifdef __GNUG__ #endif
/^$/!s/\(.*\)/#ifdef __GNUG__\
\1\
#endif/
# Go to the end of the script.
b
}
# We haven't reached the end of the #if ... #endif block.
# if the line is #pragma {implementation,interface} then remove it
/^[ ]*#[]*pragma[ ]\{1,\}interface[ ]*$/{
s/.*//
b continue
}
/^[ ]*#[]*pragma[ ]\{1,\}implementation[ ]*$/{
s/.*//
b continue
}
# The line contained something other than #pragma, so save it.
H
# Grab another line.
:continue
bloop
}
}
Re: Renaming README.Win32
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes: Andre> On Tue, Nov 30, 2004 at 10:29:34AM +0100, Jean-Marc Lasgouttes Andre> wrote: >> I would be willing to remove them if I had a good explanation of >> the trade off involved. I understand they got removed from >> 1.4.0cvs, but then they used to be a gain when they got added. Does >> that mean that only old compilers had a use for it? Andre> Someone (Lars or I...) did some comparison a while ago and the Andre> outcome was that it was not worthwhile (anymore). Yes, I found the thread, and it says that even with 2.95 there is no difference. How do I write a script to remove them? Angus? JMarc
Re: Renaming README.Win32
On Tue, Nov 30, 2004 at 10:29:34AM +0100, Jean-Marc Lasgouttes wrote: > I would be willing to remove them if I had a good explanation of the > trade off involved. I understand they got removed from 1.4.0cvs, but > then they used to be a gain when they got added. Does that mean that > only old compilers had a use for it? Someone (Lars or I...) did some comparison a while ago and the outcome was that it was not worthwhile (anymore). Andre'
Re: Re: Renaming README.Win32
On Tue, Nov 30, 2004 at 09:38:01AM +0100, [EMAIL PROTECTED] wrote: > > That's strange as LyX 1.4.0cvs + kdewin's Qt port compile almost > > out-of-the box on Win2k with Cygwin (gcc 3.3.1 I believe). > > Hmmm... You mean Qt/Win32 GPL? I think so. At least I am fairly sure the undo fix I recently committed did run through a compiler and given that ./configure does not pick up MSVC++ and Trolltech's Qt for Windows does not compile with gcc I am fairly sure that it was the kdewin's GPL'ed Qt/Win32 port. > What about LyX's "configure" tool (not the configure script for > compilation)? Does it work or does it run/wait endlessly? I had a full cygwin installation, too, so I assume most of the plaything were picked up from there... > > > In order to compile LyX 1.3.1, you have to remove all "#pragma > > > interface" and "#pragma implementation" lines from the source > > > code. > > > > Do we still have such? I thought they had been removed some time > > ago... > > Yes, they are still there... Should be removed. Andre'
Re: Renaming README.Win32
> "Michael" == <[EMAIL PROTECTED]> writes: >> > In order > to compile LyX 1.3.1, you have to remove all "#pragma >> interface" and > "#pragma implementation" lines from the source >> code. >> >> Do we still have such? I thought they had been removed some time >> ago... Michael> Yes, they are still there... I would be willing to remove them if I had a good explanation of the trade off involved. I understand they got removed from 1.4.0cvs, but then they used to be a gain when they got added. Does that mean that only old compilers had a use for it? JMarc
Re: Re: Renaming README.Win32
Andre Poenitz <[EMAIL PROTECTED]> schrieb am 29.11.2004, 20:31:33: > That's strange as LyX 1.4.0cvs + kdewin's Qt port compile almost > out-of-the box on Win2k with Cygwin (gcc 3.3.1 I believe). Hmmm... You mean Qt/Win32 GPL? That would be great news! Actually, I wasn't successful; maybe I should give it another try. What about LyX's "configure" tool (not the configure script for compilation)? Does it work or does it run/wait endlessly? > > In order > > to compile LyX 1.3.1, you have to remove all "#pragma interface" and > > "#pragma implementation" lines from the source code. > > Do we still have such? I thought they had been removed some time ago... Yes, they are still there... > > THEN you can enjoy LyX 1.3.1 on the Windows platform! > > \sum and \prod are shifted upwards, arent' they? No, IMHO they look good (cygwin with Qt/X11). > > I tried to compile Qt Win32 with cygwin a couple of days ago and I > > failed. I don't remember the details but it was definitely too > > difficult to fix with a few minutes (by myself :-)). > > How do you compile Qt Win32 with gcc? I refer to Qt Win32 GPL. Regards, Michael
Re: Renaming README.Win32
On Mon, Nov 29, 2004 at 04:22:01PM +0100, [EMAIL PROTECTED] wrote: > > Hello everybody, > > for various reasons, I'm bound to the Windows platform (XP) at present. > > I have been struggling with the compilation of LyX on Windows for some > time That's strange as LyX 1.4.0cvs + kdewin's Qt port compile almost out-of-the box on Win2k with Cygwin (gcc 3.3.1 I believe). There is only one linker flag missing, and the error message one obtains on the first run is directly pointing to this flag (I forgot, which...) > Cygwin has a nasty bug that prevents you from running any LyX version at > present. The problem is related to the gcc 3.3.3/3.4.1 output (I don't > know the full details but it is related to the way constants are > stored). Compilation/Linking works but you cannot start the > application. Ah, that's the problem... > However, if you switch back to gcc 3.3.1, you can - in principle - > compile and run LyX 1.3.1 with the Qt X11 library provided by > kde-cygwin.sf.net. Unfortunately, the cygwin setup tool no longer > allows you to downgrade to gcc 3.3.1. But have a look at the various > mirrors; the package is still there and you can install it by hand. > > Of course, this is not the whole story (what did you expect?): In order > to compile LyX 1.3.1, you have to remove all "#pragma interface" and > "#pragma implementation" lines from the source code. Do we still have such? I thought they had been removed some time ago... > THEN you can enjoy LyX 1.3.1 on the Windows platform! \sum and \prod are shifted upwards, arent' they? > Cygwin & Qt Win32 > - > > I tried to compile Qt Win32 with cygwin a couple of days ago and I > failed. I don't remember the details but it was definitely too > difficult to fix with a few minutes (by myself :-)). How do you compile Qt Win32 with gcc? And if you did use something else than gcc (say, e.g., cl), how did you run configure? Andre' PS: Anybody any experiences with using Apache authenticating against sone Win2003 domain server over ldap? If I manage this I might be able to increase the number of Linux server in this particularily Dark Place by 100%... [I think I know the theory by now. However, whatever I try, I get some error 84 (or 86?) "Authentication failed" error, even when running a simple 'ldapsearch' with the -x/-D argument. Unfortunately, the Windows server do not log anything, so that's about the only information I have. What's the syntax of the -D parameter? -D "cn=whatever, dc=myorg, dc=de"? Or something completely different? Helpful responses please to andre w a s y. de.]
Re: Renaming README.Win32
Hello everybody,
for various reasons, I'm bound to the Windows platform (XP) at present.
I have been struggling with the compilation of LyX on Windows for some
time and I thought you might be interested in an experience report:
Cygwin & Qt X11/free & LyX 1.3.1
Cygwin has a nasty bug that prevents you from running any LyX version at
present. The problem is related to the gcc 3.3.3/3.4.1 output (I don't
know the full details but it is related to the way constants are
stored). Compilation/Linking works but you cannot start the
application.
However, if you switch back to gcc 3.3.1, you can - in principle -
compile and run LyX 1.3.1 with the Qt X11 library provided by
kde-cygwin.sf.net. Unfortunately, the cygwin setup tool no longer
allows you to downgrade to gcc 3.3.1. But have a look at the various
mirrors; the package is still there and you can install it by hand.
Of course, this is not the whole story (what did you expect?): In order
to compile LyX 1.3.1, you have to remove all "#pragma interface" and
"#pragma implementation" lines from the source code.
THEN you can enjoy LyX 1.3.1 on the Windows platform! Finally... But
please note that Germany Umlauts are not printed correctly in the LyX
menus ("a instead of ä)
Cygwin & Qt X11/free & LyX 1.4.0
All I said before, also applies to LyX 1.4.0. However, the final
application is not usable. The "configure" script that comes along with
LyX (to determine the available text classes etc.) does not complete.
You have to press Ctrl-C to stop it. When you start LyX nevertheless,
you are not able to set layouts like "itemize" or "description" (might
be related, might be not...)
Cygwin & Qt Win32
-
I tried to compile Qt Win32 with cygwin a couple of days ago and I
failed. I don't remember the details but it was definitely too
difficult to fix with a few minutes (by myself :-)).
MinGW & Qt Win32
The snapshot available on the kde-cygwin.sf.net website does not work!!!
However, two days ago I was able to check out a working version from
CVS. I could compile & start the Qt applications (designer...) and they
looked good. Use cmd.exe (not MSYS) and follow the compilation
instructions. Don't use MSYS if you don't want to spend time on
fixing. The Qt library produced a lot of debug output and IMHO was a
bit slow (maybe due to the debug output).
Highly motivated, I started compiling LyX 1.4.0. However, in order to
run autogen.sh, I needed a few more tools (partly available on the
mingw website). Don't forget to install some Perl distribution. Even
after the installation of all required tools, I couldn't compile LyX.
Once again, I don't remember the details (big sorry) but it was not
trivial again. Or maybe I was just to stupid...
Summary: If you are in a hurry or you can just spend a few hours on LyX,
download an older version of gcc-cygwin and use the QT/X11 libary. If
you are looking for adventures, choose another option and share your
experiences with us :-)
Kind regards,
Michael
Re: Renaming README.Win32
"Angus Leeming" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > I have MinSyS installed on a WinXP machine. I guess I could create a > native Windows LyX executable using the gcc toolchain, no? > Yep. The regular mingw distro (gcc etc.) + msys will do. There are instructions for Qt on http://kde-cygwin.sourceforge.net/qt3-win32/compile-mingw.php. Good luck, Ruurd
Re: Renaming README.Win32
Ruurd Reitsma wrote: > "Angus Leeming" <[EMAIL PROTECTED]> wrote in > message news:[EMAIL PROTECTED] >> Edwin Leuven wrote: >> >> Here, 'formal support' means merging changes made by Ruurd to get >> LyX to compile with the half-baked compiler (Borland) that was used >> to compile the qt/win32 library provided by Trolltech. Hypocritical >> or not, that is never going to happen for reasons other than >> licencing religion. >> > > Where did Borland come from? My (poor) memory. > My changes started out as a > win32-native x11 xforms port, to be compiled by gcc (mingw). So just > support for the OS. Then, when the LyX Qt GUI came along, I had to > change some stuff to be able to compile with the Intel compiler & > the M$ linker. That part you wouldn´t want to include in the LyX > source. If you dont want to (ever) include the OS specific part, you > might as well as well cut out the cygwin things. > > Anyway, the GPL Qt from the kde-cygwin project works very well > nowadays. Especially because LyX only uses a very small part of the > Qt lib. I really don´t have the time to properly test and debug > myself, but I´m willing to help out anyone that want to persue this. > With a (free) Qt binary, it´s fairly easy to cross compile eg on > Linux. I have MinSyS installed on a WinXP machine. I guess I could create a native Windows LyX executable using the gcc toolchain, no? > Ruurd -- Angus
Re: Renaming README.Win32
"Angus Leeming" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Edwin Leuven wrote:
>
> Here, 'formal support' means merging changes made by Ruurd to get LyX to
> compile with the half-baked compiler (Borland) that was used to compile
> the qt/win32 library provided by Trolltech. Hypocritical or not, that is
> never going to happen for reasons other than licencing religion.
>
Where did Borland come from? My changes started out as a win32-native x11
xforms port, to be compiled by gcc (mingw). So just support for the OS.
Then, when the LyX Qt GUI came along, I had to change some stuff to be able
to compile with the Intel compiler & the M$ linker. That part you wouldn´t
want to include in the LyX source. If you dont want to (ever) include the OS
specific part, you might as well as well cut out the cygwin things.
Anyway, the GPL Qt from the kde-cygwin project works very well nowadays.
Especially because LyX only uses a very small part of the Qt lib. I really
don´t have the time to properly test and debug myself, but I´m willing to
help out anyone that want to persue this. With a (free) Qt binary, it´s
fairly easy to cross compile eg on Linux.
Ruurd
begin 666 lyx-win32.diff.bz2
M0EIH.3%!629366WZ(,X`$?O?@'QR?_Z_8!X\`=U?2UW>X^O<
MP^L!]>2[8]O>17ON^3=Y7L\*F9=,6^WO>Q\^'I()MMM;;MIUW6UKJNE%WAJ>IM)ZC
M0T]1Z(P::$#2$9(U/*8H\IIY0/U(:'J&0T ```#U``,0$A34]-*?HIII^J'J
[EMAIL PROTECTED]/4]([EMAIL PROTECTED] -- 2:2A(F3!,DV@@V5/!-!/32#3R@: ,@`- -&@B4
MFBF J?M4_1*>-4_*,4VH`/4`\AJ [EMAIL PROTECTED](B( 03 283$:3(Q)/U3PD
M_5 ](9 -`#0-H1M-\BB$><8J*O;M5W[[EMAIL PROTECTED]&*+%)Q<0'$Q8L*B"M3CM#%:.6X@,N61LP2Y,E
MS"W)BQ_U_S^GSYIXW0W:UK
MGS'47Y>[K\^EWNQ8Q'[3W*:*#.W*H_<0Z/V\0U[?P:J8^ZW^HX6EC;NSL<1X-5AKJL4#8$*-4* I\)=%)0Q;F]9,S*''&@&0NJBI
MF?FBDH6V8MN+)C2FI0,]V?JXUO:K=AV?45OGF-Y&B0`I3)=\7Q6;X1+,2NZ93#J_+-C*#&'XVR1'ZCL("\2ZWEOE&O<&Z([EMAIL PROTECTED]'6^3BD,X\BNM'L:CQ\OE^'[EMAIL PROTECTED]
MV#?&;M=VZD4)0$H-NX=XSIHLAR:I\3X&8U_E>X[=J\KJ],&GS//BV2,&#E'O
MOZ+W/GQQX;\$<#2E]R#R=U M]N)F:XA#&[EMAIL PROTECTED];?W2MC\>Q^Q
M^RU[@/F>;22!L2'$(2*-<6(7%H%0"K @L"3[O.A2I?^K+\%XGO/$]6:TI3>M
MLHJ_S&1#*!)4E#:@@@[EMAIL PROTECTED])C75K7>2QF-]9RV2-AYM#8!?U$
M!#+&(U_LA'GPR&SZ$&A^&W!2L7^.:@.4YA9[GCZNOQ(:>]?87&% 4?>%TLO\2*KQ9IG)-+;K-]=NNVGK._>ON?G\M
M2"]I*\RX$5SW^G]-LV$IO&*\#%2.S0007;9J3NO2;O^XFOZEV9;*&QWK:9$%
M9/7A4W_O-M,[EMAIL PROTECTED]<"M&0UQ>#O44LS&693U21E#>#*;[EMAIL
PROTECTED]&.PCDMYB
[EMAIL PROTECTED]&?E1H,;WX$II&6[3;;XD"RW=[IG[\..+37EQ[J\:L]/DB++/A=99:
M!OJ/;RKNX$U1HJ.B+N;S)A)N`68,-4+INELV_CGKMPF>GH95DM!'$%YZ+AO!
M)C[IR*C=%I"B%%S8(5F#$\VN0NXXNNV9NR>]MO%N6O7Y3C7BNCRQV&)%\+ 5
MC0- G1RW*1D1^_U\L". VUWDZ7\E]W.#);>\>[I&P%J7#\Y%PN\,59\<
MLR<]_(556RUH%-)=R>)+A9BWMQX'=W=W=WMM
O'KM)W/'O]\O MD102[$--.#I4=#C8JV0T)8F/H:Z,O1V9=]'S21\(V-*
MT>;;:U9KPN;J*+*3W=FP:7F6>-\WM[917QM(TF*O'DTJYA3
M8#L8-S#'%BC#Z#Y&PPAR'#\5/B],1(G^RH'R:2XM'-RZ0_7:'AW?G.'YCO"Q
M4W>,GIHKIF[C7J\YY&DE]4IZ?MV?LTA"/,]DA"[EMAIL PROTECTED]
M:&Y2*)[EMAIL PROTECTED](MGK+BL,5CA3&9$459!6LPPR9)[EMAIL PROTECTED],4B,[EMAIL
PROTECTED];85
M-#?.VT-]NS48C60Z21!I$#"!D^UN8\#H)=D2-81H(CC=1U _9\71V:-7<
M0?<.?E3'J[^F?5&)"G;%RJ#DK(*A2LQPF@& >G1C3[07DL)G(3T]"UK+UE66
MR"A",WLZ945_KZ6_[X[K.N=F 3X8D6+/2
MWK:+U3\+9Y:^3&:C'56^5+;\!L,%+":,YW>?HFWAGM3\]J%1%M
MD[PT9ZY(2*1 /:C &416B#$6@ Q0Z[\7PJK$B,DR^G`RAA50^6+O$B&Q(R4880$IE.4I494&HONI?=,E'8?S(VM9C;
M"C"&>"27Q0)I'E\Y0*4);Z `V)M!N.X]DHK^"!KCW&XN\8
M4[?/2G5[;[EMAIL PROTECTED]'I[U&[EMAIL PROTECTED]'-G%QZ^/YD\^VPFTE
M$GBM`SU)9HBHAX:IM$K2)6+%XB414Q$JR)6T%X%0P((=G>0JMF>M:K9UB7&+
MA-QZ,3[V#Y:Z&N_H:'3>+9]1;,',I;3BG20XYE']M0L 8-
M"DV6AXYKI)F<1B6$3IQKB>93\RE31%/>W7KS&[EMAIL PROTECTED]:E(I @;@C(>DVX?
M:-#DZR;>W(SL;>KC6V*6M)[EMAIL PROTECTED]
M+V#H)* ()(%;Z!&Y_(]:%4E;,V-8;?,SH;V,`KY1:#B$^5/#"DD([EMAIL PROTECTED]>@]
M.FQOGS#F`3O'[EMAIL PROTECTED]
MJY6 ZN3N6O-!V'%P556C*(I "!>+E!(N)D
M$&FF3W*!B0U._K*(O7OZPP]-DHQ6C[1"D:0!RR:;^_
M;'RF[K^FM:P-E/%J%![Q#<[EMAIL PROTECTED] 4#6.`7@:G=;4=>4M9W<2L35Y
MN*DW]: C.->2_'I0VW4%.%+A>5\.2Q0Y!HFV4\CCO,GR;'+'L_.3I8'>*03^
MEFHSH0`\OX["L/TQF64(C)+EDF(2L7% \/LE$/=0;E$.'J>$UR$US;T;+:O@
MI1I!K&XCE.4G.N.PU?"Z*F,?TV>%OQO_\3/WHW)"%+]^&V#D#M]7R>*!43(%5DP'X$\R"S\VMD_
M+P'V2IQL%C7Z;/CILDNCW#!*^(DSGW+OAS9JI3W?HZ4#WR>_#*1J7QGDFBK0
M7"[EMAIL PROTECTED])Y*PSB42P_7)!%A4QC/CV\R6#9+@/D'[EMAIL PROTECTED]
MZ-/B\?,&`_ZJ\9UH&DY16J;D9$$T309:H'24&'K!%[<<\$MVM2Y=ZM=JGS9RA>FV#5(VUX>PVSW$4V'64PIA7H-CVC+=_U%QL0>8S,T:
M]BD8*\,1LJA'35KL="4G2[Z;O35+6U3&NF:G\T\(TR_V05=*?F<_QY_.3.&PGH1WAW^(
[EMAIL PROTECTED]'@3FW'N*'T[ZFH1Y#H^E;D4$]] J10L==L"[#U3,/.CP3
MUE,8$%VFE4WV.L)7Y^Y3R?N&5V+]9!+-3G:VB-B\R7US"W<#@,DSMZ=6,O=2
MLS_*KS)I>>[EMAIL PROTECTED]>D$`?DLXCO..#&^W=\O5]([P)YP"
MIS/EY4N/A,)^RE^"=N \,I4Q8!SL&T=X/4YPHR'80I)6U(1",F1>GG1XSY^_
MX]7A&1M=_9/'6\PAA*\+8SC#4D,,*8-4(J%_VAK,EJ2/L5JTQ-#(,[EMAIL PROTECTED]
M/F,8&Y+V$#6O#QC8<8U?/8G:GX9B2C*7CZR7^N% JX='E4A>R)M?(8'$=^WL
M&P7M:!GP!B9'$O($$"Y5&QFA\AD1R#=L+%6$4048KTLH*'+QN_4?"!! [#_8
MZD3(-OWY=*M514& 16U%D69%SNN&IU=HX$T\)VR3SC(P%51BR*B0#>@K\R!<
M]-2+"AGKZ6(:/,VB\VN1P)4S=*I1NE>[EMAIL PROTECTED]>H]M1>"13MN
Re: Renaming README.Win32
Jean-Marc Lasgouttes wrote: Certainly, using it goes against the spirit of Open Source software and we have chosen, therefore, not to provide formal support for Ruurd's port. > > Edwin> I find this statement hypocritical given the exception in LyX's > Edwin> license for xforms which goes against the spirit of OS as well. > > Jean-Marc> Except that xforms never had a non-commercial restriction > Jean-Marc> such as the one from Qt, as far as as know. This makes a > Jean-Marc> big difference. > > OK, I have to correct this statement, now that I found an original > xforms license, which says: > > Forms Library is not public domain. It is copyright (©) by T.C. Zhao > and Mark Overmars, with all published and unpublished rights reserved. > However, permission to use for non-commercial and not-for-profit > purposes is granted. You may not use xforms commercially (including > in-house and contract/consulting use) without contacting > ([EMAIL PROTECTED]) for a license > arrangement. Use of xforms for the sole purpose of running a publically > available free software that requires it is not considered a commercial > use. > > > However, I know that the intent of the license was just to avoid > abuse, while Trolltech has a market share to defend. Given that LyX 1.4.x requires XForms >= 1.0, and given that XForms 1.0 was released under the GPL, LyX currently uses only GPL-compatible libraries. That is, there is no further need for the relaxed license. Does the FSF not have any advise on what to do in such a situation? -- Angus
Re: Renaming README.Win32
> "Jean-Marc" == Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: > "Edwin" == Edwin Leuven <[EMAIL PROTECTED]> writes: Edwin> Angus Leeming wrote: >>> Certainly, using it goes against the spirit of Open Source >>> software and we have chosen, therefore, not to provide formal >>> support for Ruurd's port. Edwin> I find this statement hypocritical given the exception in LyX's Edwin> license for xforms which goes against the spirit of OS as well. Jean-Marc> Except that xforms never had a non-commercial restriction Jean-Marc> such as the one from Qt, as far as as know. This makes a Jean-Marc> big difference. OK, I have to correct this statement, now that I found an original xforms license, which says: Forms Library is not public domain. It is copyright (©) by T.C. Zhao and Mark Overmars, with all published and unpublished rights reserved. However, permission to use for non-commercial and not-for-profit purposes is granted. You may not use xforms commercially (including in-house and contract/consulting use) without contacting ([EMAIL PROTECTED]) for a license arrangement. Use of xforms for the sole purpose of running a publically available free software that requires it is not considered a commercial use. However, I know that the intent of the license was just to avoid abuse, while Trolltech has a market share to defend. JMarc
Re: Renaming README.Win32
> "Edwin" == Edwin Leuven <[EMAIL PROTECTED]> writes: Edwin> Angus Leeming wrote: >> Certainly, using it goes against the spirit of Open Source software >> and we have chosen, therefore, not to provide formal support for >> Ruurd's port. Edwin> I find this statement hypocritical given the exception in LyX's Edwin> license for xforms which goes against the spirit of OS as well. Except that xforms never had a non-commercial restriction such as the one from Qt, as far as as know. This makes a big difference. Distribution of things done with qt2 non commercial is very limited. JMarc
Re: Renaming README.Win32
Angus Leeming wrote: Here, 'formal support' means merging changes made by Ruurd to get LyX to compile with the half-baked compiler (Borland) that was used to compile the qt/win32 library provided by Trolltech. Hypocritical or not, that is never going to happen for reasons other than licencing religion. i wasn't referring to the support issue. just to motivation the lack of support by the "spirit of open source" which isn't reflected by the exception that lyx makes for xforms. this i find hypocritical. Why not simply: "In addition, Ruurd Reitsma has created a native port of LyX on Win32 using the binary Qt/Win32 2.3.0 library. We have chosen not to provide formal support for Ruurd's port." ...and if you're serious about "the spirit of OS", well then change the license... regards, ed.
Re: Renaming README.Win32
Edwin Leuven wrote: > Angus Leeming wrote: >> Certainly, using it >> goes against the spirit of Open Source software and we have chosen, >> therefore, not to provide formal support for Ruurd's port. > > I find this statement hypocritical given the exception in LyX's license > for xforms which goes against the spirit of OS as well. > > (and in the same way as linking to qt-win32 IMO...) > > regards, ed. Everyone is entitled to their own opinion of course. Here, 'formal support' means merging changes made by Ruurd to get LyX to compile with the half-baked compiler (Borland) that was used to compile the qt/win32 library provided by Trolltech. Hypocritical or not, that is never going to happen for reasons other than licencing religion. Personally, I would be very happy if "The LyX Team" announced that all code contributed to LyX 1.4.x and after was subject to the pure GPL. I understand that such a hardening of the licence is indeed possible, but IANAL. Just my two cents. -- Angus
Re: Renaming README.Win32
Angus Leeming wrote: Certainly, using it goes against the spirit of Open Source software and we have chosen, therefore, not to provide formal support for Ruurd's port. I find this statement hypocritical given the exception in LyX's license for xforms which goes against the spirit of OS as well . (and in the same way as linking to qt-win32 IMO...) regards, ed.
Re: Renaming README.Win32
Jean-Marc Lasgouttes wrote: > Angus> Shouldn't README.Win32 be renamed as README.Cygwin? If we > Angus> want a README.Win32 then how about something like: > > Jean-Marc> Why not, but we should get our facts right. > Or maybe merge the two file in one. I think we should keep them separate. How about: README for Win32 LyX has been ported to Win32 using the Cygwin environement. See README.Cygwin for details. In addition, Ruurd Reitsma has created a native port of LyX on Win32 using the binary Qt/Win32 2.3.0 library. It is not clear whether we are legally allowed to distribute this library. Certainly, using it goes against the spirit of Open Source software and we have chosen, therefore, not to provide formal support for Ruurd's port. Having said that, you'll find the executable, together with lots of useful tips, on Ruurd's site: http://www.home.zonnet.nl/rareitsma/lyx/ The Win32 pages on the LyX wiki will also be useful: http://wiki.lyx.org/pmwiki.php/LyX/LyX Finally, you'll find lots of friendly help on the lyx users' mailing list: [EMAIL PROTECTED] Trolltech has stated that they do not intend to release Qt/Win under the GPL. However, it is likely that a native port of LyX to Windows will be supported formally in the future, for two reasons: * A frontend for LyX using the Gtk libraries is under active development. The Gtk libraries for Win32 are indeed released under the GPL. * Some success has been reported compiling LyX on Win32 using the GPL-ed port of qt/x11 to Win32 by the kde-cygwin project. See http://kde-cygwin.sourceforge.net/qt3-win32/index.php -- Angus
Re: Renaming README.Win32
Jean-Marc Lasgouttes wrote: > Angus> Shouldn't README.Win32 be renamed as README.Cygwin? > Angus> If we want a README.Win32 then how about something like: > > Why, not, but we should get our facts right. Sure. Thanks for the corrections, but see below. > Angus> Ruurd Reitsma has created a native port of LyX on Win32, > using Angus> the old but GPL-ed Qt/Win32 2.3.0 library. > > This is not GPL-ed, but a binary lib with non-commercial license. > For this reason it is not clear that it is allowed to distribute > lyx/win32 (not that there is a copy of it on our wiki). Is that 'not' or 'note'? What are you trying to say? > Angus> * Trolltech have stated that modern versions of the Qt > library on Angus> Win32 will no longer be released under the GPL. > > Rather: "Trolltech has stated that they do not intend to release > Qt/Win under the GPL" > > JMarc -- Angus
Re: Renaming README.Win32
> "Jean-Marc" == Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> Shouldn't README.Win32 be renamed as README.Cygwin? If we want Angus> a README.Win32 then how about something like: Jean-Marc> Why not, but we should get our facts right. Or maybe merge the two file in one.
Re: Renaming README.Win32
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> Shouldn't README.Win32 be renamed as README.Cygwin? If we want Angus> a README.Win32 then how about something like: Why, not, but we should get our facts right. Angus> Ruurd Reitsma has created a native port of LyX on Win32, using Angus> the old but GPL-ed Qt/Win32 2.3.0 library. This is not GPL-ed, but a binary lib with non-commercial license. For this reason it is not clear that it is allowed to distribute lyx/win32 (not that there is a copy of it on our wiki). Angus> * Trolltech have stated that modern versions of the Qt library on Angus> Win32 will no longer be released under the GPL. Rather: "Trolltech has stated that they do not intend to release Qt/Win under the GPL" JMarc
Renaming README.Win32
Shouldn't README.Win32 be renamed as README.Cygwin? If we want a README.Win32 then how about something like: Ruurd Reitsma has created a native port of LyX on Win32, using the old but GPL-ed Qt/Win32 2.3.0 library. Find it, together with lots of useful info at http://www.home.zonnet.nl/rareitsma/lyx/ The Win32 pages on the LyX wiki will also be useful: http://wiki.lyx.org/pmwiki.php/LyX/LyX The LyX developers do not currently provide formal support for LyX running natively on Win32 for a number of reasons: * Trolltech have stated that modern versions of the Qt library on Win32 will no longer be released under the GPL. * We have little experience of Windows software. However, it is likely that the Win32 platform will be supported formally in the future: * A frontend for LyX using the Gtk libraries is under active development. The Gtk libraries for Win32 are indeed released under the GPL. * Some success has been reported compiling LyX on Win32 using the GPL-ed port of qt/x11 to Win32 by the kde-cygwin project. See http://kde-cygwin.sourceforge.net/qt3-win32/index.php -- Angus
