Yes I am aware of it, and I actually got it, compiled it, and tried the example programs. They do not work 100%, and since I needed a production program, I felt that it was not yet good enough. But it does work, and I expect that within a reasonable amount of time it would be possible to use it with LyX.

To see the problems, start examples/textedit, and try to switch fonts, type a bit and so on. After a while the text simply disappears.

You are probably right that they probably debugged the gcc2/cygwin build, but I think that their version is fairly heavily hacked relative to the original Trolltech code, so I felt it would be easier to start with clean Trolltech code and fix it as I go.

I think that it might be wise to wait until they finish before distributing Win32 binaries, since binaries that depend on X11, although they work well, really need an complete cygwin environment. Non-X11 builds will be a lot easier to distribute with a few unix-like utilities, like Ruurd distributes his version.

Sivan

Jean-Marc Lasgouttes wrote:

"Sivan" == Sivan Toledo <[EMAIL PROTECTED]> writes:


Sivan> I finally managed to build LyX 1.3.3 (essentially no source
Sivan> changes, except for 3 declarations that I had to comment out)
Sivan> on top of Qt 3 on cygwin, as an X11 client. See the details at

Sivan> http://www.tau.ac.il/~stoledo/lyx_cygwin.html

Sivan> The page mentions a few problems in the sources (these few
Sivan> declarations), in the makefiles, and also in the run-time
Sivan> scripts, like convertDefault.sh. It would be good to fix them
Sivan> in the sources. I'll be happy to test.

Hi Sivan,

Concerning the qt problems mentionned on your page, did you consider
the qt-cygwin port present on the following page?
  http://kde-cygwin.sourceforge.net/qt3/

I would think that they had to tackle the same problems as you did, and since they provide a binary distribution against gcc2, I think you
should be able to use it directly.


There is also a native win32/cygwin port in progress on the same site.

I would like to have more details about the places where you had to
comment out some things. It should be easy to fix. Actually, from your
atoi hint, I suspect that the appended patch helps.

I would be interested to know whether you can use qt3-cygwin...

JMarc



------------------------------------------------------------------------

Index: src/mathed/ChangeLog
===================================================================
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/ChangeLog,v
retrieving revision 1.299.2.5
diff -u -p -r1.299.2.5 ChangeLog
--- src/mathed/ChangeLog 22 Sep 2003 14:40:39 -0000 1.299.2.5
+++ src/mathed/ChangeLog 11 Feb 2004 13:45:55 -0000
@@ -1,3 +1,8 @@
+2004-02-11 Jean-Marc Lasgouttes <[EMAIL PROTECTED]>
+
+ * math_parser.C: + * math_sizeinset.C: atoi is not always in std:: namespace
+
2003-09-18 Jean-Marc Lasgouttes <[EMAIL PROTECTED]>
* math_symbolinset.C (metrics): apply a different hack to metrics
Index: src/mathed/math_parser.C
===================================================================
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/math_parser.C,v
retrieving revision 1.259.2.3
diff -u -p -r1.259.2.3 math_parser.C
--- src/mathed/math_parser.C 11 Jun 2003 14:28:48 -0000 1.259.2.3
+++ src/mathed/math_parser.C 11 Feb 2004 13:45:55 -0000
@@ -78,7 +78,9 @@ using std::ios;
using std::endl;
using std::fill;
using std::vector;
+#ifndef CXX_GLOBAL_CSTD
using std::atoi;
+#endif
//#define FILEDEBUG
Index: src/mathed/math_sizeinset.C
===================================================================
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/math_sizeinset.C,v
retrieving revision 1.28
diff -u -p -r1.28 math_sizeinset.C
--- src/mathed/math_sizeinset.C 27 Nov 2002 10:30:28 -0000 1.28
+++ src/mathed/math_sizeinset.C 11 Feb 2004 13:45:55 -0000
@@ -11,7 +11,9 @@
#include "math_support.h"
#include "support/LOstream.h"
+#ifndef CXX_GLOBAL_CSTD
using std::atoi;
+#endif
MathSizeInset::MathSizeInset(latexkeys const * l)
: MathNestInset(1), key_(l), style_(MathStyles(atoi(l->extra.c_str())))



Reply via email to