Re: Error when compiling with Qt6 on macOS

[pdv]

On 25/03/2021 15:05, pdv wrote:

On 25/03/2021 11:27, Christoph Schmitz wrote:
I have tried to compile LyX with Qt6 on macOS. The compiler stops 
quickly after a series of error messages. I attach a complete log file 
of my configure and make run.


Compiling LyX with Qt5 works with charm (thanks to the help of Marcus 
Mikulcak).


Chris




I have build successfully with the latest LyX and with Qt6 and cmake. 
There are a few issues to take into account:


1) there is an incompatibility between the moc_ files generated with qt5 
and qt6; you must remove these files manually if you switch; a "Clean" 
within XCode is not enough.


2) qtmacextras is not included in qt6 (it's not clear whether it ever 
will). You must remove 2 steps in the cmake files and the 
QMacPasteboardMimeGraphics code in GuiApplication.cpp.


3) I had to add one #include  in support/Package.cpp.

I believe the qtmacextras is needed for copy/paste (and dragging) .pdf 
content.


P. De Visschere



I found this in the qt-wiki:


Qt Mac Extras

Not included in Qt 6.0. Will find new home in the more relevant modules 
over time, and the remaining APIs considered included in later 6.x releases.



So, some time qt6macextras should be back.

--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Error when compiling with Qt6 on macOS

[Kornel Benko]

Am Thu, 25 Mar 2021 14:50:20 +0100
schrieb Christoph Schmitz :

> One library is obviously not installed by Homebrew: Qt6MacExtrasConfig. I 
> searched for
> the two files manually, but without success.
> 
> -- CMake error message:
> 
> TOP_SRC_DIR = /Users/chris/Git/LyX
> 
> Building out-of-source
> Selecting build type defaults from configure.ac
> 
> CXX11_FLAG_DETECTED = "--std=c++17 -Wno-deprecated-register"
> Compiler supports std_regex
> Using clang
> CMake Error at CMakeLists.txt:793 (find_package):
> Could not find a package configuration file provided by "Qt6MacExtras" with
> any of the following names:
> 
> Qt6MacExtrasConfig.cmake
> qt6macextras-config.cmake
> 
> Add the installation prefix of "Qt6MacExtras" to CMAKE_PREFIX_PATH or set
> "Qt6MacExtras_DIR" to a directory containing one of the above files. If
> "Qt6MacExtras" provides a separate development package or SDK, be sure it
> has been installed.

OK, I will ignore Qt6MacExtras for Qt6. (commit 9b03680a)

> Configuring incomplete, errors occurred!
> See also "/Users/chris/Git/LyX/build/CMakeFiles/CMakeOutput.log".
> See also "/Users/chris/Git/LyX/build/CMakeFiles/CMakeError.log".
> 
> Chris
> 
> 
Kornel


pgp7UxM6Gagbs.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: updatetex2lyxtests not running on Windows

[Scott Kostyshak]

