Re: Errors compiling LyX on Windows 10 VS 2017
Am Donnerstag, 28. Februar 2019 14:22:14 CET schrieb Jean-Marc Lasgouttes
:
> Le 28/02/2019 à 13:01, Kornel Benko a écrit :
> > Am Donnerstag, 28. Februar 2019 11:56:57 CET schrieb Jean-Marc Lasgouttes
> > :
> >> Le 28/02/2019 à 11:36, Kornel Benko a écrit :
> Note that isalnum depends on the current locale, which is not a good
> idea at all. We want to use unicode stuff.
> >>>
> >>> Good to know. I was not aware of textutils.h, shame on me.
> >>
> >> I did not see an exact equivalent to isalnum, so I do not know what you
> >> are after.
> >>
> >> JMarc
> >>
> >
> > isAlnumASCII() helps a lot.
>
> What do you use it for? It it OK that it is restricted to ascii characters?
I use it to remove '\n' from the searched string (not from the pattern string)
Formerly, all '\n' were replaced by space, but that is not needed if '\n' is
followed
or prefixed by '{', or '}', or '\\' or such.
Space at some places is disturbing, because it is wrong to discard non-empty
constructs.
For instance the string '\\foreignlanguage{english}{\\emph{\n}}'
is converted to
\foreignlanguage{english}{\emph{}}
and not to
\foreignlanguage{english}{\emph{ }}
OTOH, for the string
'abc\ndef'
it is OK to be converted to 'abc def'
> JMarc
Kornel
signature.asc
Description: This is a digitally signed message part.
Re: Errors compiling LyX on Windows 10 VS 2017
On 28/02/2019 12:04, Jean-Marc Lasgouttes wrote:
Le 28/02/2019 à 08:50, Daniel a écrit :
Compiling on Windows 10 with VS 2017 used to work. But now I get an
error message when trying to compile LyX:
Error C2146
syntax error: missing ')' before identifier 'or'
LyX (applications\LyX\LyX)
C:\Users\Daniel\lyx\devel\lyx\src\BufferParams.cpp
3293
The line in question reads:
if (inputenc == "default" or features.isRequired("japanese")) {
This one is fixed in master now.
JMarc
Thanks. I can compile again!
Daniel
Re: Errors compiling LyX on Windows 10 VS 2017
Le 28/02/2019 à 13:01, Kornel Benko a écrit : Am Donnerstag, 28. Februar 2019 11:56:57 CET schrieb Jean-Marc Lasgouttes : Le 28/02/2019 à 11:36, Kornel Benko a écrit : Note that isalnum depends on the current locale, which is not a good idea at all. We want to use unicode stuff. Good to know. I was not aware of textutils.h, shame on me. I did not see an exact equivalent to isalnum, so I do not know what you are after. JMarc isAlnumASCII() helps a lot. What do you use it for? It it OK that it is restricted to ascii characters? JMarc
Re: Errors compiling LyX on Windows 10 VS 2017
Am Donnerstag, 28. Februar 2019 11:56:57 CET schrieb Jean-Marc Lasgouttes : > Le 28/02/2019 à 11:36, Kornel Benko a écrit : > >> Note that isalnum depends on the current locale, which is not a good > >> idea at all. We want to use unicode stuff. > > > > Good to know. I was not aware of textutils.h, shame on me. > > I did not see an exact equivalent to isalnum, so I do not know what you > are after. > > JMarc > isAlnumASCII() helps a lot. The problem I were the inserted '\n' in the searched strings. They were converted to ' ', but this is not needed, if '\n' is enclosed in non-alphanum chars. Kornel signature.asc Description: This is a digitally signed message part.
Re: Errors compiling LyX on Windows 10 VS 2017
Le 28/02/2019 à 08:50, Daniel a écrit :
Compiling on Windows 10 with VS 2017 used to work. But now I get an
error message when trying to compile LyX:
Error C2146
syntax error: missing ')' before identifier 'or'
LyX (applications\LyX\LyX)
C:\Users\Daniel\lyx\devel\lyx\src\BufferParams.cpp
3293
The line in question reads:
if (inputenc == "default" or features.isRequired("japanese")) {
This one is fixed in master now.
JMarc
Re: Errors compiling LyX on Windows 10 VS 2017
Le 28/02/2019 à 11:36, Kornel Benko a écrit : Note that isalnum depends on the current locale, which is not a good idea at all. We want to use unicode stuff. Good to know. I was not aware of textutils.h, shame on me. I did not see an exact equivalent to isalnum, so I do not know what you are after. JMarc
Re: Errors compiling LyX on Windows 10 VS 2017
Am Donnerstag, 28. Februar 2019 10:53:15 CET schrieb Jean-Marc Lasgouttes
:
> Le 28/02/2019 à 09:33, Kornel Benko a écrit :
> >>Error C2672
> >>'std::isalnum': no matching overloaded function found
> >>LyX (applications\LyX\LyX)
> >>C:\Users\Daniel\lyx\devel\lyx\src\lyxfind.cpp
> >>2866
> >>
> >> The line in question reads:
> >>
> >>if (std::isalnum(t[pos+1])) {
> >
> > Probably missing
> > #include
> > Could you please test?
>
> Kornel, it would be better for consistency at least for now to stick to
> the functions defined in support/textutils.h. If you do not find there
> what you need please create a correct function.
>
> Note that isalnum depends on the current locale, which is not a good
> idea at all. We want to use unicode stuff.
Good to know. I was not aware of textutils.h, shame on me.
> JMarc
Kornel
signature.asc
Description: This is a digitally signed message part.
Re: Errors compiling LyX on Windows 10 VS 2017
On 28/02/2019 09:33, Kornel Benko wrote:
Am Donnerstag, 28. Februar 2019 08:50:04 CET schrieb Daniel :
But next I get:
Error C2672
'std::isalnum': no matching overloaded function found
LyX (applications\LyX\LyX)
C:\Users\Daniel\lyx\devel\lyx\src\lyxfind.cpp
2866
The line in question reads:
if (std::isalnum(t[pos+1])) {
Probably missing
#include
Could you please test?
I tried adding
#include
at the top of lyxfind.cpp, but it does not help.
Daniel
Re: Errors compiling LyX on Windows 10 VS 2017
Le 28/02/2019 à 09:33, Kornel Benko a écrit :
Error C2672
'std::isalnum': no matching overloaded function found
LyX (applications\LyX\LyX)
C:\Users\Daniel\lyx\devel\lyx\src\lyxfind.cpp
2866
The line in question reads:
if (std::isalnum(t[pos+1])) {
Probably missing
#include
Could you please test?
Kornel, it would be better for consistency at least for now to stick to
the functions defined in support/textutils.h. If you do not find there
what you need please create a correct function.
Note that isalnum depends on the current locale, which is not a good
idea at all. We want to use unicode stuff.
JMarc
Re: Errors compiling LyX on Windows 10 VS 2017
Am Donnerstag, 28. Februar 2019 08:50:04 CET schrieb Daniel :
> Compiling on Windows 10 with VS 2017 used to work. But now I get an
> error message when trying to compile LyX:
>
> Error C2146
> syntax error: missing ')' before identifier 'or'
> LyX (applications\LyX\LyX)
> C:\Users\Daniel\lyx\devel\lyx\src\BufferParams.cpp
> 3293
>
> The line in question reads:
>
> if (inputenc == "default" or features.isRequired("japanese")) {
Git blame gives
32e4a85e4 src/BufferParams.cpp (Günter Milde 2019-02-03
22:04:17 +0100 3293)
> Manually replacing the "or" with "||" seems to fix the problem. But next
> I get:
>
> Error C2672
> 'std::isalnum': no matching overloaded function found
> LyX (applications\LyX\LyX)
> C:\Users\Daniel\lyx\devel\lyx\src\lyxfind.cpp
> 2866
>
> The line in question reads:
>
> if (std::isalnum(t[pos+1])) {
Probably missing
#include
Could you please test?
> Any idea what is going?
Yes, you are not fast enough in compiling :)
> Daniel
>
Kornel
signature.asc
Description: This is a digitally signed message part.
Errors compiling LyX on Windows 10 VS 2017
Compiling on Windows 10 with VS 2017 used to work. But now I get an
error message when trying to compile LyX:
Error C2146
syntax error: missing ')' before identifier 'or'
LyX (applications\LyX\LyX)
C:\Users\Daniel\lyx\devel\lyx\src\BufferParams.cpp
3293
The line in question reads:
if (inputenc == "default" or features.isRequired("japanese")) {
Manually replacing the "or" with "||" seems to fix the problem. But next
I get:
Error C2672
'std::isalnum': no matching overloaded function found
LyX (applications\LyX\LyX)
C:\Users\Daniel\lyx\devel\lyx\src\lyxfind.cpp
2866
The line in question reads:
if (std::isalnum(t[pos+1])) {
Any idea what is going?
Daniel
Re: LyX on Windows: New Wiki Pages
Richard Kimberly Heck wrote: > What a great idea! The file > development/Win32/packaging/installer/Packages.txt > is what Uwe used to tell MiKTeX what to install (and which I'll use to > build the batch files). I believe it is meant to include everything that > LyX could ever possibly want. That would do, I suppose. It's 319 > packages, or so says 'wc -l', but it probably doesn't end up being a > whole ton of space, and some of them may already be installed. > Alternatively, we could try to pare the list down a bit to packages > people are more likely to need. If we wanted to spare some download time/install time the best place would be to strip the docs. I measured it some time ago - the basic TL packages nedeed were ~300 mb and their documentation 1.5 GB... I'm pretty sure instaler could be instructed not to use the docs. Pavel
Re: LyX on Windows: New Wiki Pages
On 09/09/2018 18:38, Richard Kimberly Heck wrote: On 09/09/2018 12:23 PM, Daniel wrote: On 09/09/2018 18:12, Richard Kimberly Heck wrote: On 09/09/2018 07:32 AM, Daniel wrote: On 09/09/2018 01:35, Richard Kimberly Heck wrote: As mentioned previously, I am not going to build a "bundled" installer for 2.3.1. Indeed, I have removed the 'bundle' code from the installer at 8c32a1a7 and removed the bundled installer for 2.3.0 from the downloads page. I've added language instructing people to install a TeX distribution before installing LyX (as we do for OSX). I have also written this wiki page https://wiki.lyx.org/Windows/TeXLive to help people install TeXLive and this page https://wiki.lyx.org/LaTeX/TeXLivePackages to help people learn how to install packages. I'd appreciate it if people could have a look and make whatever changes or additions seem worth making. We could probably use, on one of those two pages, a quick guide to updating the TeXLive packages using the GUI. Soon, I am going to write small batch file that people can use to install various packages that LyX might want. I'll link that off the wiki, and probably include it in the Windows installer. I mean just the file itself. Not running it as part of the installer. Riki Thanks. That will hopefully help many users. But maybe there is still a problem for non-English speakers? We could work to get this translated, but I'm not sure how. Riki I am not sure either. Unfortunately, there are no translated instructions on the MiKTeX and TeX Live websites either, as far as I could see. But their installers might be or they are at least pretty much straight forward. Maybe there could be a link in the LyX installer that opens the download website (if they are stable)? That might help some people to quickly get going. It's really preferable that TeX be set up before the LyX installation. I mean, we could create two new 'bundled' installers that did nothing but launch the TeX install for people, but I'm not sure I see the point of that. I think we should really re-think 'bundling' ImageMagick, etc, in the way we do, as well. Presently, it's not at all obvious how a user could update ImageMagick itself in the wake of the kinds of security issues we've just seen. You'd have to re-install LyX, really...and wait for us to release an updated installer. I guess I really need to update the included ImageMagick, but I'm not totally sure how to do that yet. I wasn't suggesting to install TeX after the installation. Rather, when LyX is searching for TeX but doesn't find any, it offers links to a TeX installer website and tells them to install it before proceeding with the LyX install. Since there is no automatic dependency installation, it could at least make it easier to take this hurdle in order to install LyX. Daniel
Re: LyX on Windows: New Wiki Pages
On 09/09/2018 12:23 PM, Daniel wrote: > On 09/09/2018 18:12, Richard Kimberly Heck wrote: >> On 09/09/2018 07:32 AM, Daniel wrote: >>> On 09/09/2018 01:35, Richard Kimberly Heck wrote: As mentioned previously, I am not going to build a "bundled" installer for 2.3.1. Indeed, I have removed the 'bundle' code from the installer at 8c32a1a7 and removed the bundled installer for 2.3.0 from the downloads page. I've added language instructing people to install a TeX distribution before installing LyX (as we do for OSX). I have also written this wiki page https://wiki.lyx.org/Windows/TeXLive to help people install TeXLive and this page https://wiki.lyx.org/LaTeX/TeXLivePackages to help people learn how to install packages. I'd appreciate it if people could have a look and make whatever changes or additions seem worth making. We could probably use, on one of those two pages, a quick guide to updating the TeXLive packages using the GUI. Soon, I am going to write small batch file that people can use to install various packages that LyX might want. I'll link that off the wiki, and probably include it in the Windows installer. I mean just the file itself. Not running it as part of the installer. Riki >>> >>> Thanks. That will hopefully help many users. But maybe there is still >>> a problem for non-English speakers? >> >> We could work to get this translated, but I'm not sure how. >> >> Riki >> >> > > I am not sure either. Unfortunately, there are no translated > instructions on the MiKTeX and TeX Live websites either, as far as I > could see. But their installers might be or they are at least pretty > much straight forward. Maybe there could be a link in the LyX > installer that opens the download website (if they are stable)? That > might help some people to quickly get going. It's really preferable that TeX be set up before the LyX installation. I mean, we could create two new 'bundled' installers that did nothing but launch the TeX install for people, but I'm not sure I see the point of that. I think we should really re-think 'bundling' ImageMagick, etc, in the way we do, as well. Presently, it's not at all obvious how a user could update ImageMagick itself in the wake of the kinds of security issues we've just seen. You'd have to re-install LyX, really...and wait for us to release an updated installer. I guess I really need to update the included ImageMagick, but I'm not totally sure how to do that yet. Riki
Re: LyX on Windows: New Wiki Pages
On 09/09/2018 18:12, Richard Kimberly Heck wrote: On 09/09/2018 07:32 AM, Daniel wrote: On 09/09/2018 01:35, Richard Kimberly Heck wrote: As mentioned previously, I am not going to build a "bundled" installer for 2.3.1. Indeed, I have removed the 'bundle' code from the installer at 8c32a1a7 and removed the bundled installer for 2.3.0 from the downloads page. I've added language instructing people to install a TeX distribution before installing LyX (as we do for OSX). I have also written this wiki page https://wiki.lyx.org/Windows/TeXLive to help people install TeXLive and this page https://wiki.lyx.org/LaTeX/TeXLivePackages to help people learn how to install packages. I'd appreciate it if people could have a look and make whatever changes or additions seem worth making. We could probably use, on one of those two pages, a quick guide to updating the TeXLive packages using the GUI. Soon, I am going to write small batch file that people can use to install various packages that LyX might want. I'll link that off the wiki, and probably include it in the Windows installer. I mean just the file itself. Not running it as part of the installer. Riki Thanks. That will hopefully help many users. But maybe there is still a problem for non-English speakers? We could work to get this translated, but I'm not sure how. Riki I am not sure either. Unfortunately, there are no translated instructions on the MiKTeX and TeX Live websites either, as far as I could see. But their installers might be or they are at least pretty much straight forward. Maybe there could be a link in the LyX installer that opens the download website (if they are stable)? That might help some people to quickly get going. Daniel
Re: LyX on Windows: New Wiki Pages
On 09/09/2018 04:20 AM, Pavel Sanda wrote: > Richard Kimberly Heck wrote: >> Soon, I am going to write small batch file that people can use to >> install various packages that LyX might want. I'll link that off the >> wiki, and probably include it in the Windows installer. I mean just the >> file itself. Not running it as part of the installer. > Once we collect set of packages/binaries we want by default from texlive > we could write to texlive mailling list and ask them if they would > be willing to create lyx-scheme for us directly in the installer... What a great idea! The file development/Win32/packaging/installer/Packages.txt is what Uwe used to tell MiKTeX what to install (and which I'll use to build the batch files). I believe it is meant to include everything that LyX could ever possibly want. That would do, I suppose. It's 319 packages, or so says 'wc -l', but it probably doesn't end up being a whole ton of space, and some of them may already be installed. Alternatively, we could try to pare the list down a bit to packages people are more likely to need. Riki
Re: LyX on Windows: New Wiki Pages
On 09/09/2018 07:32 AM, Daniel wrote: > On 09/09/2018 01:35, Richard Kimberly Heck wrote: >> As mentioned previously, I am not going to build a "bundled" installer >> for 2.3.1. Indeed, I have removed the 'bundle' code from the installer >> at 8c32a1a7 and removed the bundled installer for 2.3.0 from the >> downloads page. I've added language instructing people to install a TeX >> distribution before installing LyX (as we do for OSX). >> >> I have also written this wiki page >> >> https://wiki.lyx.org/Windows/TeXLive >> >> to help people install TeXLive and this page >> >> https://wiki.lyx.org/LaTeX/TeXLivePackages >> >> to help people learn how to install packages. I'd appreciate it if >> people could have a look and make whatever changes or additions seem >> worth making. We could probably use, on one of those two pages, a quick >> guide to updating the TeXLive packages using the GUI. >> >> Soon, I am going to write small batch file that people can use to >> install various packages that LyX might want. I'll link that off the >> wiki, and probably include it in the Windows installer. I mean just the >> file itself. Not running it as part of the installer. >> >> Riki > > Thanks. That will hopefully help many users. But maybe there is still > a problem for non-English speakers? We could work to get this translated, but I'm not sure how. Riki
Re: LyX on Windows: New Wiki Pages
On 09/09/2018 01:35, Richard Kimberly Heck wrote: As mentioned previously, I am not going to build a "bundled" installer for 2.3.1. Indeed, I have removed the 'bundle' code from the installer at 8c32a1a7 and removed the bundled installer for 2.3.0 from the downloads page. I've added language instructing people to install a TeX distribution before installing LyX (as we do for OSX). I have also written this wiki page https://wiki.lyx.org/Windows/TeXLive to help people install TeXLive and this page https://wiki.lyx.org/LaTeX/TeXLivePackages to help people learn how to install packages. I'd appreciate it if people could have a look and make whatever changes or additions seem worth making. We could probably use, on one of those two pages, a quick guide to updating the TeXLive packages using the GUI. Soon, I am going to write small batch file that people can use to install various packages that LyX might want. I'll link that off the wiki, and probably include it in the Windows installer. I mean just the file itself. Not running it as part of the installer. Riki Thanks. That will hopefully help many users. But maybe there is still a problem for non-English speakers? Daniel
Re: LyX on Windows: New Wiki Pages
Richard Kimberly Heck wrote: > Soon, I am going to write small batch file that people can use to > install various packages that LyX might want. I'll link that off the > wiki, and probably include it in the Windows installer. I mean just the > file itself. Not running it as part of the installer. Once we collect set of packages/binaries we want by default from texlive we could write to texlive mailling list and ask them if they would be willing to create lyx-scheme for us directly in the installer... Pavel
LyX on Windows: New Wiki Pages
As mentioned previously, I am not going to build a "bundled" installer for 2.3.1. Indeed, I have removed the 'bundle' code from the installer at 8c32a1a7 and removed the bundled installer for 2.3.0 from the downloads page. I've added language instructing people to install a TeX distribution before installing LyX (as we do for OSX). I have also written this wiki page https://wiki.lyx.org/Windows/TeXLive to help people install TeXLive and this page https://wiki.lyx.org/LaTeX/TeXLivePackages to help people learn how to install packages. I'd appreciate it if people could have a look and make whatever changes or additions seem worth making. We could probably use, on one of those two pages, a quick guide to updating the TeXLive packages using the GUI. Soon, I am going to write small batch file that people can use to install various packages that LyX might want. I'll link that off the wiki, and probably include it in the Windows installer. I mean just the file itself. Not running it as part of the installer. Riki
Re: Installation of Lyx on Windows
Le 3 août 2018 19:34:56 Richard Kimberly Heck a écrit : I hadn't seen it before, but I'm planning to kill off the bundle for 2.3.1 anyway. Great idea! -- Jean-Pierre
Re: Installation of Lyx on Windows
On 08/03/2018 10:54 AM, Jean-Pierre wrote: > Hello > > A French user tried to install the official lyx-2.3.0 bundle and > complained on lyx-fr that no classes were present. > I suggested to install MiKTeX first and use the installer instead of > the bundle. That was successful. > > Is this beavior known? I hadn't seen it before, but I'm planning to kill off the bundle for 2.3.1 anyway. Riki
Installation of Lyx on Windows
Hello A French user tried to install the official lyx-2.3.0 bundle and complained on lyx-fr that no classes were present. I suggested to install MiKTeX first and use the installer instead of the bundle. That was successful. Is this beavior known? -- Jean-Pierre
Re: LyX on windows performance
Am 23.12.2017 um 20:35 schrieb Jean-Marc Lasgouttes: But, thanks to the nice INSTALL file, I did it (Qt 5.9.3 64bits) for 2.3.x+properpaint branch (I will switch to master soon). Cool. So I am not alone anymore on Windows. LyX is not yet ready for 64bit. This is something we should do for LyX 2.4. Therefore I am sure that you get troubles. Also note that I use MSVC 2015 because there are still issues with Qt and MSVC 2017. Second (bad) news: the performance is terrible, much worse that 2.2.3 as packaged by Uwe. Uwe, what is your secret? Do I have to set some optimization level? - use the 32bit Qt - write a batch script that does nothing more than to load this: C:\Program Files\Microsoft Visual Studio 11.0\VC\vcvarsall.bat (change it to the path of your 32bit MSVC) - double-click on this batch file. A console pops up where the MSVC environment is loaded - in the command line switch to LyX's Git folder /development/CMake and execute there the command build5-2015 install (before please check that the paths in the file build5-2015.bat are correct for your system) That's it. - optional: in 32bit MSVC set "Release" as build option. If you select "Debug" you get a dog slow build but one you can debug. (Despite I was never able to get the debugger running) I see that point 6 of http://www.lyx.org/trac/browser/lyxgit/INSTALL.Win32 is not correct. - At first just start the CMake Gui - set there the GNUWIN32 directory and the CMAKE_PATH_PREFIX directory - press generate in CMake and fix the missing paths it might complain about - press generate again then build - from now on use the build5-2015.bat file to build In the CMake GUI you might set how LyX is built. When I am back home in January, I will send you my settings. - Btw. I cannot send at the moment mails to lyx-devel directly. It only works by writing to the Gmane newsgroup. I get: This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: Reason: delivery retry timeout exceeded regards Uwe
Re: LyX on windows performance
Am Sonntag, 24. Dezember 2017 um 14:23:34, schrieb Jean-Marc Lasgouttes > Le 24/12/2017 à 14:00, Kornel Benko a écrit : > > But does it apply to MSVC? I could not see > > In cmake we have Debug, Release, RelWithDebInfo, MinSizeRel. > > But no profiling for MSVC. Explicitly disabled by Peter Kümmel. > > And he knows better. > > Well, profiling should be done with correct optimization (one wants to > understand the performance of the relase version) and with debug > information so that windows can tell me which function is a problem. OK > Looking a bit around, I found this: > https://msdn.microsoft.com/en-us/library/ms182372.aspx Nice. > So it might be that a release build is enough for profiling. I will > experiment with this next week. Hopefully with success :) > > In INSTALL: > > The `profiling' build type uses the -fno-omit-frame-pointer option with > > gcc > > But again: what to do for MSVC? I am as clueless as before. > > I do not think this is needed. > > JMarc Kornel signature.asc Description: This is a digitally signed message part.
Re: LyX on windows performance
Le 24/12/2017 à 14:00, Kornel Benko a écrit : But does it apply to MSVC? I could not see In cmake we have Debug, Release, RelWithDebInfo, MinSizeRel. But no profiling for MSVC. Explicitly disabled by Peter Kümmel. And he knows better. Well, profiling should be done with correct optimization (one wants to understand the performance of the relase version) and with debug information so that windows can tell me which function is a problem. Looking a bit around, I found this: https://msdn.microsoft.com/en-us/library/ms182372.aspx So it might be that a release build is enough for profiling. I will experiment with this next week. In INSTALL: The `profiling' build type uses the -fno-omit-frame-pointer option with gcc But again: what to do for MSVC? I am as clueless as before. I do not think this is needed. JMarc
Re: LyX on windows performance
Am Sonntag, 24. Dezember 2017 um 12:39:16, schrieb Jean-Marc Lasgouttes > Le 24/12/2017 à 06:18, Kornel Benko a écrit : > >> What does debug mean? Is this only debug information or also > >> instrumenting for run-time checking? > > > > Only Debug information. Also the optimization is turned to -O0 > > OK. > > >> Kornel, what is a good set of parameters for profiling? > > > I would try > > -DLYX_DEBUG=ON -DLYX_PROFILE=ON -DLYX_CONSOLE=ON > > and without -DLYX_INSTALL=ON, because this disables profiling on Windows. > > (You may comment the CMakeLists.txt:196 line > > #set(LYX_PROFILE OFF) > > ) > > but mark, my knowledge about Windows is nearly to nothing. > > Also you may need 'gprof'. > > Actually, gprof is no good for LyX, and is only for gcc. What I use > these days is a build with full optimization and debug information. You > can run that under a system level debugger and get good results. > > You can take a look at the matrix of settings for the > --enable-build-type option in INSTALL to see the autoconf choices. > > JMarc But does it apply to MSVC? I could not see In cmake we have Debug, Release, RelWithDebInfo, MinSizeRel. But no profiling for MSVC. Explicitly disabled by Peter Kümmel. And he knows better. In INSTALL: The `profiling' build type uses the -fno-omit-frame-pointer option with gcc But again: what to do for MSVC? I am as clueless as before. Kornel signature.asc Description: This is a digitally signed message part.
Re: LyX on windows performance
Le 24/12/2017 à 06:18, Kornel Benko a écrit : What does debug mean? Is this only debug information or also instrumenting for run-time checking? Only Debug information. Also the optimization is turned to -O0 OK. Kornel, what is a good set of parameters for profiling? I would try -DLYX_DEBUG=ON -DLYX_PROFILE=ON -DLYX_CONSOLE=ON and without -DLYX_INSTALL=ON, because this disables profiling on Windows. (You may comment the CMakeLists.txt:196 line #set(LYX_PROFILE OFF) ) but mark, my knowledge about Windows is nearly to nothing. Also you may need 'gprof'. Actually, gprof is no good for LyX, and is only for gcc. What I use these days is a build with full optimization and debug information. You can run that under a system level debugger and get good results. You can take a look at the matrix of settings for the --enable-build-type option in INSTALL to see the autoconf choices. JMarc
Re: LyX on windows performance
Am Samstag, 23. Dezember 2017 um 20:35:04, schrieb Jean-Marc Lasgouttes > Hi there, > > I took the dive to compile LyX on windows 10. Interesting experiment... > Intalling Visual studio takes maybe one hour (not downloading), Qt takes > just as much, selecting what platform to install is like evading a maze. > > But, thanks to the nice INSTALL file, I did it (Qt 5.9.3 64bits) for > 2.3.x+properpaint branch (I will switch to master soon). > > First (good) news: there is no black screen like on the Mac. > > Second (bad) news: the performance is terrible, much worse that 2.2.3 as > packaged by Uwe. Uwe, what is your secret? Do I have to set some > optimization level? > > I tried to run with a profiler (Very Sleepy CS), but without debug I do > not see any LyX function, and with debug what I see is some string > manipulation from the C++ library. > > What does debug mean? Is this only debug information or also > instrumenting for run-time checking? Only Debug information. Also the optimization is turned to -O0 > Kornel, what is a good set of parameters for profiling? > > JMarc I would try -DLYX_DEBUG=ON -DLYX_PROFILE=ON -DLYX_CONSOLE=ON and without -DLYX_INSTALL=ON, because this disables profiling on Windows. (You may comment the CMakeLists.txt:196 line #set(LYX_PROFILE OFF) ) but mark, my knowledge about Windows is nearly to nothing. Also you may need 'gprof'. Of course, I could never test it. Kornel signature.asc Description: This is a digitally signed message part.
LyX on windows performance
Hi there, I took the dive to compile LyX on windows 10. Interesting experiment... Intalling Visual studio takes maybe one hour (not downloading), Qt takes just as much, selecting what platform to install is like evading a maze. But, thanks to the nice INSTALL file, I did it (Qt 5.9.3 64bits) for 2.3.x+properpaint branch (I will switch to master soon). First (good) news: there is no black screen like on the Mac. Second (bad) news: the performance is terrible, much worse that 2.2.3 as packaged by Uwe. Uwe, what is your secret? Do I have to set some optimization level? I tried to run with a profiler (Very Sleepy CS), but without debug I do not see any LyX function, and with debug what I see is some string manipulation from the C++ library. What does debug mean? Is this only debug information or also instrumenting for run-time checking? Kornel, what is a good set of parameters for profiling? JMarc
Re: Compiling LyX on Windows with more recent Visual Studio versions
Am 01.11.2015 um 22:02 schrieb Georg Baum: Peter Kümmel wrote: For iconv and hunspell one can find some CMakeLists.txt at github, not ready for MSVC but usable as starting point. AFAIk zlib already ships with cmake files. Would it be an option to add tripped down iconv, hunspell and zlib sources to lyx and to build them as static libraries like boost? Then the Windows installer would only depend on ready-to-use binaries, maintained by other projects. If the license of those libs allows redistribution with the LyX sources, then this would be an option IMHO if the size increase of the package would not be too big. This would be easier to use than my suggestion, but in both cases we would need somebody who keeps the sources up to date. Georg Hunspell: License: GPL/LGPL/MPL tri-license. Latest release date: 2014-06-02 http://hunspell.sourceforge.net/ libiconv: License: GPL Latest release date: 2011-08-07 https://www.gnu.org/software/libiconv/ zlib: License: zlib (BSD/MIT like) Latest release date: 2013-04-29 http://www.zlib.net/ Linking these libs into a GPL application is therefore no problem. Sources also does not change very often, less then boost. And the size is also not that big when only the files are used needed to build the library. Then I start to add the libs. Before I push I send an overview of the changes. Peter
Re: Compiling LyX on Windows with more recent Visual Studio versions
Peter Kümmel wrote: > For iconv and hunspell one can find some CMakeLists.txt at github, not > ready for MSVC but usable as starting point. AFAIk zlib already ships > with cmake files. > > Would it be an option to add tripped down iconv, hunspell and zlib sources > to lyx and to build them as static libraries like boost? Then the Windows > installer would only depend on ready-to-use binaries, maintained by other > projects. If the license of those libs allows redistribution with the LyX sources, then this would be an option IMHO if the size increase of the package would not be too big. This would be easier to use than my suggestion, but in both cases we would need somebody who keeps the sources up to date. Georg
Re: Compiling LyX on Windows with more recent Visual Studio versions
Am 14.10.2015 um 21:52 schrieb Georg Baum: David Hyde wrote: I'm interested in looking into this at least a bit (may become deterred if some dependency nightmare occurs!). I've looked at the current MSVC dependencies that are in the archive on sourceforge. Which of these are things that should actually be downloaded and compiled on the fly? AFAIK iconv, zlib, hunspell and gettext. Unfortunately the zip file contains JMarc said that gettext is not needed any more (there is no *getlib.lib in deps). For iconv and hunspell one can find some CMakeLists.txt at github, not ready for MSVC but usable as starting point. AFAIk zlib already ships with cmake files. Would it be an option to add tripped down iconv, hunspell and zlib sources to lyx and to build them as static libraries like boost? Then the Windows installer would only depend on ready-to-use binaries, maintained by other projects. a mixture of different kinds of dependencies: The ones I mentioned are needed for compiling LyX, the others like python and ghostscript are for building the installer or running LyX. In my initial answer I did not think of the latter. I believe that we do not need to do much about these, since you can always simply install the latest version of these tools. For example, do you think that Python and ghostscript should be compiled from source, or do you think it suffices to just include up-to -date Windows binaries? Same question goes for other deps I think. Based on your feedback I can try to hack around with this a bit and see what I can get working with the latest MSVC. Very nice! Don't hesitate to ask if you've got any question, the worst thing that can happen is that nobody knows (unlikely). Georg
Re: Compiling LyX on Windows with more recent Visual Studio versions
Op 31-10-2015 om 14:44 schreef PhilipPirrip: On 10/31/2015 09:27 AM, PhilipPirrip wrote: Thanks, David. It did work with Qt 4.8.6 First thing I noticed, though, is that most icons are missing. Have to investigate. I remember seeing a similar issue here on the list recently. The errors reported in the message pane are of this kind GuiApplication.cpp (635): Cannot load icon C:/LyX/lyx-install/Resources/images/thesaurus-entry.svgz please verify resource system! Is there any special library, not mentioned in INSTALL.Win32 that needs to be copied somewhere? How can one force LyX to use png icons as a fallback? Thnx I'm already working on this issue. The problem is that Qt 4.x cannot read svgz icon files where Qt 5.x can. There is some logic to fall back to png when the svgz file could not be read but this is poorly implemented and apparently untested. Workaround would be to select classic icons in the preferences, or to change some occurences of "svgz,png" to "png" in the source code. Vincent
Re: Compiling LyX on Windows with more recent Visual Studio versions
On 10/31/2015 09:27 AM, PhilipPirrip wrote: Thanks, David. It did work with Qt 4.8.6 First thing I noticed, though, is that most icons are missing. Have to investigate. I remember seeing a similar issue here on the list recently. The errors reported in the message pane are of this kind GuiApplication.cpp (635): Cannot load icon C:/LyX/lyx-install/Resources/images/thesaurus-entry.svgz please verify resource system! Is there any special library, not mentioned in INSTALL.Win32 that needs to be copied somewhere? How can one force LyX to use png icons as a fallback? Thnx
Re: Compiling LyX on Windows with more recent Visual Studio versions
Thanks, David. It did work with Qt 4.8.6 First thing I noticed, though, is that most icons are missing. Have to investigate. I remember seeing a similar issue here on the list recently. On 10/31/2015 03:53 AM, David Hyde wrote: I experienced this error as well when setting up my LyX build environment (Windows 10 + MSVC 2010 + Qt 4.8.6). The only insight I can provide is that initially, my cmake config wasn't an exact match to what was described in INSTALL.Win32. That file was written for Qt < 5, so as part of getting everything to match INSTALL.Win32 and compile, I switched to Qt 4.8.6 rather than Qt 5.4 or 5.5. I don't exactly recall if that switch was the silver bullet for this error, but I know I haven't been able to compile LyX yet using Qt 5.x on Windows. Perhaps try compiling LyX with Qt 4.8.6 (keeping all other config the same), and see if that removes this error? In which case there is possibly some issue with compiling with Qt 5.x on Windows... Best regards, David
Re: Compiling LyX on Windows with more recent Visual Studio versions
I experienced this error as well when setting up my LyX build environment (Windows 10 + MSVC 2010 + Qt 4.8.6). The only insight I can provide is that initially, my cmake config wasn't an exact match to what was described in INSTALL.Win32. That file was written for Qt < 5, so as part of getting everything to match INSTALL.Win32 and compile, I switched to Qt 4.8.6 rather than Qt 5.4 or 5.5. I don't exactly recall if that switch was the silver bullet for this error, but I know I haven't been able to compile LyX yet using Qt 5.x on Windows. Perhaps try compiling LyX with Qt 4.8.6 (keeping all other config the same), and see if that removes this error? In which case there is possibly some issue with compiling with Qt 5.x on Windows... Best regards, David From: lyx-devel@lists.lyx.org on behalf of PhilipPirrip Sent: Friday, October 30, 2015 8:16 PM To: lyx-devel@lists.lyx.org Subject: Re: Compiling LyX on Windows with more recent Visual Studio versions Hello! I'm trying to compile LyX for Windows: WinXP VirtualBox, Visual Studio 2010, Qt 5.5, all by the instructions in INSTALL.Win32 No matter what I do in CMake config, the compilation ends with the messages I give below, and I have no idea what's happening and how to fix it. 24> -- Installing: C:/LyX/lyx-install/Resources/doc/es/DocumentoTextoPostizo.txt 24> -- Installing: C:/LyX/lyx-install/Resources/doc/attic/Changelog-UserGuide-LyX_22x.txt 24> -- Installing: C:/LyX/lyx-install/Resources/doc/attic/Changelog-EmbeddedObjects-LyX_22x.txt 24> -- Installing: C:/LyX/lyx-install/Resources/doc/attic/Changelog-Math-LyX_22.txt 24> -- Installing: C:/LyX/lyx-install/Resources/doc/./SpecialParagraphShape.tex 24> -- Installing: C:/LyX/lyx-install/Resources/doc/LFUNs.lyx 24> CMake Error at src/cmake_install.cmake:32 (file): 24> file INSTALL cannot find "C:/LyX/lyx-build-windows/bin/Debug/LyX.exe". 24> Call Stack (most recent call first): 24> cmake_install.cmake:3975 (include) 24> 24> 24> 24>C:\Program Files\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: The command "setlocal "C:\Program Files\CMake\bin\cmake.exe" -DBUILD_TYPE=Debug -P cmake_install.cmake if %errorlevel% neq 0 goto :cmEnd :cmEnd endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone :cmErrorLevel exit /b %1 :cmDone if %errorlevel% neq 0 goto :VCEnd :VCEnd" exited with code 1. 24> 24>Build FAILED. 24> 24>Time Elapsed 00:00:47.16 == Build: 21 succeeded, 3 failed, 0 up-to-date, 0 skipped
Re: Compiling LyX on Windows with more recent Visual Studio versions
Hello! I'm trying to compile LyX for Windows: WinXP VirtualBox, Visual Studio 2010, Qt 5.5, all by the instructions in INSTALL.Win32 No matter what I do in CMake config, the compilation ends with the messages I give below, and I have no idea what's happening and how to fix it. 24> -- Installing: C:/LyX/lyx-install/Resources/doc/es/DocumentoTextoPostizo.txt 24> -- Installing: C:/LyX/lyx-install/Resources/doc/attic/Changelog-UserGuide-LyX_22x.txt 24> -- Installing: C:/LyX/lyx-install/Resources/doc/attic/Changelog-EmbeddedObjects-LyX_22x.txt 24> -- Installing: C:/LyX/lyx-install/Resources/doc/attic/Changelog-Math-LyX_22.txt 24> -- Installing: C:/LyX/lyx-install/Resources/doc/./SpecialParagraphShape.tex 24> -- Installing: C:/LyX/lyx-install/Resources/doc/LFUNs.lyx 24> CMake Error at src/cmake_install.cmake:32 (file): 24> file INSTALL cannot find "C:/LyX/lyx-build-windows/bin/Debug/LyX.exe". 24> Call Stack (most recent call first): 24> cmake_install.cmake:3975 (include) 24> 24> 24> 24>C:\Program Files\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: The command "setlocal "C:\Program Files\CMake\bin\cmake.exe" -DBUILD_TYPE=Debug -P cmake_install.cmake if %errorlevel% neq 0 goto :cmEnd :cmEnd endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone :cmErrorLevel exit /b %1 :cmDone if %errorlevel% neq 0 goto :VCEnd :VCEnd" exited with code 1. 24> 24>Build FAILED. 24> 24>Time Elapsed 00:00:47.16 == Build: 21 succeeded, 3 failed, 0 up-to-date, 0 skipped
Re: Compiling LyX on Windows with more recent Visual Studio versions
David Hyde wrote: > I'm interested in looking into this at least a bit (may become deterred > if some dependency nightmare occurs!). I've looked at the current MSVC > dependencies that are in the archive on sourceforge. Which of these > are things that should actually be downloaded and compiled on the fly? AFAIK iconv, zlib, hunspell and gettext. Unfortunately the zip file contains a mixture of different kinds of dependencies: The ones I mentioned are needed for compiling LyX, the others like python and ghostscript are for building the installer or running LyX. In my initial answer I did not think of the latter. I believe that we do not need to do much about these, since you can always simply install the latest version of these tools. > For example, do you think that Python and ghostscript should be > compiled from source, or do you think it suffices to just include up-to > -date Windows binaries? Same question goes for other deps I think. > Based on your feedback I can try to hack around with this a bit and > see what I can get working with the latest MSVC. Very nice! Don't hesitate to ask if you've got any question, the worst thing that can happen is that nobody knows (unlikely). Georg
Re: Compiling LyX on Windows with more recent Visual Studio versions
Le 14/10/2015 07:27, David Hyde a écrit : Which of these are things that should actually be downloaded and compiled on the fly? For example, do you think that Python and ghostscript should be compiled from source, or do you think it suffices to just include up-to -date Windows binaries? Same question goes for other deps I think. IMO, the things that need rebuilding are the libraries, not the helper programs. This rules out python and ghostscript. JMarc
Re: Compiling LyX on Windows with more recent Visual Studio versions
Hi Georg, Thanks for your reply! > This is possible, but needs some work. > > The current MSVC build instructions use some pre-compiled third party > libraries. Of course these work only for exactly one MSVC version. > Therefore > I would propose the following procedure instead of just replicating > this > setup with a newer MSVC version: > > Create a python or cmake script that downloads, unpacks and builds > each > needed library. Add this script to the LyX git repo, and modify the > windows > cmake setup to use it instead of the current binaries from > sourceforge. I'm interested in looking into this at least a bit (may become deterred if some dependency nightmare occurs!). I've looked at the current MSVC dependencies that are in the archive on sourceforge. Which of these are things that should actually be downloaded and compiled on the fly? For example, do you think that Python and ghostscript should be compiled from source, or do you think it suffices to just include up-to -date Windows binaries? Same question goes for other deps I think. Based on your feedback I can try to hack around with this a bit and see what I can get working with the latest MSVC. Thanks again! David
Re: Compiling LyX on Windows with more recent Visual Studio versions
David Hyde wrote: > Hi there, > > > I'm interested in compiling LyX on Windows. I've read through the > INSTALL.Win32 file and was able to get LyX to compile from source using > Visual C++ Express 2010, following the instructions in that file. Great! > I'm > wondering though, is it possible (do people have experience, or know it > doesn't work, etc.) to compile LyX using a more recent VS version (2013 or > even 2015)? VS2010 isn't supported very well anymore (it was hard to even > find a download for VS2010), so being able to compile LyX on Windows using > more modern toolchains would be very useful. This is possible, but needs some work. Currently we are lacking a volunteer to do it. If you are interested (which would be much appreciated) we can help by answering any questions that might come up. The current MSVC build instructions use some pre-compiled third party libraries. Of course these work only for exactly one MSVC version. Therefore I would propose the following procedure instead of just replicating this setup with a newer MSVC version: Create a python or cmake script that downloads, unpacks and builds each needed library. Add this script to the LyX git repo, and modify the windows cmake setup to use it instead of the current binaries from sourceforge. This is more initial work, but definitely worth it, because it has a very high probability that it works with future MSVC versions as well. Georg
Compiling LyX on Windows with more recent Visual Studio versions
Hi there, I'm interested in compiling LyX on Windows. I've read through the INSTALL.Win32 file and was able to get LyX to compile from source using Visual C++ Express 2010, following the instructions in that file. I'm wondering though, is it possible (do people have experience, or know it doesn't work, etc.) to compile LyX using a more recent VS version (2013 or even 2015)? VS2010 isn't supported very well anymore (it was hard to even find a download for VS2010), so being able to compile LyX on Windows using more modern toolchains would be very useful. Thanks for any advice or experiences you may have on this! David
Re: Bundling SumatraPDF with LyX on Windows
Am 06.05.2015 um 02:04 schrieb Uwe Stöhr: Am 05.05.2015 um 22:24 schrieb Liviu Andronic: I may be the odd one around here, but why not Evince for Windows? It seems that Evince does not fully support PDF annotations/comments and also its PDF form support is limited. Liviu, could you please test LyX's PDF comment example with Evince and report back? Scott, could you please test if SumatraPDF can display our PDF comment in LyX 2.1.3 the same way as Adobe Reader? If it can do that, then SumatraPDF could indeed the solution for the Adobe Reader mess. I performed these tests on Windows. Sumatra cannot handle PDF form fields but it can handle PDF actions. It fails with annotations. Evince can handle some annotations but not all. It can handle all PDF forms but has bugs there. So all in all Evince performs better. However, both programs are not suitable for PDF forms and PDF annotations. Both are also not able to execute JavaScript. I would therefore say that we should rely in Adobe Reader. I'll have a look what I can do with Adobe Reader DC. regards Uwe
Re: Bundling SumatraPDF with LyX on Windows
Am 05.05.2015 um 22:24 schrieb Liviu Andronic: I may be the odd one around here, but why not Evince for Windows? It seems that Evince does not fully support PDF annotations/comments and also its PDF form support is limited. Liviu, could you please test LyX's PDF comment example with Evince and report back? Scott, could you please test if SumatraPDF can display our PDF comment in LyX 2.1.3 the same way as Adobe Reader? If it can do that, then SumatraPDF could indeed the solution for the Adobe Reader mess. I tested Adobe Reader DC which is very different from other Reader version. They changed the API heavily and therefore our current method to view PDF files fails. thanks and regards Uwe
Re: Bundling SumatraPDF with LyX on Windows
On Tue, May 5, 2015 at 9:31 AM, Scott Kostyshak wrote: > My motivation for this proposal is that in so many cases I have seen > "LyX doesn't open/update my PDF" and when SumatraPDF is proposed, I > see responses of "that works" and "wow I like this PDF reader". Here > are some examples: > I may be the odd one around here, but why not Evince for Windows? I've tried SumatraPDF on several occasions, and never managed to get used to that. Evince on the other hand is incredibly simply and intuitive, and among other things refreshes files from disk automatically. Liviu > http://www.mail-archive.com/lyx-users@lists.lyx.org/msg98064.html > https://www.mail-archive.com/lyx-users@lists.lyx.org/msg99586.html > http://comments.gmane.org/gmane.editors.lyx.general/84530 > http://www.lyx.org/trac/ticket/9512 > http://tex.stackexchange.com/questions/179639/pdf-crashes-after-previewing-from-lyx > > And from trac, here are some related issues: > http://www.lyx.org/trac/ticket/9512 > http://www.lyx.org/trac/ticket/9299 > http://www.lyx.org/trac/ticket/8672 > The following two are quite old and probably not relevant. > http://www.lyx.org/trac/ticket/3573 > http://www.lyx.org/trac/ticket/3045 > Uwe notes in that bug the following: > "I also reported this to the Adobe people but as often with closed > source nobody cares abotu this, only if you have a support contract." > > The topic of bundling SumatraPDF with LyX has previously been discussed here: > https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg185207.html > In particular, Uwe wrote a detailed response with his thoughts, and in > the end concluded that he was not in favor of bundling SumatraPDF. > From what I understood, he brought up three reasons against the > bundling: > > (1) The increase in size of LyX's installation file because of bundling. > (2) The license is not 100% free because of the non-free unrar component. > (3) Users prefer their own PDF reader. > > In response to (1), SumatraPDF is only 2.7 MB. Further, we already > bundle eLyXer and JabRef. Note that we would not have to install > anything. As Enrico notes, we can drop the standalone binary in the > PATH and we're done. It doesn't even write in the registry and the > preferences are stored in a text file placed alongside the exe. It > would suffice placing the executable in a directory under the LyX > directory tree that is already in the PATH prefix. > > In response to (2), as of SumatraPDF version 3.0 a free component is > used to unrar (see http://www.sumatrapdfreader.org/news.html) so > SumatraPDF is now 100% free. > > In response to (3), I think that users do not realize the advantages > of using SumatraPDF and this justifies the bundling and default > configuration. As Enrico states, "SumatraPDF is far superior to Adobe > Reader when used as a viewer for documents produced by LaTeX, because > a document gets autoreloaded on change and forward/reverse search is > supported." Forward/reverse search could be supported out of the box > (instead of the complicated configuration described here: > http://wiki.lyx.org/LyX/SyncTeX). > > A final advantage of bundling SumatraPDF, is that if there is someday > a problem with PDF viewing, we could (potentially) debug the issue > ourselves, and ship a previous/patched version of SumatraPDF or send a > patch upstream. > > In the end, I agree that the user should be free to use the PDF viewer > of her choice. However, to change to Adobe Reader, all the user has to > do is go to preferences and change it. It is much more likely that a > user realizes this (or can easily google it) than the user realizes > that to solve their problem of a PDF not opening they should install a > new PDF reader (I don't think it is obvious that they should blame > Adobe Reader and it makes sense that they think LyX is at fault). Note > also that in SumatraPDF, the user can easily open the file in Adobe > Reader by selecting File -> Open in Adobe Reader. > > Scott -- Do you think you know what math is? http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02 Or what it means to be intelligent? http://www.ideasroadshow.com/issues/john-duncan-2013-08-30 Think again: http://www.ideasroadshow.com/library
Re: Bundling SumatraPDF with LyX on Windows
Scott Kostyshak wrote: > My motivation for this proposal is that in so many cases I have seen > "LyX doesn't open/update my PDF" and when SumatraPDF is proposed, I > see responses of "that works" and "wow I like this PDF reader". Here > are some examples: +1 > A final advantage of bundling SumatraPDF, is that if there is someday > a problem with PDF viewing, we could (potentially) debug the issue > ourselves, and ship a previous/patched version of SumatraPDF or send a > patch upstream. Well, this would work also without bundling: If such a severe issue comes up then we can start to bundle at any time. Apart from that I would try to avoid debugging anything besides LyX for man power reasons ;-/ However, for those who know that they don't want SumatraPDF (or who have installed it already) it should be possible to deselect the installation of the bundled one in the installer. Georg
Bundling SumatraPDF with LyX on Windows
My motivation for this proposal is that in so many cases I have seen "LyX doesn't open/update my PDF" and when SumatraPDF is proposed, I see responses of "that works" and "wow I like this PDF reader". Here are some examples: http://www.mail-archive.com/lyx-users@lists.lyx.org/msg98064.html https://www.mail-archive.com/lyx-users@lists.lyx.org/msg99586.html http://comments.gmane.org/gmane.editors.lyx.general/84530 http://www.lyx.org/trac/ticket/9512 http://tex.stackexchange.com/questions/179639/pdf-crashes-after-previewing-from-lyx And from trac, here are some related issues: http://www.lyx.org/trac/ticket/9512 http://www.lyx.org/trac/ticket/9299 http://www.lyx.org/trac/ticket/8672 The following two are quite old and probably not relevant. http://www.lyx.org/trac/ticket/3573 http://www.lyx.org/trac/ticket/3045 Uwe notes in that bug the following: "I also reported this to the Adobe people but as often with closed source nobody cares abotu this, only if you have a support contract." The topic of bundling SumatraPDF with LyX has previously been discussed here: https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg185207.html In particular, Uwe wrote a detailed response with his thoughts, and in the end concluded that he was not in favor of bundling SumatraPDF. >From what I understood, he brought up three reasons against the bundling: (1) The increase in size of LyX's installation file because of bundling. (2) The license is not 100% free because of the non-free unrar component. (3) Users prefer their own PDF reader. In response to (1), SumatraPDF is only 2.7 MB. Further, we already bundle eLyXer and JabRef. Note that we would not have to install anything. As Enrico notes, we can drop the standalone binary in the PATH and we're done. It doesn't even write in the registry and the preferences are stored in a text file placed alongside the exe. It would suffice placing the executable in a directory under the LyX directory tree that is already in the PATH prefix. In response to (2), as of SumatraPDF version 3.0 a free component is used to unrar (see http://www.sumatrapdfreader.org/news.html) so SumatraPDF is now 100% free. In response to (3), I think that users do not realize the advantages of using SumatraPDF and this justifies the bundling and default configuration. As Enrico states, "SumatraPDF is far superior to Adobe Reader when used as a viewer for documents produced by LaTeX, because a document gets autoreloaded on change and forward/reverse search is supported." Forward/reverse search could be supported out of the box (instead of the complicated configuration described here: http://wiki.lyx.org/LyX/SyncTeX). A final advantage of bundling SumatraPDF, is that if there is someday a problem with PDF viewing, we could (potentially) debug the issue ourselves, and ship a previous/patched version of SumatraPDF or send a patch upstream. In the end, I agree that the user should be free to use the PDF viewer of her choice. However, to change to Adobe Reader, all the user has to do is go to preferences and change it. It is much more likely that a user realizes this (or can easily google it) than the user realizes that to solve their problem of a PDF not opening they should install a new PDF reader (I don't think it is obvious that they should blame Adobe Reader and it makes sense that they think LyX is at fault). Note also that in SumatraPDF, the user can easily open the file in Adobe Reader by selecting File -> Open in Adobe Reader. Scott
Re: AW: LyX on Windows with UNC home directories
Dear LyX users and developers, LyX has a problem with Windows users that have their home directory on a UNC path. http://wiki.lyx.org/LyX/Troubleshooting mentions these problems for Lyx 1.5 already. (Recent versions do start, but have no classes available.) I have been struggling with this for a long time. The workaround described in the link (saving some steps by running configure.py directly from the AppData\Lyx2.0 folder) worked for me on Windows XP. Now, on Windows 7, it does not work anymore. Today, I have done some experiments but unfortunately not found a solution yet. What I have found out is that - Under local users, LyX states "~\AppData\Roaming\Lyx2.0" as the user directory. I have not seen the tilde on Windows before, but it works. - Under network users, it states "\\server\user\ntdata\Anwendungsdaten\LyX2.0" as the user directory. - Running reconfigure from LyX as the network user gives some messages in the status line that can be traced back to the fact that cmd.exe does not accept UNC folders. Is there any way to reliably make LyX run as a user with a UNC home directory? Could it help to just give LyX a different user directory to work in? If so, how can that be done? I think this issue really needs to be fixed soon - People with home directories on serves are not uncommon and LyX is practically unusable for them. Regards Matthias Hi Matthias, Thanks for the descriptive report of the problem and your investigation of it. Please, could you add a ticket to the bug tracker at http://www.lyx.org/trac/wiki/BugTrackerHome with as much information as you can. Your email already is very descriptive of your investigation, it would help to have this recorded on the bug tracker until someone tries to tackle the bug. I'm also cc'ing the dev list to see if anyone has any immediate ideas. Regards, Julien Does anyone know how to 'simulate' such an UNC home directory. I used to do this using a network map, but maybe there are other methods ? Vincent
Re: LyX on Windows with UNC home directories
Il 22/03/2012 20:09, Julien Rioux ha scritto: On 21/03/2012 11:10 AM, Matthias Hunstig wrote: Dear LyX users and developers, LyX has a problem with Windows users that have their home directory on a UNC path. http://wiki.lyx.org/LyX/Troubleshooting mentions these problems for Lyx 1.5 already. (Recent versions do start, but have no classes available.) I have been struggling with this for a long time. The workaround described in the link (saving some steps by running configure.py directly from the AppData\Lyx2.0 folder) worked for me on Windows XP. Now, on Windows 7, it does not work anymore. Today, I have done some experiments but unfortunately not found a solution yet. What I have found out is that - Under local users, LyX states "~\AppData\Roaming\Lyx2.0" as the user directory. I have not seen the tilde on Windows before, but it works. - Under network users, it states "\\server\user\ntdata\Anwendungsdaten\LyX2.0" as the user directory. - Running reconfigure from LyX as the network user gives some messages in the status line that can be traced back to the fact that cmd.exe does not accept UNC folders. Is there any way to reliably make LyX run as a user with a UNC home directory? Could it help to just give LyX a different user directory to work in? If so, how can that be done? Please, see the "-userdir" command-line option. T.
Re: LyX on Windows with UNC home directories
On 21/03/2012 11:10 AM, Matthias Hunstig wrote: Dear LyX users and developers, LyX has a problem with Windows users that have their home directory on a UNC path. http://wiki.lyx.org/LyX/Troubleshooting mentions these problems for Lyx 1.5 already. (Recent versions do start, but have no classes available.) I have been struggling with this for a long time. The workaround described in the link (saving some steps by running configure.py directly from the AppData\Lyx2.0 folder) worked for me on Windows XP. Now, on Windows 7, it does not work anymore. Today, I have done some experiments but unfortunately not found a solution yet. What I have found out is that - Under local users, LyX states "~\AppData\Roaming\Lyx2.0" as the user directory. I have not seen the tilde on Windows before, but it works. - Under network users, it states "\\server\user\ntdata\Anwendungsdaten\LyX2.0" as the user directory. - Running reconfigure from LyX as the network user gives some messages in the status line that can be traced back to the fact that cmd.exe does not accept UNC folders. Is there any way to reliably make LyX run as a user with a UNC home directory? Could it help to just give LyX a different user directory to work in? If so, how can that be done? I think this issue really needs to be fixed soon - People with home directories on serves are not uncommon and LyX is practically unusable for them. Regards Matthias Hi Matthias, Thanks for the descriptive report of the problem and your investigation of it. Please, could you add a ticket to the bug tracker at http://www.lyx.org/trac/wiki/BugTrackerHome with as much information as you can. Your email already is very descriptive of your investigation, it would help to have this recorded on the bug tracker until someone tries to tackle the bug. I'm also cc'ing the dev list to see if anyone has any immediate ideas. Regards, Julien
Re: Lyx on Windows 7 Bug
Just as a follow-up. This is bug http://www.lyx.org/trac/ticket/7187 and will be fixed in the next release. Vincent
Re: Lyx on Windows 7 Bug
Op 21-7-2010 18:08, Larry Maturo schreef: I have a 64 bit Windows 7 installation. The install of Lyx version 167-4-25 went very smoothly. However, when it came up the text on the screen was virtually unintelligible. I brought up the DVI and printed it out and that was just fine. After playing with it for a while I believe the problem is that it is not putting spaces between words. Not only is it not putting spaces between words, but it seems to be overlapping the first character in the word after the space with the last character in the word before the space, which makes things even more unreadable. I believe that is why I had such a hard time trying to read the "Welcome to Lyx!" document. I'm a software developer, so if there is anything I can do to help you with debugging this just let me know. Can you show us a screenshot or the like ? Vincent
Lyx on Windows 7 Bug
I have a 64 bit Windows 7 installation. The install of Lyx version 167-4-25 went very smoothly. However, when it came up the text on the screen was virtually unintelligible. I brought up the DVI and printed it out and that was just fine. After playing with it for a while I believe the problem is that it is not putting spaces between words. Not only is it not putting spaces between words, but it seems to be overlapping the first character in the word after the space with the last character in the word before the space, which makes things even more unreadable. I believe that is why I had such a hard time trying to read the "Welcome to Lyx!" document. I'm a software developer, so if there is anything I can do to help you with debugging this just let me know.
Re: Should LyX (on Windows) open a new window when clicking on a second .lyx-file?
Christian Ridderström wrote: Hi, I've got a question about the behaviour of LyX which I'm using on Windows (Uwe's installer), here's the use case: * I've got a LyX file open in a LyX window. * I click on a LyX file in my browser (Opera), and a second LyX window is opened. Actually, I assume that I've started a new instance of LyX. Is this behaviour what we want? (I've gotten used to other applications opening the new document in a separate tab). A new tab or a new window - a presentation issue if it is the same session. New session advantages: * If one session crash, you won't loose changes in the other document. Of course, LyX should never crash, but there will likely always be bugs. * If one session is tied up in a 5-minute latex run (big book with many external insets - or slow computer) then other sessions will still be responsive. The busy session won't respond until latex finishes. Same session advantages: * Slightly less memory used. * Faster loading as the running instance doesn't need to start up. * perfect copy/paste of formatted data (including mouse middle click pasting) between documents in the same session. This at least used to be a problem with separate sessions. * You can make cross references between the two documents, when they are in the same session. Helge Hafting
Re: Should LyX (on Windows) open a new window when clicking on a second .lyx-file?
Christian Ridderström writes: > I've got a question about the behaviour of LyX which I'm using on > Windows (Uwe's installer), here's the use case: > > * I've got a LyX file open in a LyX window. > > * I click on a LyX file in my browser (Opera), and a second LyX window is > opened. Actually, I assume that I've started a new instance of LyX. We had this discussion already, and the answer was that we should let this be configurable or at least overrideable. I posted some references to implementation of SingleInstanceAlpplication for Qt, so all we need is somebody motivated enough to actually do it. JMarc PS: this behaviour is the system default on OS X.
Should LyX (on Windows) open a new window when clicking on a second .lyx-file?
Hi, I've got a question about the behaviour of LyX which I'm using on Windows (Uwe's installer), here's the use case: * I've got a LyX file open in a LyX window. * I click on a LyX file in my browser (Opera), and a second LyX window is opened. Actually, I assume that I've started a new instance of LyX. Is this behaviour what we want? (I've gotten used to other applications opening the new document in a separate tab). /Christian -- Christian Ridderström Mobile: +46-8 768 39 44
Re: How to debug LyX on Windows?
Bo Peng schrieb: Bo could you then please report it to the Scons people? In contary to me you'll be able to melt the problematic down to a small scons trest script for the bug report. Please CC me the report. I can not do that without access to a 64 bit windows machine. The windows XP license is simply too expensive. I eant that you put the vc-procect stuff into a small Scons script and send this to the Scons people, becuase sending our whole Scons-script is too much. Uwe
Re: How to debug LyX on Windows?
Bo could you then please report it to the Scons people? In contary to me you'll be able to melt the problematic down to a small scons trest script for the bug report. Please CC me the report. I can not do that without access to a 64 bit windows machine. The windows XP license is simply too expensive. I will ask scons people if they are aware of this problem. Bo
Re: How to debug LyX on Windows?
> I guess so. This looks like a scons windows 64 bug but I have no > access to such a machine. Bo could you then please report it to the Scons people? In contary to me you'll be able to melt the problematic down to a small scons trest script for the bug report. Please CC me the report. Thanks in advance and regards Uwe
Re: How to debug LyX on Windows?
Bo Peng wrote:
>> > : 'SConsEnvironment' object has no
>> > attribute '
>> > MSVSProject':
>> > File "D:\LyXSVN\lyx-devel\development\scons\SConstruct", line 1898:
>> > build_project('boost', src = boost_src)
>> > File "D:\LyXSVN\lyx-devel\development\scons\SConstruct", line 1882:
>> > proj = env.MSVSProject(
>> >
>> > regards Uwe
>> >
>>
>> For debugging on Windows it is simpler to use cmake.
>
> I guess so. This looks like a scons windows 64 bug but I have no
> access to such a machine.
>
> Bo
>
I've overead that it's 64bit, I never tried cmake on
a 64bit Windows.
Peter
Re: How to debug LyX on Windows?
> : 'SConsEnvironment' object has no
> attribute '
> MSVSProject':
> File "D:\LyXSVN\lyx-devel\development\scons\SConstruct", line 1898:
> build_project('boost', src = boost_src)
> File "D:\LyXSVN\lyx-devel\development\scons\SConstruct", line 1882:
> proj = env.MSVSProject(
>
> regards Uwe
>
For debugging on Windows it is simpler to use cmake.
I guess so. This looks like a scons windows 64 bug but I have no
access to such a machine.
Bo
Re: How to debug LyX on Windows?
Uwe Stöhr wrote:
> Uwe Stöhr schrieb:
>
There's a problem: The lyx.vcproject isn't created:
>
> It still doesn't work, also not with the bild script Michael has
> commited today to svn.
> I'm on WinXP x64, so perhape this could have a side effect, but I still
> don't understand why it stops at:
>
> Processing files in boost/libs/iostreams/src...
> : 'SConsEnvironment' object has no
> attribute '
> MSVSProject':
> File "D:\LyXSVN\lyx-devel\development\scons\SConstruct", line 1898:
> build_project('boost', src = boost_src)
> File "D:\LyXSVN\lyx-devel\development\scons\SConstruct", line 1882:
> proj = env.MSVSProject(
>
> regards Uwe
>
For debugging on Windows it is simpler to use cmake.
Peter
Re: How to debug LyX on Windows?
Uwe Stöhr schrieb:
There's a problem: The lyx.vcproject isn't created:
It still doesn't work, also not with the bild script Michael has commited today
to svn.
I'm on WinXP x64, so perhape this could have a side effect, but I still don't
understand why it stops at:
Processing files in boost/libs/iostreams/src...
: 'SConsEnvironment' object has no attribute '
MSVSProject':
File "D:\LyXSVN\lyx-devel\development\scons\SConstruct", line 1898:
build_project('boost', src = boost_src)
File "D:\LyXSVN\lyx-devel\development\scons\SConstruct", line 1882:
proj = env.MSVSProject(
regards Uwe
Re: How to debug LyX on Windows?
Bo Peng schrieb: There's a problem: The lyx.vcproject isn't created: It works fine here. I guess you did not run from within 'vs 2005 command prompt', right? If it still does not work, add use_vc=yes. Of course I run it from the MSVC command prompt and also tried to use use_vc=yes. Here's my build script: scons install prefix=..\..\build-msvc use_vc=yes frontend=qt4 mode=debug version_suffix=15 gettext=system nls=yes extra_inc_path=..\..\lyx-windows-deps-msvc-qt4\include extra_lib_path=..\..\lyx-windows-deps-msvc-qt4\lib extra_bin_path=..\..\lyx-windows-deps-msvc-qt4\bin qt_dir=..\..\lyx-windows-deps-msvc-qt4\qt-4 scons msvs_projects Uwe
Re: How to debug LyX on Windows?
Btw. I noticed that tex2lyx.exe isn't created when compiling in debug mode. Is this intended? scons [options] [targets] can have different targets like supports, insets, lyx, tex2lyx. all = lyx + tex2lyx + client, install = all, po and installation. By default, scons only builds lyx so tex2lyx is not built. Bo
Re: How to debug LyX on Windows?
There's a problem: The lyx.vcproject isn't created: It works fine here. I guess you did not run from within 'vs 2005 command prompt', right? If it still does not work, add use_vc=yes. Bo
Re: How to debug LyX on Windows?
Bo Peng schrieb: 2. build lyx in debug mode (default) Btw. I noticed that tex2lyx.exe isn't created when compiling in debug mode. Is this intended? Uwe
Re: How to debug LyX on Windows?
Bo Peng schrieb:
Yes. Have a look at INSTALL.scons. Basically, you need to
1. go to the scons directory.
2. build lyx in debug mode (default)
3. scons msvs_projects
4. double click the generated lyx.vcproject (name might be wrong) then
use F5 etc.
There's a problem: The lyx.vcproject isn't created:
Building all targets recursively
Processing files in boost/libs/signals/src...
Processing files in boost/libs/regex/src...
Processing files in boost/libs/filesystem/src...
Processing files in boost/libs/iostreams/src...
: 'SConsEnvironment' object has no attribute '
MSVSProject':
File "D:\LyXSVN\lyx-devel\development\scons\SConstruct", line 1898:
build_project('boost', src = boost_src)
File "D:\LyXSVN\lyx-devel\development\scons\SConstruct", line 1882:
proj = env.MSVSProject(
Then it breaks.
Uwe
Re: How to debug LyX on Windows?
> then launch lyx, connect to > process in mscv and then i can debug... That sounds complicated. You just need to type F5 in MSVC to debug... here is a few handy shortcuts: Yes. Have a look at INSTALL.scons. Basically, you need to 1. go to the scons directory. 2. build lyx in debug mode (default) 3. scons msvs_projects 4. double click the generated lyx.vcproject (name might be wrong) then use F5 etc. MSVS calls scons to rebuild later on. If you need faster rebuild, try cmake. Bo
Re: How to debug LyX on Windows?
Edwin Leuven wrote: what i do is build as debug (not release), Yes. then launch lyx, connect to process in mscv and then i can debug... That sounds complicated. You just need to type F5 in MSVC to debug... here is a few handy shortcuts: F9: set a break point (as many as you want) F10: process one line F11: enter the function at current line. Shift-F11: return out of the current function F5: continue Shift+F5: exit debug (and thus kill LyX). Hope that helps, Abdel.
Re: How to debug LyX on Windows?
what i do is build as debug (not release), then launch lyx, connect to process in mscv and then i can debug... Jean-Marc Lasgouttes wrote: "Uwe" == Uwe Stöhr <[EMAIL PROTECTED]> writes: Uwe> The symbols files are a "debug database" with the file extensions Uwe> *.pdb, the manuals tell me that MSVC creates them automatically Uwe> when compiling an application, but I can't find them anywhere. Uwe> The manual also says that without the symbols files debugging is Uwe> impossible if the application is not specially compiled to be Uwe> later debugged. So has anybody an idea how to compile LyX Uwe> correctly to be able to debug it? If you use scons I am sure there is a way to have debug info. Bo? JMarc -- http://leuven.ecodip.net
Re: How to debug LyX on Windows?
> "Uwe" == Uwe Stöhr <[EMAIL PROTECTED]> writes: Uwe> The symbols files are a "debug database" with the file extensions Uwe> *.pdb, the manuals tell me that MSVC creates them automatically Uwe> when compiling an application, but I can't find them anywhere. Uwe> The manual also says that without the symbols files debugging is Uwe> impossible if the application is not specially compiled to be Uwe> later debugged. So has anybody an idea how to compile LyX Uwe> correctly to be able to debug it? If you use scons I am sure there is a way to have debug info. Bo? JMarc
How to debug LyX on Windows?
I spend now some time to be able to debug LyX on Windows but without success. The MSVC-compiler that MS offers for free, doesn't seem to come with a debugger. I therefore installed the "Debugging Tools for Windows" that are available at MS's homepage, I also installed the symbols file collection for my system but the debugger "Windbg" of the installed tools is still not able to debug LyX because LyX's symbols files are missing. The symbols files are a "debug database" with the file extensions *.pdb, the manuals tell me that MSVC creates them automatically when compiling an application, but I can't find them anywhere. The manual also says that without the symbols files debugging is impossible if the application is not specially compiled to be later debugged. So has anybody an idea how to compile LyX correctly to be able to debug it? thanks and regards Uwe
Re: Cannot start LyX on Windows - Scons problem?
On 1/4/07, Michael Gerz <[EMAIL PROTECTED]> wrote: Andr� Poenitz schrieb: > Is there a reason for not embedding manifests in the .exe? > The manifest is already embedded in the .exe! I think there was some kind of misunderstanding... It is because the lyx.exe.manifest file that stands beside lyx.exe. Maybe I should remove the manifest file. Bo
Re: Cannot start LyX on Windows - Scons problem?
Andr� Poenitz schrieb: Is there a reason for not embedding manifests in the .exe? The manifest is already embedded in the .exe! I think there was some kind of misunderstanding... Michael
Re: Cannot start LyX on Windows - Scons problem?
Is there a reason for not embedding manifests in the .exe? No, but I need to figure out how. :-) Bo
Re: Cannot start LyX on Windows - Scons problem?
(I really don't understand why it was necessary to over-complicate things in this area - we have just one (1) frontend) We are still officially following GUII so I need to leave rooms for other frontends. The change made two building environments clearly separated: 1. basic env: used to build src/* except for support and qt4. Without all the qt flags and header files, building in this env is faster. 2. frontend_env: is supposed to be frontend dependent. It is used to build support and lyx executables. I will commit in a minute, because the patch is quite clear. Thank you very much for the fix. Bo
Re: Cannot start LyX on Windows - Scons problem?
Uwe Stöhr schrieb: I found the problem: The lyx.exe.manifest must be in the same folder with lyx.exe. The problem is that the file is not automatically be copied by SCons to the folder ~\lyx-devel\build-msvc where the compiled LyX is created by SCons. No, the problem is that mt.exe is no longer executed after linking. When introducing frontend_env, Bo forgot to fix the LINKCOM statement. (I really don't understand why it was necessary to over-complicate things in this area - we have just one (1) frontend) I will commit in a minute, because the patch is quite clear. Michael
Re: Cannot start LyX on Windows - Scons problem?
Uwe Stöhr schrieb: > This is the old manifest problem, but I can not reproduce it. Do you > have lyx.exe.manifest in the build (most likely debug) directory? > Yes, I have it in > ~\lyx-devel\development\scons\release I found the problem: The lyx.exe.manifest must be in the same folder with lyx.exe. The problem is that the file is not automatically be copied by SCons to the folder ~\lyx-devel\build-msvc where the compiled LyX is created by SCons. regards Uwe
Re: Cannot start LyX on Windows - Scons problem?
> Do you mean INSTALL.Win32 using lyx-windows-deps-msvc-qt4.zip? Last > time I tried, it worked. Yes. >>Runtime Error! >>Program: C:\bla\foo\lyx.exe >>R6034 >>An application has made an attempt to load the C runtime library >>incorrectly. >>Please contact the application's support team for more information. I have this problem too since this wednesday, so the problem must be introduced after SVN revision 16343, this was the last time I could compile LyX1.5.0SVN without this problems. > This is the old manifest problem, but I can not reproduce it. Do you > have lyx.exe.manifest in the build (most likely debug) directory? Yes, I have it in ~\lyx-devel\development\scons\release It contains this: publicKeyToken='1fc8b3b9a1e18e3b' /> I hope you have an idea how to fix this. thanks and regards Uwe
Re: Cannot start LyX on Windows - Scons problem?
when following Joost's recipe, I get the following error message: Do you mean INSTALL.Win32 using lyx-windows-deps-msvc-qt4.zip? Last time I tried, it worked. Runtime Error! Program: C:\bla\foo\lyx.exe R6034 An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information. This is the old manifest problem, but I can not reproduce it. Do you have lyx.exe.manufest in the build (most likely debug) directory? Bo
Cannot start LyX on Windows - Scons problem?
Bo, when following Joost's recipe, I get the following error message: Runtime Error! Program: C:\bla\foo\lyx.exe R6034 An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information. Some resources in the Internet suggest that this a Manifest problem. Michael
Re: Installing LyX on Windows 98 - Solved very well with Cygwin
On Mon, Jun 05, 2006 at 05:02:38PM +0200, Enrico Forestieri wrote: On Sun, Jun 04, 2006 at 08:16:15PM -0700, Stephen Harris wrote: > I wanted to put links on my Windows Desktop that would automatically > start LyX up. It should suffice creating a shortcut to C:\cygwin\usr\local\bin\lyx-x11.exe on the desktop. You will also get a nice icon. Enrico wrote: "Thinking about it, maybe you don't have C:\cygwin\bin in the Windows system PATH. If this is the case, then you can solve your problem simply copying lyx-x11.exe to C:\cygwin\bin and then creating a shortcut to C:\cygwin\bin\lyx-x11.exe." --- You are right. I tried earlier to put Cygwin in the Path, but the C:\ autoexec.bat had 0 bytes. So I cleverly appended C:\cygwin\bin to the autoexec.bat which exists in the C:\windows\command\EBD dir. and copied that file to C:\. That proved to be a big mistake. Now the C:\autoexec.bat file contains SET PATH=C:\Windows;C:\Cygwin\bin doskey which works *very well*! I have fontconfig installed, I guess I have to read the documentation. Thanks for the extensive font explanation and certainly the Path advice. I will repeat the out of environment remedy to have it all in one place. If, after installing cygnus, you get the message: Out of environment space add the line shell=C:\command.com /e:4096 /p to your c:\config.sys Also thanks for the icon which is kind of tricky in Win98, Stephen
Re: Installing LyX on Windows 98 - Solved fairly well with Cygwin
On Mon, Jun 05, 2006 at 05:02:38PM +0200, Enrico Forestieri wrote: > On Sun, Jun 04, 2006 at 08:16:15PM -0700, Stephen Harris wrote: > > > I wanted to put links on my Windows Desktop that would automatically > > start LyX up. > > It should suffice creating a shortcut to C:\cygwin\usr\local\bin\lyx-x11.exe > on the desktop. You will also get a nice icon. Thinking about it, maybe you don't have C:\cygwin\bin in the Windows system PATH. If this is the case, then you can solve your problem simply copying lyx-x11.exe to C:\cygwin\bin and then creating a shortcut to C:\cygwin\bin\lyx-x11.exe. -- Enrico
Re: Installing LyX on Windows 98 - Solved fairly well with Cygwin
On Sun, Jun 04, 2006 at 08:16:15PM -0700, Stephen Harris wrote:
> Enrico Forestieri wrote:
>
> "Notice that if you make a shortcut to lyx-x11.exe, you don't need to
> manually start the X server. If needed, lyx-x11.exe will start the X
> server using the /usr/local/bin/startxserver script which performs the
> same exact actions as the /usr/X11R6/bin/startxwin.{sh,bat} scripts,
> minus launching an additional xterm.
>
> The program lyx-x11.exe is a wrapper to the real binary lyx-x11bin.exe
> and sets up a proper environment, also assuring that the X server is
> running before launching lyx-x11bin.exe. The latter is thought to be
> used from the command line and you can simply symlink it to "lyx"
> to save typing."
> --
> Enrico
>
> -
>
> I think this applies to using LyX after opening or inside of Cygwin.
>
> I wanted to put links on my Windows Desktop that would automatically
> start LyX up.
It should suffice creating a shortcut to C:\cygwin\usr\local\bin\lyx-x11.exe
on the desktop. You will also get a nice icon.
> The problem with LyX and Xemacs too was that cyg*.dlls
> were required. It is fairly ugly to copy all those files into the
> /cygdrive/c/cygwin/usr/local/bin directory containing lyx-x11.exe
This should not be necessary as lyx-x11.exe takes care of adding
"/usr/local/bin:/usr/bin:/usr/X11R6/bin" to the PATH before launching
lyx-x11bin.exe.
> So I solved this less than elegantly by appending
> run c:\cygwin\usr\local\bin\lyx-x11.exe
> to the bottom of startxwin.bat and then renaming that to LyX11.bat
> I made a similar Xemacs.bat too.
Ok, this also works. lyx-x11.exe simply detects an already running
X server and does not try to launch another instance of it.
> So it works with a double-click from the Desktop and the Viewers
> all work without a problem. It is a little more messy to exit.
> Just the Lyx XWindow method works, the win-bin stuff generates
> only a 4cm. x 12cm. rectangle; that is Ok because the fonts seem
> crisper. I've used less than 2gigs of an 8gig harddrive and the
> 450 cpu is adequate, luckily I have 224mb of memory. I put the
> Bakoma fonts in /usr/share/texmf/fonts - texhash - and in /X11R6
> fonts since I wasn't exactly sure where they went.
You should install fontconfig and then list the directory where
you put the fonts in /etc/fonts/local.conf. As an example, here is my
local.conf file:
$ cat /etc/fonts/local.conf
/usr/local/share/fonts/bakoma
/usr/local/share/fonts/ms-ttf
I put the bakoma fonts in /usr/local/share/fonts/bakoma. The ms-ttf
directory simply contains symlinks to the Windows fonts I have in
/cygdrive/c/WINNT/Fonts.
> lyx-1.4.1-cygwin.tar.gz file at ftp://ftp.lyx.org/pub/lyx/bin/1.4.1
> seems to me an excellent solution for people who want LyX to work
> on Win98, especially since it doesn't appear that the (Qt?)problem
> is going to be fixed and enthusiasm for Win98 has waned. lyx-winbin
> works well for Win XP pro of course. I think you did a bangup job
> on this release even extending to non-intimidating instructions. I'm
> buttering you up so you don't label my solution an abomination :-)
Not at all. It is only a little convoluted ;-)
> Best regards from an average Word user,
You seem to find your way quite well on cygwin ;-)
--
Enrico
Re: Installing LyX on Windows 98 - Solved fairly well with Cygwin
Enrico Forestieri wrote:
"Notice that if you make a shortcut to lyx-x11.exe, you don't need to
manually start the X server. If needed, lyx-x11.exe will start the X
server using the /usr/local/bin/startxserver script which performs the
same exact actions as the /usr/X11R6/bin/startxwin.{sh,bat} scripts,
minus launching an additional xterm.
The program lyx-x11.exe is a wrapper to the real binary lyx-x11bin.exe
and sets up a proper environment, also assuring that the X server is
running before launching lyx-x11bin.exe. The latter is thought to be
used from the command line and you can simply symlink it to "lyx"
to save typing."
--
Enrico
-
I think this applies to using LyX after opening or inside of Cygwin.
I wanted to put links on my Windows Desktop that would automatically
start LyX up. The problem with LyX and Xemacs too was that cyg*.dlls
were required. It is fairly ugly to copy all those files into the
/cygdrive/c/cygwin/usr/local/bin directory containing lyx-x11.exe
So I solved this less than elegantly by appending
run c:\cygwin\usr\local\bin\lyx-x11.exe
to the bottom of startxwin.bat and then renaming that to LyX11.bat
I made a similar Xemacs.bat too.
So it works with a double-click from the Desktop and the Viewers
all work without a problem. It is a little more messy to exit.
Just the Lyx XWindow method works, the win-bin stuff generates
only a 4cm. x 12cm. rectangle; that is Ok because the fonts seem
crisper. I've used less than 2gigs of an 8gig harddrive and the
450 cpu is adequate, luckily I have 224mb of memory. I put the
Bakoma fonts in /usr/share/texmf/fonts - texhash - and in /X11R6
fonts since I wasn't exactly sure where they went.
lyx-1.4.1-cygwin.tar.gz file at ftp://ftp.lyx.org/pub/lyx/bin/1.4.1
seems to me an excellent solution for people who want LyX to work
on Win98, especially since it doesn't appear that the (Qt?)problem
is going to be fixed and enthusiasm for Win98 has waned. lyx-winbin
works well for Win XP pro of course. I think you did a bangup job
on this release even extending to non-intimidating instructions. I'm
buttering you up so you don't label my solution an abomination :-)
Best regards from an average Word user,
Stephen
Re: Installing LyX on Windows 98 - Solved fairly well with Cygwin
On Sat, Jun 03, 2006 at 10:09:25PM -0700, Stephen Harris wrote:
> Stephen Harris wrote:
>
> >> Nico wrote:
> >> At the end, LyX started, but with the error message "This is not a LyX
> >> document", in a tiny, non-resizable window, and the error "bddraw = 0"
> >> in the dos box, seemingly repeating itself whenever the mouse moves over
> >> the LyX window. [Trying Win98 native LyX1.3.7]
> >>
> >>
>
> >>SH: I also tried this on Win98, but with Enrico's Cygwin 1.4.1 release,
> >> lyx-1.4.1-cygwin.tar.gz file at ftp://ftp.lyx.org/pub/lyx/bin/1.4.1
> >
> >
> > Cygwin turned out to work ok. I stumbled into opening another instance
> > of startxwin before trying a viewer and then the Lyx viewers work Ok.
> > Lyx1.4.1 is not 1.3.7 but works fairly good. All that was needed was
> > follow the instructions, README and Install, included in Enrico's file,
> > and to increase the win98 environment:
> >
> > If, after installing cygnus, you get the message:
> >Out of environment space
> >add the line
> >shell=C:\command.com /e:4096 /p
> >to your c:\config.sys
> >
> > The difficult part is downloading the Cygwin files if your
> > Win98 machine uses a dialup connection rather than dsl and
> > if you have no cd player. A network card might help out. The
> > Cygwin X server works with lyx-x11.exe after startxwin shortcut.
> >
Notice that if you make a shortcut to lyx-x11.exe, you don't need to
manually start the X server. If needed, lyx-x11.exe will start the X
server using the /usr/local/bin/startxserver script which performs the
same exact actions as the /usr/X11R6/bin/startxwin.{sh,bat} scripts,
minus launching an additional xterm.
The program lyx-x11.exe is a wrapper to the real binary lyx-x11bin.exe
and sets up a proper environment, also assuring that the X server is
running before launching lyx-x11bin.exe. The latter is thought to be
used from the command line and you can simply symlink it to "lyx"
to save typing.
--
Enrico
Installing LyX on Windows 98 - Solved fairly well with Cygwin
Stephen Harris wrote: Nico wrote: At the end, LyX started, but with the error message "This is not a LyX document", in a tiny, non-resizable window, and the error "bddraw = 0" in the dos box, seemingly repeating itself whenever the mouse moves over the LyX window. [Trying Win98 native LyX1.3.7] SH: I also tried this on Win98, but with Enrico's Cygwin 1.4.1 release, lyx-1.4.1-cygwin.tar.gz file at ftp://ftp.lyx.org/pub/lyx/bin/1.4.1 Cygwin turned out to work ok. I stumbled into opening another instance of startxwin before trying a viewer and then the Lyx viewers work Ok. Lyx1.4.1 is not 1.3.7 but works fairly good. All that was needed was follow the instructions, README and Install, included in Enrico's file, and to increase the win98 environment: If, after installing cygnus, you get the message: Out of environment space add the line shell=C:\command.com /e:4096 /p to your c:\config.sys The difficult part is downloading the Cygwin files if your Win98 machine uses a dialup connection rather than dsl and if you have no cd player. A network card might help out. The Cygwin X server works with lyx-x11.exe after startxwin shortcut. Regards, Stephen
Re: LyX on Windows (MinGW) - Font problem
Jean-Marc Lasgouttes wrote: Michael> That doesn't really explain why LyX 1.3 behaves correctly Michael> where LyX 1.4 does not. What are the values of the font-related preferences? Sorry, I was wrong. The problem occurs with 1.4 and 1.3. It is definitely a Q.../Free problem. I have already informed Christian Ehrlicher about it. Michael
Re: LyX on Windows (MinGW) - Font problem
> "Michael" == Michael Gerz <[EMAIL PROTECTED]> writes: Michael> Angus Leeming wrote: >> Not in LyX. >> >> qtconfig in your qt3/bin directory. >> >> Michael> That doesn't really explain why LyX 1.3 behaves correctly Michael> where LyX 1.4 does not. What are the values of the font-related preferences? JMarc
Re: LyX on Windows (MinGW) - Font problem
Angus Leeming wrote: Not in LyX. qtconfig in your qt3/bin directory. That doesn't really explain why LyX 1.3 behaves correctly where LyX 1.4 does not. Michael
Re: LyX on Windows (MinGW) - Font problem
Michael Gerz wrote: > Ok, > > I am able to run LyX on Windows again. However, the selected font is > pretty ugly. It seems that LyX 1.4 is not able to find reasonable fonts > (LyX 1.3 does!) and so Qt decides to take the first font in > alphabetically order. This font is not only choosen for displaying a LyX > document but also for all Qt dialogs (title bar, labels, text fields, > etc.)! > > Does anybody know where I can find the code that decides which font is > to be used for Qt dialogs? Not in LyX. qtconfig in your qt3/bin directory. -- Angus
LyX on Windows (MinGW) - Font problem
Ok, I am able to run LyX on Windows again. However, the selected font is pretty ugly. It seems that LyX 1.4 is not able to find reasonable fonts (LyX 1.3 does!) and so Qt decides to take the first font in alphabetically order. This font is not only choosen for displaying a LyX document but also for all Qt dialogs (title bar, labels, text fields, etc.)! Does anybody know where I can find the code that decides which font is to be used for Qt dialogs? Thanks in advance, Michael
Re: LyX on Windows - Experience Report
Jean-Marc Lasgouttes wrote:
>>> Dear Angus,
>>>
>>> I tried to edit/view a document which was located at
>>>
>>> "c:\Dokumente und Einstellungen\michael\Eigene Dateien"
>>>
>>> but I failed for several reasons:
>>>
>>> 1. BibTeX, Version 0.99c (MiKTeX 2.4) cannot handle spaces
>>>
>>> White space in argument---line 66 of file doc.aux :
>>> \bibdata{"C:/Dokumente : und Einstellungen/michael/Eigene
>>> Dateien/doc"} I'm skipping whatever remains of this command
>
> Angus> Well then. Looks pretty conclusive to me. Not much we can do
> Angus> about that if the underlying software can't cope.
>
> Is it really needed to use quotes for a \bibliography call? This is
> not really a case of underlying \input, after all. It may be that
> latex_path is not necessary in this case.
It would be nice if someone else took up the baton on this one. I feel
sort of snowed under by LyX ATM :(
--
Angus
Re: LyX on Windows - Experience Report
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> [EMAIL PROTECTED] wrote:
>> Dear Angus,
>>
>> I tried to edit/view a document which was located at
>>
>> "c:\Dokumente und Einstellungen\michael\Eigene Dateien"
>>
>> but I failed for several reasons:
>>
>> 1. BibTeX, Version 0.99c (MiKTeX 2.4) cannot handle spaces
>>
>> White space in argument---line 66 of file doc.aux :
>> \bibdata{"C:/Dokumente : und Einstellungen/michael/Eigene
>> Dateien/doc"} I'm skipping whatever remains of this command
Angus> Well then. Looks pretty conclusive to me. Not much we can do
Angus> about that if the underlying software can't cope.
Is it really needed to use quotes for a \bibliography call? This is
not really a case of underlying \input, after all. It may be that
latex_path is not necessary in this case.
JMarc
Re: LyX on Windows - Experience Report
[EMAIL PROTECTED] wrote:
>
> Dear Angus,
>
> I tried to edit/view a document which was located at
>
>"c:\Dokumente und Einstellungen\michael\Eigene Dateien"
>
> but I failed for several reasons:
>
> 1. BibTeX, Version 0.99c (MiKTeX 2.4) cannot handle spaces
>
>White space in argument---line 66 of file doc.aux
> : \bibdata{"C:/Dokumente
> :und Einstellungen/michael/Eigene
> Dateien/doc"}
>I'm skipping whatever remains of this command
Well then. Looks pretty conclusive to me. Not much we can do about that if
the underlying software can't cope.
Does it help if you use a relative path or create a shortcut from your
document dir to the bibtex database?
> 2. YAP (Yet Another Previewer) cannot display my graphics:
>
>Cannot find file "".
Go and grab clean_dvi.py from
http://wiki.lyx.org/LaTeX/FilesWithSpecialChars
> 3. Graphics conversion for PDFLaTeX fails (MikTeX Ghostscript 8.15)
Sigh. Michael, what sort of bug report is this? Does your graphics
conversion fall through to convertDefault.sh or do you use your own
EPS->PDF converter? Etc, etc.
> Looks like there are still a few problems left to be solved...
> Regards, Michael
--
Angus
LyX on Windows - Experience Report
Dear Angus,
I tried to edit/view a document which was located at
"c:\Dokumente und Einstellungen\michael\Eigene Dateien"
but I failed for several reasons:
1. BibTeX, Version 0.99c (MiKTeX 2.4) cannot handle spaces
White space in argument---line 66 of file doc.aux
: \bibdata{"C:/Dokumente
:und Einstellungen/michael/Eigene
Dateien/doc"}
I'm skipping whatever remains of this command
2. YAP (Yet Another Previewer) cannot display my graphics:
Cannot find file "".
3. Graphics conversion for PDFLaTeX fails (MikTeX Ghostscript 8.15)
Error: /undefinedfilename in (und)
Operand stack:
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval--
--nostringval-- 2 %stopped_push --nostringval-- --nostringval--
--nostringval-- false 1 %stopped_push
Dictionary stack:
--dict:1115/1686(ro)(G)-- --dict:0/20(G)-- --dict:70/200(L)--
Current allocation mode is local
Last OS error: No such file or directory
M iKTeX GPL Ghostscript 8.15: Unrecoverable error, exit code 1
Looks like there are still a few problems left to be solved...
Regards, Michael
Re: LyX on Windows
Andre Poenitz wrote: Since we are at it: I had a look at the .vcproj and a more recent (and therefore possibly incompatible) version of LyX sources. Patch applied nicely, however I was not able get anywhere near a full compile. Compilation succeed for individual files, but there seemed to be files missing from boost (something with while.hpp and soemthing with msvc somewhere in the path). I believe I did add all necessary boost files to the CVS. Please try again with a fresh update. Are you building from a clean check out with only your patch applied? Do you have the boost path in your VS settings? Just '../../boost' is certainly not enough when you access the I do not have time to do a clean check out and apply the patch, but I think everything should be set up correctly in the project file. It is enough with a bunch of include directives to the boost files here. Regards, Asger
Re: LyX on Windows
On Tue, Jan 25, 2005 at 09:16:38AM +0100, Asger Ottar Alstrup wrote: > John Weiss wrote: > [A great opportunity to have a little flame-fest.] > > >Not FUD. Reality. [Long story about something irrelevant.] > > Took them YEARS to get it to that state. > > Sad for them. I have a working LyX. It took a week of work while Elias > was sleeping. All you are saying is FUD, and the proof is in the code. Since we are at it: I had a look at the .vcproj and a more recent (and therefore possibly incompatible) version of LyX sources. Patch applied nicely, however I was not able get anywhere near a full compile. Compilation succeed for individual files, but there seemed to be files missing from boost (something with while.hpp and soemthing with msvc somewhere in the path). Are you building from a clean check out with only your patch applied? Do you have the boost path in your VS settings? Just '../../boost' is certainly not enough when you access the Andre'
