[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Texmacs-dev] Qt TeXmacs-, Qt-4.6.3 compilation error

From: Gubinelli Massimiliano
Subject: Re: [Texmacs-dev] Qt TeXmacs-, Qt-4.6.3 compilation error
Date: Mon, 8 Nov 2010 12:40:56 +0100

 this should be fixed now in svn. The problem was inclusion of QStatusbar. The correct spelling is QStatusBar, but on mac the error does not appear since the filesystem is case-insensitive.



On 8 nov. 10, at 08:50, Sam Liddicott wrote:

I've been using --enable-qt on linux without problems until recently.

With todays svn head I've had to apply the attached patch.

and it's still not compiling yet, problems finding the include file QStatusBar, so I'm trying to find which ubuntu package provides that


Mon Nov 08 2010 06:14:54 AM GMT from "Andrey G. Grozin" <address@hidden> Subject: Re: [Texmacs-dev] Qt TeXmacs-, Qt-4.6.3 compilation error
On Fri, 5 Nov 2010, Miguel de Benito Delgado wrote:
  I read at qtcentre (http://www.qtcentre.org/archive/index.php/t-7223.html) that this problem was due
to duplicate symbol definitions in the preprocessor and then it was related to the order of inclusion
of header files.
Thanks! After reading this, I wrote the following patch which fixes the
compilation problem in Linux.

diff -r -U1 TeXmacs- TeXmacs-
--- TeXmacs- 2010-10-23 02:38:02.000000000 +0700
+++ TeXmacs- 2010-11-08 19:43:16.000000000 +0600
@@ -25,2 +25,5 @@
+#ifdef CursorShape
+#undef CursorShape
#include "Qt/qt_utilities.hpp"

It seems that the problem is well-known; there is a "standard" solution,
namely, /usr/include/fixx11.h (so, instead of these 3 lines, one might
just insert 1: #include <fixx11.h>). But this file belongs to kdelibs, and
not every Linux user has it installed. So, my patch is more limited but
more portable (and it solves the immediate problem).

Hmm. It seems that during the last year nobody has ever compiled TeXmacs
with --enable-qt on any kind of Linux. Otherwise, this problem would be
encountered by somebody:

#define CursorShape 0

enum CursorShape { ... }

which, of course, becomes

enum 0 { ... }

Not a very encouraging thought...


(, 0 bytes) Download

Sam Liddicott

Texmacs-dev mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]