On Wed, Mar 24, 2021 at 10:10:08PM +0100, Thibaut Cuvelier wrote:
> On Wed, 24 Mar 2021 at 18:14, Scott Kostyshak  wrote:
> 
> > On Tue, Mar 23, 2021 at 11:27:35PM +0100, Thibaut Cuvelier wrote:
> > > On Tue, 23 Mar 2021 at 22:08, Richard Kimberly Heck 
> > > wrote:
> > >
> > > > On 3/23/21 4:13 PM, Thibaut Cuvelier wrote:
> > > >
> > > > On Tue, 23 Mar 2021 at 15:48, Richard Kimberly Heck 
> > > > wrote:
> > > >
> > > >> On 3/22/21 7:33 PM, Thibaut Cuvelier wrote:
> > > >> > commit 0f782b0ded08953dbcde48f22d51ba87133bc029
> > > >> > Author: Thibaut Cuvelier 
> > > >> > Date:   Tue Mar 23 00:08:50 2021 +0100
> > > >> >
> > > >> > DocBook: add a parameter to change the namespace prefix for
> > MathML.
> > > >>
> > > >> Any time the syntax of semantics of the LyX file itself changes, it's
> > a
> > > >> format change, so: (1) Bump the document format; (2) Write a lyx2lyx
> > > >> routine to remove the new parameter; (3) Do what needs doing with
> > > >> tex2lyx. See lib/doc/Document.lyx, section 2.2.
> > > >>
> > > >
> > > > I had missed that, thanks for the notice. It should be corrected in the
> > > > new commit: 7a1e048f. There is nothing to add in tex2lyx, as its
> > behaviour
> > > > should not change with this new parameter.
> > > >
> > > > The one last thing to do, then, is to update the tex2lyx tests.
> > Otherwise,
> > > > Scott will very soon complain that they are all failing.
> > > >
> > > With CMake, according to the docs, it should just be running the
> > > updatetex2lyxtests target. However, it does not do a lot of things: in
> > one
> > > hour, it only changed one file. Here is the patch:
> >
> > I think that is the correct target. When I run that target, it takes 45
> > seconds and produced the diff that I committed at b2b68c3e. I went ahead
> > and committed the diff so that we can fix the tests while we work
> > through this issue.
> >
> > Does it show which commands it is running in the terminal? If not,
> > perhaps you can look in the process manager? I attach my log for
> > comparison.
> >
> 
> Here is the complete output from CMake:
> 
> C:\Users\Thibaut\AppData\Local\JetBrains\Toolbox\apps\CLion\ch-0\203.7717.62\bin\cmake\win\bin\cmake.exe
> --build D:\LyX\lyx-unstable\cmake-build-debug --target updatetex2lyxtests
> -- Git-hash = 56bd50ea6c
> -- Created D:/LyX/lyx-unstable/cmake-build-debug/lyx_date.tmp
> -- Created D:/LyX/lyx-unstable/cmake-build-debug/lyx_commit_hash.tmp
> [  0%] Built target lyx_version
> [  3%] Built target zlibstatic
> [  5%] Built target hunspell
> [  5%] Built target iconv
> [  5%] Built target mytheslibstatic
> [  5%] Built target frontends
> [ 51%] Built target frontend_qt
> [ 61%] Built target mathed
> [ 67%] Built target support
> [ 77%] Built target insets
> [ 78%] Built target graphics
> [ 94%] Built target LyX
> [100%] Built target tex2lyx
> [100%] Generating Tex2lyxFilesUpdated
> 
> Then, I only have a tex2lyx.exe process that is running and doing nothing
> (no CPU usage, RAM does not vary, no IO operations either: the user and
> system times are fixed and do not increase with time). Here is the command
> being executed:
> 
> D:/LyX/lyx-unstable/cmake-build-debug/bin/tex2lyx.exe  -roundtrip -f
> D:\LyX\lyx-unstable\src\tex2lyx\test\test.ltx

Can you reproduce the long execution time if you run the above command directly?

> The error message seems to indicate that Python is not found. However, this
> executable is started from a Python script…

Ah that is a helpful clue. I don't know why that would cause the process to 
take so much time though.

Scott


signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Error when compiling with Qt6 on macOS

[pdv]

On 25/03/2021 11:27, Christoph Schmitz wrote:

I have tried to compile LyX with Qt6 on macOS. The compiler stops quickly after 
a series of error messages. I attach a complete log file of my configure and 
make run.

Compiling LyX with Qt5 works with charm (thanks to the help of Marcus Mikulcak).

Chris




I have build successfully with the latest LyX and with Qt6 and cmake. 
There are a few issues to take into account:


1) there is an incompatibility between the moc_ files generated with qt5 
and qt6; you must remove these files manually if you switch; a "Clean" 
within XCode is not enough.


2) qtmacextras is not included in qt6 (it's not clear whether it ever 
will). You must remove 2 steps in the cmake files and the 
QMacPasteboardMimeGraphics code in GuiApplication.cpp.


3) I had to add one #include  in support/Package.cpp.

I believe the qtmacextras is needed for copy/paste (and dragging) .pdf 
content.


P. De Visschere

--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Error when compiling with Qt6 on macOS

[Christoph Schmitz]

One library is obviously not installed by Homebrew: Qt6MacExtrasConfig. I 
searched for the two files manually, but without success.

-- CMake error message:

TOP_SRC_DIR = /Users/chris/Git/LyX

Building out-of-source
Selecting build type defaults from configure.ac

CXX11_FLAG_DETECTED = "--std=c++17 -Wno-deprecated-register"
Compiler supports std_regex
Using clang
CMake Error at CMakeLists.txt:793 (find_package):
Could not find a package configuration file provided by "Qt6MacExtras" with
any of the following names:

Qt6MacExtrasConfig.cmake
qt6macextras-config.cmake

