On Fri, 2024-02-09 at 20:07 -0500, Richard Kimberly Heck wrote:
> Here:
>
> http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
>
> Please prepare binaries.
>
> Riki
Done for Fedora/RHEL at
https://copr.fedorainfracloud.org/coprs/jamatos/lyx-devel/
It build and works fine.
--
José Abílio
--
lyx-d
Am Sa., 10. Feb. 2024 um 02:08 Uhr schrieb Richard Kimberly Heck <
rikih...@gmail.com>:
> Here:
>
> http://ftp.lyx.org/pub/lyx/devel/lyx-2.4/
>
> Please prepare binaries.
>
Done for Windows, uploaded as usual.
--
Eugene
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.o
On Fri, Oct 10, 2008 at 03:33:00PM +0200, Jean-Marc Lasgouttes wrote:
> Looking at the uses of Q_CYGWIN_WIN in our own code, I see two of them:
>
> 1/ in GuiApplication.cpp:
>
> #ifdef Q_WS_WIN
> #include
> #if defined(Q_CYGWIN_WIN) || defined(Q_CC_MINGW)
> #include
> #endif
> #include
> #endi
On Fri, Oct 10, 2008 at 03:23:11PM +0200, Jean-Marc Lasgouttes wrote:
> Enrico Forestieri <[EMAIL PROTECTED]> writes:
> > That didn't help, but looking at the code I saw that the contents of
> > PRL_EXPORT_DEFINES get output to pkg-config files. So, adding the line
> >
> > cygwin-g++-win32:PRL_EXPO
Enrico Forestieri <[EMAIL PROTECTED]> writes:
> That didn't help, but looking at the code I saw that the contents of
> PRL_EXPORT_DEFINES get output to pkg-config files. So, adding the line
>
> cygwin-g++-win32:PRL_EXPORT_DEFINES += Q_CYGWIN_WIN
>
> to qbase.pri did the trick!
Looking at the uses
Enrico Forestieri <[EMAIL PROTECTED]> writes:
> That didn't help, but looking at the code I saw that the contents of
> PRL_EXPORT_DEFINES get output to pkg-config files. So, adding the line
>
> cygwin-g++-win32:PRL_EXPORT_DEFINES += Q_CYGWIN_WIN
>
> to qbase.pri did the trick!
Very good. This mean
On Thu, Oct 09, 2008 at 10:26:49PM +0200, Jean-Marc Lasgouttes wrote:
> > Maybe you are right. I simply didn't find a way for having a #define
> > transferred in the .pc files by simply acting on qmake.conf and didn't
> > want to have a post-install patch. I think it's now time to try to
> > direct
Maybe you are right. I simply didn't find a way for having a #define
transferred in the .pc files by simply acting on qmake.conf and didn't
want to have a post-install patch. I think it's now time to try to
directly patch the code that generates the .pc files.
Looking at the mac code would proba
On Thu, Oct 09, 2008 at 05:53:08PM +0200, Konrad Hofbauer wrote:
> Enrico,
>
> just out of curiosity, and an honest question:
>
> Why would one want to build/run LyX in Cygwin, if there is a (well, two
> ...) native windows version ?
First of all, because I already use cygwin (I only use cygwin
On Thursday 09 October 2008 16:53:08 Konrad Hofbauer wrote:
> Why would one want to build/run LyX in Cygwin, if there is a (well, two
> ...) native windows version ?
You mean two installers and one native windows version. :-)
> /Konrad
--
José Abílio
On Thu, Oct 09, 2008 at 05:37:48PM +0200, Jean-Marc Lasgouttes wrote:
> Very impressive work, BTW.
Most of the patches were quite trivial. The difficult part was devising
an event dispatcher working for both Windows messages and Unix pipes
and sockets. When building for X11 on cygwin, the Qt sourc
On Thu, Oct 09, 2008 at 05:31:53PM +0200, Jean-Marc Lasgouttes wrote:
> OK, I see now that Q_CYGWIN_WIN is a creation from you :) I read a bit
> the page
> http://wiki.lyx.org/LyX/LyXOnCygwin
> and the impressive patch therein. BTW, is there a reason why you do not
> start from qt-all-opensource-4.
Enrico,
just out of curiosity, and an honest question:
Why would one want to build/run LyX in Cygwin, if there is a (well, two
...) native windows version ?
/Konrad
Andre Poenitz wrote:
One needs to delete *.la from /path/to/qt-4.4-install/lib/ after
compiling Qt !!!
You could still file it on http://trolltech.com/developer/task-tracker
This is what I did. But (as expected) they want more information, and
this is where my knowledge ends.
Somebody
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> OK, I see now that Q_CYGWIN_WIN is a creation from you :)
Very impressive work, BTW.
JMarc
Enrico Forestieri <[EMAIL PROTECTED]> writes:
>> It seems to me that this extra define is not really needed...
>
> It is needed because the window system choice is made in qglobal.h and
> I see no other way to have Q_WS_WIN32 defined, rather than Q_WS_X11.
> In other words, Q_WS_WIN32 gets defined
On Thu, Oct 09, 2008 at 03:18:50PM +0200, Jean-Marc Lasgouttes wrote:
> Enrico Forestieri <[EMAIL PROTECTED]> writes:
> >> Applied then. And now, is the nox.diff patch working in cygwin?
> >
> > Yes, it works.
> >
> >> I guess so, but I prefer to be sure... In particular, is Q_CYGWIN_WIN
> >> defin
Enrico Forestieri <[EMAIL PROTECTED]> writes:
>> Applied then. And now, is the nox.diff patch working in cygwin?
>
> Yes, it works.
>
>> I guess so, but I prefer to be sure... In particular, is Q_CYGWIN_WIN
>> defined as needed by pkg-config?
>
> Yes, it is, as --without-x still sets with_x=no.
Th
On Thu, Oct 09, 2008 at 09:27:48AM +0200, Jean-Marc Lasgouttes wrote:
> Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
> > On Wed, Oct 08, 2008 at 12:49:11PM +0200, Jean-Marc Lasgouttes wrote:
> >> It would be this patch (again not tested). I'd appreciate if people
> >> using windows and mac os c
Enrico Forestieri <[EMAIL PROTECTED]> writes:
> On Wed, Oct 08, 2008 at 12:49:11PM +0200, Jean-Marc Lasgouttes wrote:
>> It would be this patch (again not tested). I'd appreciate if people
>> using windows and mac os could test these two patches.
>
> Both patches work on cygwin.
Applied then. And
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> This is what this patch does (completely untested, but it does compile
> on linux). I think it is the right way of tackling this problem.
>
> Of course, I should use Qt string functions in there, but to be frank, I
> do not care :)
This is in now.
Enrico Forestieri <[EMAIL PROTECTED]> writes:
> On Wed, Oct 08, 2008 at 12:49:11PM +0200, Jean-Marc Lasgouttes wrote:
>> It would be this patch (again not tested). I'd appreciate if people
>> using windows and mac os could test these two patches.
>
> Both patches work on cygwin.
Thanks for testin
On Wed, Oct 08, 2008 at 12:49:11PM +0200, Jean-Marc Lasgouttes wrote:
> It would be this patch (again not tested). I'd appreciate if people
> using windows and mac os could test these two patches.
Both patches work on cygwin.
--
Enrico
On Wed, Oct 08, 2008 at 03:10:17PM +0200, Jean-Marc Lasgouttes wrote:
> Enrico Forestieri <[EMAIL PROTECTED]> writes:
> > Only in some special cases a distinction needs to be made, and
> > --without-x seems to be the appropriate configure switch for making
> > this distinction in sources outside of
Enrico Forestieri <[EMAIL PROTECTED]> writes:
> Configuration works independently from --without-x (i.e., using or not
> this switch doesn't matter).
OK, all is done via pkg-config, then.
> On cygwin, Qt can be built either using X11 as a graphics backend or
> without it.
This I knew.
> Only
On Wed, Oct 08, 2008 at 11:25:05AM +0200, Jean-Marc Lasgouttes wrote:
> Enrico Forestieri <[EMAIL PROTECTED]> writes:
> > On Tue, Oct 07, 2008 at 09:47:34AM +0200, Jean-Marc Lasgouttes wrote:
> >> > but I have a problem on Cygwin. With this patch, X_DISPLAY_MISSING
> >> > is not defined in config.h
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> I am sure André will correct that.
but I am not sure it will make the code shorter.
JMarc
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> Or maybe createApplication? We have basically to replicate the pruning
>> code in easyParse, right?
>
> Yes, good idea.
It would be this patch (again not tested). I'd appreciate if people
using windows and mac os could test these two patches.
JMarc
On 08/10/2008 12:20, Jean-Marc Lasgouttes wrote:
Jean-Marc Lasgouttes<[EMAIL PROTECTED]> writes:
This code is only useful for the Clipboard, which is in frontend anyway.
We have reliable way to check twhat we want in the frontend. For
example, the code above is wrong in the Mac/X11 case.
T
On 08/10/2008 12:35, Jean-Marc Lasgouttes wrote:
Abdelrazak Younes<[EMAIL PROTECTED]> writes:
No, just let GuiApplication ctor handle argc and argv directly, no
need for an additional virutal interface IMO.
Or maybe createApplication? We have basically to replicate the pruning
code
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> No, just let GuiApplication ctor handle argc and argv directly, no
> need for an additional virutal interface IMO.
Or maybe createApplication? We have basically to replicate the pruning
code in easyParse, right?
JMarc
On 08/10/2008 11:46, Jean-Marc Lasgouttes wrote:
Enrico Forestieri<[EMAIL PROTECTED]> writes:
With this patch, X_DISPLAY_MISSING is not defined in config.h and this
is used in a couple of places in the code for distinguishing between
Qt4/X11 and Qt4/Win Cygwin builds.
I took a look
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> This code is only useful for the Clipboard, which is in frontend anyway.
> We have reliable way to check twhat we want in the frontend. For
> example, the code above is wrong in the Mac/X11 case.
>
> This code should go to frontends/qt4/qt_helpers.
Enrico Forestieri <[EMAIL PROTECTED]> writes:
> With this patch, X_DISPLAY_MISSING is not defined in config.h and this
> is used in a couple of places in the code for distinguishing between
> Qt4/X11 and Qt4/Win Cygwin builds.
I took a look at these two uses of X_DISPLAY_MISSING and they look
high
Enrico Forestieri <[EMAIL PROTECTED]> writes:
> On Tue, Oct 07, 2008 at 09:47:34AM +0200, Jean-Marc Lasgouttes wrote:
>> > but I have a problem on Cygwin. With this patch, X_DISPLAY_MISSING
>> > is not defined in config.h and this is used in a couple of places
>> > in the
>> > code for distinguis
On Mon, Oct 6, 2008 at 9:59 AM, Jean-Marc Lasgouttes <[EMAIL PROTECTED]>wrote:
> Let's trying something I had in mind to avoid using --without-x. Wih
> this patch, the code to configure X is only run when pkg-config has not
> been successful.
>
> With this patch, you should be able to omit --witho
On Tue, Oct 07, 2008 at 09:47:34AM +0200, Jean-Marc Lasgouttes wrote:
> > but I have a problem on Cygwin. With this patch, X_DISPLAY_MISSING
> > is not defined in config.h and this is used in a couple of places
> > in the
> > code for distinguishing between Qt4/X11 and Qt4/Win Cygwin builds.
>
>
There's no problem on Solaris (I think it may qualify as 'exotic'
these
days)
Yes :)
but I have a problem on Cygwin. With this patch, X_DISPLAY_MISSING
is not defined in config.h and this is used in a couple of places
in the
code for distinguishing between Qt4/X11 and Qt4/Win Cygwin build
On Mon, Oct 06, 2008 at 03:59:34PM +0200, Jean-Marc Lasgouttes wrote:
> Konrad Hofbauer <[EMAIL PROTECTED]> writes:
> > At least on the Mac, it seems to be a non-issue. Deleting *.la in
> > /qt/lib, and everything seems to be just fine - if I don't forget
> > about it ;-). IMO no need to mess arou
Konrad Hofbauer <[EMAIL PROTECTED]> writes:
> At least on the Mac, it seems to be a non-issue. Deleting *.la in
> /qt/lib, and everything seems to be just fine - if I don't forget
> about it ;-). IMO no need to mess around before 1.6.0.
What was the contents of the .la files?
> We can build right
Jean-Marc Lasgouttes wrote:
Andre Poenitz <[EMAIL PROTECTED]> writes:
Maybe it is also related to the libtool version. Is libtool included in
the LyX source, or is that something I should update on my system (If
needed, I can install quite recent versions of whatever, using MacPorts).
I was
Andre Poenitz <[EMAIL PROTECTED]> writes:
>> Maybe it is also related to the libtool version. Is libtool included in
>> the LyX source, or is that something I should update on my system (If
>> needed, I can install quite recent versions of whatever, using MacPorts).
>
> I was under the impressi
On 4 okt 2008, at 13.30, Pavel Sanda wrote:
Anders Ekberg wrote:
Btw should that file be updated? In particular should the tricks
needed to
have LyX running on 10.3.9 and as a universal binary be documented?
feel free to post patch of updates to the documentation.
pavel
I think Konrad an
Anders Ekberg wrote:
> Btw should that file be updated? In particular should the tricks needed to
> have LyX running on 10.3.9 and as a universal binary be documented?
feel free to post patch of updates to the documentation.
pavel
On 4 okt 2008, at 01.08, Konrad Hofbauer wrote:
Andre Poenitz wrote:
I do not understand why, but I was told before, and I forgot:
One needs to delete *.la from /path/to/qt-4.4-install/lib/ after
compiling Qt !!!
Well, I haven't heard that before.
This was what Bennet told me to get star
On Sat, Oct 04, 2008 at 01:08:17AM +0200, Konrad Hofbauer wrote:
> Andre Poenitz wrote:
>>> I do not understand why, but I was told before, and I forgot:
>>> One needs to delete *.la from /path/to/qt-4.4-install/lib/ after
>>> compiling Qt !!!
>>
>> Well, I haven't heard that before.
>
> This wa
Andre Poenitz wrote:
I do not understand why, but I was told before, and I forgot:
One needs to delete *.la from /path/to/qt-4.4-install/lib/ after
compiling Qt !!!
Well, I haven't heard that before.
This was what Bennet told me to get started - and it looks like it is
necessary. I found a
Konrad Hofbauer wrote:
Konrad Hofbauer wrote:
It fails to build on Mac (using the same settings as for rc2).
I have not much of an idea what could be the matter ...
...
libtool: link: cannot find the library `' or unhandled argument `Carbon'
make[4]: *** [lyx] Error 1
For the above, I used t
Am Sonntag 28 September 2008 schrieb Uwe Stöhr:
> > This happens in both Windows (LyX-16rc2-4-08-AltInstaller-Small.exe),
> > and with the rc2 Linux source I compiled. (See
> > http://bugzilla.lyx.org/show_bug.cgi?id=5263 )
>
> I can confirm this with latest trunk too. It is a regression to LyX
> This happens in both Windows (LyX-16rc2-4-08-AltInstaller-Small.exe), and with
> the rc2 Linux source I compiled. (See
http://bugzilla.lyx.org/show_bug.cgi?id=5263 )
I can confirm this with latest trunk too. It is a regression to LyX 1.5, see
http://bugzilla.lyx.org/show_bug.cgi?id=5263
reg
Kornel Benko wrote:
> > 1.) I had to add in the preamble "\usepackage{amssymb}" to resolve the
> > Error "Undefined control sequence \mathbb"
I also manually had to add "\usepackage{amssymb}" to the preamble. I was
exporting from the command line, e.g.
lyx -e pdf newfile1.lyx
This h
Am Freitag 26 September 2008 schrieb Uwe Stöhr:
> > View the german version of User-Guide as PDF (ps2pdf) is not possible.
>
> Works here with MiKTeX with pdflatex and ps2pdf without problems. (I
> recommend to use pdflatex btw.).
>
> > 1.) I had to add in the preamble "\usepackage{amssymb}" to r
> View the german version of User-Guide as PDF (ps2pdf) is not possible.
Works here with MiKTeX with pdflatex and ps2pdf without problems. (I recommend
to use pdflatex btw.).
> 1.) I had to add in the preamble "\usepackage{amssymb}" to resolve the
> Error "Undefined control sequence \ma
Konrad Hofbauer wrote:
> Do I make a backtrace with:
> gdb lyx
> run
> (crash)
> backtrace
>
> Should I do this differently?
this is correct
> I rebuilt with --enable-build-type=dev (instead of rel), still this is the
> only backtrace I get:
i dont remember what dev type sets, but you should be
Konrad Hofbauer wrote:
>> Qt: QPixmap:
>> Invalid pixmap parameters
>> QPaintDevice: Unable to create context for pixmap (-2/16/0)
i remember there were some changes in trunk wrt QPixmap and QImage.
maybe it has something to do with it.
pavel
Konrad Hofbauer wrote:
Konrad Hofbauer wrote:
José Matos wrote:
The svn26576 suffix is used to warn about the trial nature of the
package.
Please test if this builds in our supported platforms and if there
are not any major bugs related with data losses. Any occurrence of
these types will r
Konrad Hofbauer wrote:
José Matos wrote:
The svn26576 suffix is used to warn about the trial nature of the
package.
Please test if this builds in our supported platforms and if there are
not any major bugs related with data losses. Any occurrence of these
types will reset the release procedu
José Matos wrote:
The svn26576 suffix is used to warn about the trial nature of the package.
Please test if this builds in our supported platforms and if there are not any
major bugs related with data losses. Any occurrence of these types will reset
the release procedure.
I built, opened (it
Konrad Hofbauer wrote:
It fails to build on Mac (using the same settings as for rc2).
I have not much of an idea what could be the matter ...
creating liblyxinsets.la
(cd .libs && rm -f liblyxinsets.la && ln -s ../liblyxinsets.la
liblyxinsets.la)
/bin/sh ../libtool --tag=CXX --mode=link g++
José Matos wrote:
Please test if this builds in our supported platforms and if there are not any
major bugs related with data losses. Any occurrence of these types will reset
the release procedure.
It fails to build on Mac (using the same settings as for rc2).
I have not much of an idea what c
60 matches
Mail list logo
