Re: trunk compile problem

2007-11-13 Thread Pavel Sanda
> > btw in addition i use --enable-monolithic-insets and still see many > > insets/Inset*.cpp compiled individually. is it supposed to be this way? > > For some reason the feature seems to be gone? it seems that for some reason this and few other monolithic features have never been implemented. t

Re: trunk compile problem

2007-11-13 Thread Martin Vermeer
On Tue, Nov 13, 2007 at 02:51:42PM +0100, Pavel Sanda wrote: > > Pavel Sanda wrote: > >> hi, trunk has some problems now. > > > > Sorry, I'll correct that. It's weird that MSVC didn't choke... > > which is not the end of my troubles: > make[2]: Entering directory `/home/paf/mac/ledpar/lib' > make[

Re: trunk compile problem

2007-11-13 Thread Pavel Sanda
> Pavel Sanda wrote: >> hi, trunk has some problems now. > > Sorry, I'll correct that. It's weird that MSVC didn't choke... which is not the end of my troubles: make[2]: Entering directory `/home/paf/mac/ledpar/lib' make[2]: *** No rule to make target `layouts/url.module', needed by `all-am'. St

Re: trunk compile problem

2007-11-13 Thread Abdelrazak Younes
Pavel Sanda wrote: hi, trunk has some problems now. Sorry, I'll correct that. It's weird that MSVC didn't choke... Abdel.

trunk compile problem

2007-11-13 Thread Pavel Sanda
hi, trunk has some problems now. GuiView.h:126: error: a class-key must be used when declaring a friend GuiView.h:126: error: friend declaration does not name a class or function GuiView.cpp: In member function 'virtual void lyx::frontend::GuiWorkArea::close()': GuiView.cpp:938: error: 'void lyx

Re: trunk compile problem

2007-11-11 Thread Andre Poenitz
On Sun, Nov 11, 2007 at 01:27:13PM +0100, Pavel Sanda wrote: > > > are you talking about all occurences of X/lib/.h ? > > > i'm bit confused what all the numbers mean, eg # 1 > > > "/usr/include/X11/Xatom.h" 1 3 4 > > > > The first one is the line number, I don't know about the others. > > i lea

Re: trunk compile problem

2007-11-11 Thread Pavel Sanda
> > are you talking about all occurences of X/lib/.h ? > > i'm bit confused what all the numbers mean, eg # 1 > > "/usr/include/X11/Xatom.h" 1 3 4 > > The first one is the line number, I don't know about the others. i learnt meanwhile `1' indicates the start of a new file. `2' indicates return

Re: trunk compile problem

2007-11-11 Thread Andre Poenitz
On Sat, Nov 10, 2007 at 11:54:32PM +0100, Pavel Sanda wrote: > are you talking about all occurences of X/lib/.h ? > i'm bit confused what all the numbers mean, eg # 1 "/usr/include/X11/Xatom.h" > 1 3 4 The first one is the line number, I don't know about the others. I specifically meant the file

Re: trunk compile problem

2007-11-11 Thread Pavel Sanda
> > > yes, that works. > > > > Whoahey. > > > > Now you could do me a favour: Could you run that file through the > > preprocessor > > only (i.e. g++ -E instead of g++ -c) and figure out who pulls in X.h (or > > Xlib.h)? GuiApplication.cpp, 56.line pavel

Re: trunk compile problem

2007-11-10 Thread Pavel Sanda
> > yes, that works. > > Whoahey. > > Now you could do me a favour: Could you run that file through the preprocessor > only (i.e. g++ -E instead of g++ -c) and figure out who pulls in X.h (or > Xlib.h)? are you talking about all occurences of X/lib/.h ? i'm bit confused what all the numbers mean

Re: trunk compile problem

2007-11-10 Thread Andre Poenitz
On Sat, Nov 10, 2007 at 11:16:15PM +0100, Pavel Sanda wrote: > > Hm... shot into the dark: > > > > What happens if you add > > > > #undef CursorShape > > yes, that works. Whoahey. Now you could do me a favour: Could you run that file through the preprocessor only (i.e. g++ -E instead of g++ -c

Re: trunk compile problem

2007-11-10 Thread Pavel Sanda
> Hm... shot into the dark: > > What happens if you add > > #undef CursorShape yes, that works. > around line 14 in GuiDocument.h (i.e. before the #include "ui_*.h" lines) now remains ../../../src/DispatchResult.h: In constructor 'lyx::DispatchResult::DispatchResult()': ../../../src/DispatchR

Re: trunk compile problem

2007-11-10 Thread Andre Poenitz
On Sat, Nov 10, 2007 at 10:43:47PM +0100, Pavel Sanda wrote: > > If you're seeing that problem, your trunk must be out of date: > > > > [EMAIL PROTECTED] src]$ srcgrep lfun_name_ > > sorry, i didnt recognized that the error message is slightly different. > > make[6]: Entering directory `/home/ins

Re: trunk compile problem

2007-11-10 Thread Pavel Sanda
> If you're seeing that problem, your trunk must be out of date: > > [EMAIL PROTECTED] src]$ srcgrep lfun_name_ sorry, i didnt recognized that the error message is slightly different. make[6]: Entering directory `/home/installer/lyx/trunkaa/src/frontends/qt4' /bin/sh ../../../libtool --tag=CXX

Re: trunk compile problem

2007-11-10 Thread Richard Heck
Pavel Sanda wrote: ui_TextLayoutUi.h: In member function 'void Ui_TextLayoutUi::setupUi(QWidget*)': ui_TextLayoutUi.h:154: error: expected primary-expression before '(' token ui_TextLayoutUi.h:154: error: expected type-specifier ui_TextLayoutUi.h:154: error: expected `>' ui_TextLayoutUi.h:154:

Re: trunk compile problem

2007-11-09 Thread Pavel Sanda
>>> ui_TextLayoutUi.h: In member function 'void >>> Ui_TextLayoutUi::setupUi(QWidget*)': >>> ui_TextLayoutUi.h:154: error: expected primary-expression before '(' >>> token >>> ui_TextLayoutUi.h:154: error: expected type-specifier >>> ui_TextLayoutUi.h:154: error: expected `>' >>> ui_TextLayoutUi.

Re: trunk compile problem

2007-11-02 Thread Pavel Sanda
> This seems to be my fault. Which Qt do you use? Maybe the QColor > constructors with reals are too new. Cannot check myself right now as I am > in the middle of a OS update, sorry. 4.3.0 pavel

Re: trunk compile problem

2007-11-02 Thread Stefan Schimanski
GuiPainter.cpp: In member function 'QColor lyx::frontend::GuiPainter::filterColor(const QColor&)': GuiPainter.cpp:140: warning: passing 'qreal' for argument 1 to 'QColor::QColor(int, int, int, int)' GuiPainter.cpp:140: warning: passing 'qreal' for argument 2 to 'QColor::QColor(int, int, int,

Re: trunk compile problem

2007-11-02 Thread Pavel Sanda
>> Richard, we have a restriction of which you might not ave heard yet: >> static functions/objects need to have different names, even if they >> are in different .cpp files, otherwise the 'chunked build' will fail. >> > Sorry! I've fixed it. > > rh there is another one problem: make[6]: Enter

Re: trunk compile problem

2007-10-25 Thread Richard Heck
Andre Poenitz wrote: On Thu, Oct 25, 2007 at 04:17:27PM +0200, Pavel Sanda wrote: hi, dont know whether this is according to last changesets or the fact i tried to use monolithic compilation. make[6]: Entering directory `/home/installer/lyx/trunk_disable/src/frontends/qt4' /bin/sh ../../..

Re: trunk compile problem

2007-10-25 Thread Andre Poenitz
On Thu, Oct 25, 2007 at 04:17:27PM +0200, Pavel Sanda wrote: > hi, > dont know whether this is according to last changesets or the fact i tried to > use monolithic compilation. > > make[6]: Entering directory > `/home/installer/lyx/trunk_disable/src/frontends/qt4' > /bin/sh ../../../libtool --ta

Re: trunk compile problem

2007-10-25 Thread Pavel Sanda
> hi, > dont know whether this is according to last changesets or the fact i tried to > use monolithic compilation. removing --enable-monolithic-frontend-qt4 helped. p

trunk compile problem

2007-10-25 Thread Pavel Sanda
hi, dont know whether this is according to last changesets or the fact i tried to use monolithic compilation. make[6]: Entering directory `/home/installer/lyx/trunk_disable/src/frontends/qt4' /bin/sh ../../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../../../src -DQT_CLEAN_