Add the installation prefix of "Qt6MacExtras" to CMAKE_PREFIX_PATH or set
"Qt6MacExtras_DIR" to a directory containing one of the above files. If
"Qt6MacExtras" provides a separate development package or SDK, be sure it
has been installed.

Configuring incomplete, errors occurred!
See also "/Users/chris/Git/LyX/build/CMakeFiles/CMakeOutput.log".
See also "/Users/chris/Git/LyX/build/CMakeFiles/CMakeError.log".

Chris


> Am 25.03.2021 um 13:40 schrieb Kornel Benko :
> 
> Am Thu, 25 Mar 2021 12:38:22 +0100
> schrieb Christoph Schmitz mailto:chr.schm...@web.de>>:
> 
>> Yes, I tried a clean build several times. And I tried it now again:
>> 
>> - I deleted the local repository.
>> - I cloned the repository.
>> - I removed Qt5 (brew remove Qt5 && brew cleanup).
>> 
>> Attached is the complete build log.
>> 
>> Unfortunately I have no idea what to do with cmake. I started the cmake GUI 
>> and clicked
>> on "Configure". There are a few surprising parameters (see attached 
>> screenshot):
>> 
>> LYX_USE_QT=QT4
>> QT_MKSPECS_DIR=**Unknown**
>> Qt5Core_DIR is present while Qt6Core_DIR is present as well.
>> 
>> Chris
>> 
> 
> Try calling cmake with '-DLYX_USE_QT=QT6'
> (or, in the GUI, select LYX_USE_QT to QT6)
> 
> Configure should fail if QT6 is not complete.
> 
>   Kornel
> -- 
> lyx-devel mailing list
> lyx-devel@lists.lyx.org 
> http://lists.lyx.org/mailman/listinfo/lyx-devel 
> 
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Error when compiling with Qt6 on macOS

[Kornel Benko]

Am Thu, 25 Mar 2021 12:38:22 +0100
schrieb Christoph Schmitz :

> Yes, I tried a clean build several times. And I tried it now again:
> 
> - I deleted the local repository.
> - I cloned the repository.
> - I removed Qt5 (brew remove Qt5 && brew cleanup).
> 
> Attached is the complete build log.
> 
> Unfortunately I have no idea what to do with cmake. I started the cmake GUI 
> and clicked
> on "Configure". There are a few surprising parameters (see attached 
> screenshot):
> 
> LYX_USE_QT=QT4
> QT_MKSPECS_DIR=**Unknown**
> Qt5Core_DIR is present while Qt6Core_DIR is present as well.
> 
> Chris
> 

Try calling cmake with '-DLYX_USE_QT=QT6'
(or, in the GUI, select LYX_USE_QT to QT6)

Configure should fail if QT6 is not complete.

Kornel


pgp_GdyEN6iJL.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] Zoom slider

[Pavel Sanda]

On Sun, Mar 07, 2021 at 01:24:29PM +0100, Juergen Spitzmueller wrote:
> commit bdb006543b43f71a06fc5b9915d0df19aae0ef68
> Author: Juergen Spitzmueller 
> Date:   Sun Mar 7 13:29:23 2021 +0100
> 
> Zoom slider

Juergen, would you mind if slider and its buttons were toggling between
visible/invisible rather than enabled/disabled?
It would look imho better when no document is loaded.

Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/master] DocBook: add a parameter to change the namespace prefix for MathML.

[Pavel Sanda]

On Wed, Mar 24, 2021 at 10:15:45PM +0100, Thibaut Cuvelier wrote:
> That's right. I've updated the manual to indicate it. Is this better?

Looks good to me, thanks. Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: #12214: Unexpected Advanced Search Dialog Behaviour

[Christoph Schmitz]

LyX 2.3.6.2 behaves similarly.

Chris


> Am 25.03.2021 um 11:57 schrieb LyX Ticket Tracker :
>
> #12214: Unexpected Advanced Search Dialog Behaviour
> +---
> Reporter:  docc|   Owner:  kornel
> Type:  defect  |  Status:  new
> Priority:  low |   Milestone:  2.4.0
> Component:  search  | Version:  2.4.0dev
> Severity:  minor   |  Resolution:
> Keywords:  |
> +---
>
> Comment (by racoon):
>
> Replying to [comment:3 racoon]:
>> Replying to [comment:1 spitz]:
>>> Maybe related to Daniel's changes.
>>
>> Which changes do you have in mind?
>
> Anything recent maybe?
>
> @docc: The ticket does not have the regression keyword yet. Did or could
> you try any earlier LyX version for whether they exhibit the same
> behaviour?
>
> --
> Ticket URL: 
> The LyX Project 
> LyX -- The Document Processor

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Error when compiling with Qt6 on macOS

[Kornel Benko]

Am Thu, 25 Mar 2021 11:27:02 +0100
schrieb Christoph Schmitz :

> I have tried to compile LyX with Qt6 on macOS. The compiler stops quickly 
> after a
> series of error messages. I attach a complete log file of my configure and 
> make run.
> 
> Compiling LyX with Qt5 works with charm (thanks to the help of Marcus 
> Mikulcak).
> 
> Chris
> 

1.) Have you tried a clean build? (Looks like you do not use moc6 but moc5)
2.) Are you able to use cmake to compile?

Kornel


pgp6KlrX6VxTy.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Error when compiling with Qt6 on macOS

[Christoph Schmitz]

I have tried to compile LyX with Qt6 on macOS. The compiler stops quickly after 
a series of error messages. I attach a complete log file of my configure and 
make run.

Compiling LyX with Qt5 works with charm (thanks to the help of Marcus Mikulcak).

Chris

❯ ./autogen.sh

Using automake (GNU automake) 1.16.3
Using autoconf (GNU Autoconf) 2.69
Building macros...
Building config header template...
Building Makefile templates...
Building configure...
Building po/POTFILES.in...

run "./configure && make"

❯ ./configure \
--with-version-suffix=-2.4 \
--prefix=/Users/chris/Git/LyX/build/LyX.app \
--with-x=no \
--disable-stdlib-debug \
--with-included-hunspell \
--with-libiconv-prefix=/usr \
--enable-qt6 \
--with-qt-dir=/usr/local/opt/qt

configuring LyX version 2.4.0dev
checking for build type... development
checking for version suffix... -2.4
checking whether Qt6 is requested... yes
checking build system type... x86_64-apple-darwin20.4.0
checking host system type... x86_64-apple-darwin20.4.0
checking target system type... x86_64-apple-darwin20.4.0
checking what packaging should be used... macosx
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... config/install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether UID '501' is supported by ustar format... yes
checking whether GID '20' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking for a Python interpreter with version >= 2.7.0 or 3.5.0... python3
checking for python3... /usr/local/bin/python3
checking for python version... 3.9
checking for python platform... darwin
checking for python script directory... ${prefix}/lib/python3.9/site-packages
checking for python extension module directory... 
${exec_prefix}/lib/python3.9/site-packages
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for ar... ar
checking the archiver (ar) interface... ar
checking for ranlib... ranlib
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking whether the compiler is clang... yes
checking for clang version... 12.0.0
checking for a good C++ mode... -std=c++17
checking whether STL is libstdc++... no
checking whether STL is libstdc++ using the C++11 ABI... no
checking for std::call_once availability... yes
checking whether C++ compiler accepts -Wno-deprecated-copy... no
checking for gcc... gcc
checking whether we are using the GNU Objective C compiler... yes
checking whether gcc accepts -g... yes
checking dependency style of gcc... gcc3
checking dependency style of gcc... (cached) gcc3
checking for extra library directory... NONE
checking for extra include directory... NONE
checking for extra lib+include directory... NONE
checking for main in -lshlwapi... no
checking for main in -lpsapi... no
checking for main in -lgdi32... no
checking for main in -lole32... no
checking whether to use included nod library... yes
checking whether to use included boost library... no
checking for boost library... no
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking whether printing callstack is possible... (cached) yes
checking whether make_unique is defined by header memory... yes
checking size of wchar_t... 4
checking for wchar_t... yes
checking for unsigned long long int... yes
checking for long long int... yes
checking for ld used by GCC... 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld
checking if the linker 
(/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld)
 is GNU ld... no
checking for shared library run path origin... 

Re: Emergency-dialog options

[Pavel Sanda]

On Sun, Mar 14, 2021 at 09:40:38PM +0100, Pavel Sanda wrote:
> we have two 2.4 milestoned bugs:
> #11253 - requesting option of opening both side by side.
> #4658 - requesting option of running comparison between original and 
> emergency copy
> 
> No one is actually sure about the best way how to fix the dialog.
> I see these options: 
> a) fix #11253 only
> b) fix #4658 only
> c) offer both ways in the dialog
> d) do #4658, but show only the resulting difference without visually opening
>original and emergency.
> Or perhaps different scenario.
> 
> I think that the only sane thing to do after opening both is to run comparison
> and check. Also once both emergency and original are loaded you can't as 
> easily
> remove the emergency or replace the orignal. So I tend to choose the option 
> d).
> What others think?

Attached is my attempt to address those bugs. I won't commit because there is
problem I currently do not know how to address.
It adds new button for displaying diff only and runs compare machinery if 
selected.

There is however some memory corruption which is causing crash in ~20% of 
trials 
and sometimes I can see some garbage in Environment combo box.

If it crashes the backtrace always leads to:

Thread 5 "lyx::Compare" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffea115700 (LWP 13732)]
0x582918a0 in ?? ()
(gdb) bt
#0  0x582918a0 in ?? ()
#1  0x56338523 in lyx::CursorSlice::nargs (this=0x7fffe0039ed0) at 
CursorSlice.h:92
#2  0x5642739e in lyx::CursorSlice::lastidx (this=0x7fffe0039ed0) at 
CursorSlice.h:70
#3  0x56437e10 in lyx::DocIterator::lastidx (this=0x7fffea114b20) at 
DocIterator.cpp:259
#4  0x564386cf in lyx::DocIterator::backwardPos (this=0x7fffea114b20) 
at DocIterator.cpp:453
#5  0x562de6fd in lyx::DocRange::DocRange (this=0x7fffea114ad0, 
buf=0x580a1040) at Compare.cpp:71
#6  0x562de9ce in lyx::DocRangePair::DocRangePair (this=0x7fffea114ad0, 
o_buf=0x580a1040,
n_buf=0x58220280) at Compare.cpp:150
#7  0x562dc52f in lyx::Compare::Impl::diff (this=0x5822b4a0, 
new_buf=0x58220280,
old_buf=0x580a1040, dest_buf=0x582dc8b0) at Compare.cpp:724
#8  0x562dacb6 in lyx::Compare::doCompare (this=0x5825aa60) at 
Compare.cpp:420
#9  0x562dab3a in lyx::Compare::run (this=0x5825aa60) at 
Compare.cpp:403


I can see two possible reasons: 
1. Compare is using threads and there is some resource conflict (like writing 
to LYXERR or whatever)
2. Loading the first buffer is not completely finished when launching compare
   which itself will load another document.

The problem with reproducibility leads me to think towards 1; I also looked at
the various pathways how we load the document and only nonessential stuff (like
connections to workarea) is missing before loading the second emergency buffer.
On the other hand the crash backtraces is always the same and seems that 
cursorslice::inset_ is wrong
so this recursive document load might indeed mi(/e)ss something.

Other option would be to rewrite the machinery so emergency check is not tried 
in special cases and we can
load both documents sequentially. That would be more complex change and I am 
running out of time now.

So unless there is some other bright idea I tend to delete 2.4 milestone for 
#11253.

Pavel
diff --git a/src/Buffer.cpp b/src/Buffer.cpp
index fdce444aef..e243453015 100644
--- a/src/Buffer.cpp
+++ b/src/Buffer.cpp
@@ -4694,7 +4694,7 @@ Buffer::ReadStatus Buffer::loadEmergency()
"%1$s exists.\n\nRecover emergency save?"), file);
 
int const load_emerg = Alert::prompt(_("Load emergency save?"), text,
-   0, 2, _(""), _(" Original"), _(""));
+   0, 3, _(""), _(" Original"), _(" show 
difference"), _(""));
 
switch (load_emerg)
{
@@ -4769,6 +4769,16 @@ Buffer::ReadStatus Buffer::loadEmergency()
return ReadOriginal;
}
 
+   case 2: {
+   string f1 = d->filename.absFileName();
+   string f2 = emergencyFile.absFileName();
+   if (loadThisLyXFile(d->filename) != ReadSuccess)
+   return ReadCancel;
+   string par = "compare run " + quoteName(f1) + " " + 
quoteName(f2);
+   LYXERR(Debug::FILES, par << "\n");
+   lyx::dispatch(FuncRequest(LFUN_DIALOG_SHOW, par));
+   return ReadCancel; //Release the buffer immediately
+   }
default:
break;
}
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel