On Wed, Dec 04, 2024 at 11:26:28PM +0100, Pavel Sanda wrote:
> On Wed, Dec 04, 2024 at 11:56:49AM +0100, Scott Kostyshak wrote:
> > On Wed, Dec 04, 2024 at 11:26:39AM +0100, Pavel Sanda wrote:
> > > On Wed, Dec 04, 2024 at 10:56:58AM +0100, Scott Kostyshak wrote:
> > > > This is great, thank you Pa
On Wed, Dec 04, 2024 at 11:56:49AM +0100, Scott Kostyshak wrote:
> On Wed, Dec 04, 2024 at 11:26:39AM +0100, Pavel Sanda wrote:
> > On Wed, Dec 04, 2024 at 10:56:58AM +0100, Scott Kostyshak wrote:
> > > This is great, thank you Pavel! For the build, do you use -Werror ?
> >
> > No. Do we want that
On Wed, Dec 04, 2024 at 11:26:39AM +0100, Pavel Sanda wrote:
> On Wed, Dec 04, 2024 at 10:56:58AM +0100, Scott Kostyshak wrote:
> > This is great, thank you Pavel! For the build, do you use -Werror ?
>
> No. Do we want that? Or else are we happy to fix any warning gcc come up with?
I would say ye
On Wed, Dec 04, 2024 at 10:56:58AM +0100, Scott Kostyshak wrote:
> This is great, thank you Pavel! For the build, do you use -Werror ?
No. Do we want that? Or else are we happy to fix any warning gcc come up with?
> I would be interested in setting up the tests, but I don't want to deal with
> t
On Tue, Dec 03, 2024 at 12:00:07PM +0100, Pavel Sanda wrote:
> On Mon, Nov 18, 2024 at 11:52:22AM +0100, Pavel Sanda wrote:
> > a) compilation on legacy system to conform our minimanl demands (qt5 & gcc)
> > and on rolling system having most recent qt6 and gcc? The stable
> > configuration
>
Le 03/12/2024 à 12:00, Pavel Sanda a écrit :
On Mon, Nov 18, 2024 at 11:52:22AM +0100, Pavel Sanda wrote:
a) compilation on legacy system to conform our minimanl demands (qt5 & gcc)
and on rolling system having most recent qt6 and gcc? The stable
configuration
is IMHO well covered b
On Mon, Nov 18, 2024 at 11:52:22AM +0100, Pavel Sanda wrote:
> a) compilation on legacy system to conform our minimanl demands (qt5 & gcc)
> and on rolling system having most recent qt6 and gcc? The stable
> configuration
> is IMHO well covered by feedback of the current dev base.
This s
Am Wed, 20 Nov 2024 19:37:51 +0100
schrieb Pavel Sanda :
> On Tue, Nov 19, 2024 at 10:27:20AM +0100, Kornel Benko wrote:
> > Am Tue, 19 Nov 2024 09:49:50 +0100
> > schrieb Pavel Sanda :
> >
> > > > I am running the tests mostly as 24 jobs parallel (I have 8 cpu's with
> > > > 2 cores
> > > > e
On Tue, Nov 19, 2024 at 10:27:20AM +0100, Kornel Benko wrote:
> Am Tue, 19 Nov 2024 09:49:50 +0100
> schrieb Pavel Sanda :
>
> > > I am running the tests mostly as 24 jobs parallel (I have 8 cpu's with 2
> > > cores each).
> > > The individual export tests may vary between < 1 second and > 1800
Le 19/11/2024 à 08:54, Kornel Benko a écrit :
I am running the tests mostly as 24 jobs parallel (I have 8 cpu's with 2 cores
each).
The individual export tests may vary between < 1 second and > 1800 seconds.
Total time for export tests here
$ ctest -j24 --timeout 1800 -L export -E '(xhtml|lyx.
On Tue, Nov 19, 2024 at 08:54:50AM +0100, Kornel Benko wrote:
> Am Mon, 18 Nov 2024 11:52:22 +0100
> schrieb Pavel Sanda :
>
> > 2) Demands:
> > a) How long takes one test? (Instead of "many hours" which can drastically
> > change
> >with different cpu's can you estimate ratio to e.g. total c
Am Tue, 19 Nov 2024 10:43:16 +0100
schrieb Jean-Marc Lasgouttes :
> Le 19/11/2024 à 10:27, Kornel Benko a écrit :
> > Am Tue, 19 Nov 2024 09:49:50 +0100
> > schrieb Pavel Sanda :
> >
> >>> I am running the tests mostly as 24 jobs parallel (I have 8 cpu's with 2
> >>> cores
> >>> each). The ind
Am Tue, 19 Nov 2024 10:42:17 +0100
schrieb Jean-Marc Lasgouttes :
> Le 19/11/2024 à 08:54, Kornel Benko a écrit :
> > I am running the tests mostly as 24 jobs parallel (I have 8 cpu's with 2
> > cores each).
> > The individual export tests may vary between < 1 second and > 1800 seconds.
> > Total
On Tue, Nov 19, 2024 at 08:54:50AM +0100, Kornel Benko wrote:
> Am Mon, 18 Nov 2024 11:52:22 +0100
> schrieb Pavel Sanda :
>
> > 2) Demands:
> > a) How long takes one test? (Instead of "many hours" which can drastically
> > change
> >with different cpu's can you estimate ratio to e.g. total c
Le 19/11/2024 à 10:27, Kornel Benko a écrit :
Am Tue, 19 Nov 2024 09:49:50 +0100
schrieb Pavel Sanda :
I am running the tests mostly as 24 jobs parallel (I have 8 cpu's with 2 cores
each).
The individual export tests may vary between < 1 second and > 1800 seconds.
Total time for export tests h
Am Tue, 19 Nov 2024 09:49:50 +0100
schrieb Pavel Sanda :
> > I am running the tests mostly as 24 jobs parallel (I have 8 cpu's with 2
> > cores each).
> > The individual export tests may vary between < 1 second and > 1800 seconds.
> > Total time for export tests here
> > $ ctest -j24 --timeout 1
Am Mon, 18 Nov 2024 11:52:22 +0100
schrieb Pavel Sanda :
> 2) Demands:
> a) How long takes one test? (Instead of "many hours" which can drastically
> change
>with different cpu's can you estimate ratio to e.g. total compilation
> time?)
> b) Can your test work in parallel manner for 4 or 8 c
ersonally argue this would be a good use
> of our
> funds, to donate in compensation for the cycles; but I'm not sure how other
> developers
> feel about this.
>
> Thank you, Pavel. I'm excited about this possibility!
>
> Kornel, I'm guessing that at som
On Sun, Nov 17, 2024 at 12:12:48PM +0100, Scott Kostyshak wrote:
> > Can you describe
> > 1) how exactly it works in backgrounds?
>
> Do you mean backporting? It checks if a certain commit is in the log, and if
> not it cherry-picks it. For example:
>
> if ! git merge-base --is-ancestor "b73ab
ranch/master seems perfectly
> reasonable to me.
> But I leave it for you to decide what's best.
Sounds good, I committed at 6cc9638d. When I have time I'll work on
cleaning it up, generalizing, and ask others for feedback on what
features they want, or how to adapt it to help
ant to use this feature as a standalone for their own build scripts.
> 2) what's the expected commandline usage?
./lyxbuild --help gives the arguments and their descriptions. For example the
--help output gives:
-o, --patch-old apply needed patches to build old commits on
On Sun, Nov 10, 2024 at 05:00:04PM +0100, Scott Kostyshak wrote:
> I have been working on a build script that helps during a bisect by
> backporting compiler fixes. Is anyone interested in this? Let me know if
> so and we can figure out how to integrate it into your build setup.
I sometimes need t
I have been working on a build script that helps during a bisect by
backporting compiler fixes. Is anyone interested in this? Let me know if
so and we can figure out how to integrate it into your build setup.
The script is "lyxbuild" located here:
https://gitlab.com/scottkosty/lyx-tester
If an
On Thu, 2024-07-04 at 15:06 +0200, Jean-Marc Lasgouttes wrote:
> Or just
> ./config.status --recheck
Thank you.
This is nice to know.
> > @Jean-Marc I see now that --no-create --no-recursion are no longer
> > the
> > default. Before when calling ~/SRC_DIR/configure those options were
> > always a
Le 04/07/2024 à 14:01, José Matos a écrit :
On Thu, 2024-07-04 at 13:47 +0200, Pavel Sanda wrote:
I would be concerned if running ./configure does not fix the Qt
version.
Does it fix it in your case?
Pavel
Yes, it works.
Since you do an out source dir build I always need to extract the
previ
On Thu, Jul 04, 2024 at 01:01:34PM +0100, José Matos wrote:
> Since you do an out source dir build I always need to extract the
> previous call from config.log file.
Workaround which I often use:
./autogen.sh
make
(configure is automatically triggered when you lauch make and it take
the paramete
On Thu, 2024-07-04 at 13:47 +0200, Pavel Sanda wrote:
> I would be concerned if running ./configure does not fix the Qt
> version.
> Does it fix it in your case?
>
> Pavel
Yes, it works.
Since you do an out source dir build I always need to extract the
previous call from config.log file.
For th
Le 04/07/2024 à 13:47, Pavel Sanda a écrit :
On Thu, Jul 04, 2024 at 12:29:13PM +0100, José Matos wrote:
There is some mechanism in action because all C++ files were recompiled
when the Qt version changed.
I would be concerned if running ./configure does not fix the Qt version.
Does it fix it
On Thu, Jul 04, 2024 at 12:29:13PM +0100, José Matos wrote:
> There is some mechanism in action because all C++ files were recompiled
> when the Qt version changed.
I would be concerned if running ./configure does not fix the Qt version.
Does it fix it in your case?
Pavel
--
lyx-devel mailing li
On Thu, 2024-07-04 at 12:16 +0200, Pavel Sanda wrote:
> But isn't it reasonable to run configure again when Qt changes?
> And it's not just QT, I think that if you don't rerun autogen
> you won't get correct lyx version when we bump the version.
>
> Pavel
There is some mechanism in action because
On Thu, Jul 04, 2024 at 10:47:00AM +0100, José Matos wrote:
> The Qt version is an old one, most likely the one used last time that
> configure ran.
But isn't it reasonable to run configure again when Qt changes?
And it's not just QT, I think that if you don't rerun autogen
you won't get correct l
Le 04/07/2024 à 11:47, José Matos a écrit :
The Qt version is an old one, most likely the one used last time that
configure ran.
Indeed. Not sure what to do about it. But the Qt version at configure
time may matter, if we did tricks according to it.
JMarc
--
lyx-devel mailing list
lyx-devel
Even before starting I should say that I am just raising this issue but
we do not need to fix it because it applies only to developers and not
to packagers. I have both hats so I know which one to pick and when.
😀️
This is just to share what I learn and I do not think that we need to
care about th
Paval,
I don't know enough to help you but just sent a donation to the tex user's
group which I gather
is a donation to lyx.
John
On Tuesday, March 5, 2024 10:57:37 AM PST Pavel Sanda wrote:
> Dear LyX community,
>
> we are transitioning our www/wiki/trac services present
trivial for us, poor C++ LyX devs -
but
might be trivial for someone whose deaily bread involves php(/pmwiki)
programming.
In case some kind soul would willing to help little bit, please contact me
directly.
Thanks for the LyX team,
Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http
On Thu, Sep 07, 2023 at 06:02:40PM -0600, José Alberto Valle Cid wrote:
> I don't know what coul be wrog, im mageia use cmake to build the lyx
> package but once installed when run the first ten items of lyx not load and
> running from console i get some like
>
> LyX: unable to find documentation
me texlive packages also provided by
mageia but still not works
Hope you can help me to solve this nasty issue, is current under
investigation on mageia's bug tracker
https://bugs.mageia.org/show_bug.cgi?id=28938
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Sat, Aug 26, 2023 at 02:11:59PM +0200, Cor Blom wrote:
>
> Hi,
>
> Below the answer on my request for help.
>
> osc build is what I have used throughout and what is used to build the
> packages for openSUSE. Adding qt6-gui-private-devel does solve the error and
> the
Hi,
Below the answer on my request for help.
osc build is what I have used throughout and what is used to build the
packages for openSUSE. Adding qt6-gui-private-devel does solve the error
and the package now builds fine.
Configure should probably fail if that library is not found.
Thanks
Am Thu, 18 May 2023 10:56:21 -0400
schrieb Richard Kimberly Heck :
> On 5/18/23 10:26, Kornel Benko wrote:
> > Specifically I would like to know if the component toString() in class
> > Inset is
> > overridden.
>
> https://en.cppreference.com/w/cpp/types/is_same
>
>
> > To solution for #1278
On 5/18/23 10:26, Kornel Benko wrote:
Specifically I would like to know if the component toString() in class Inset is
overridden.
https://en.cppreference.com/w/cpp/types/is_same
To solution for #12783 would be ATM the attached, but I'd like to have it done
for other insets too.
Why does
Specifically I would like to know if the component toString() in class Inset is
overridden.
To solution for #12783 would be ATM the attached, but I'd like to have it done
for
other insets too.
Kornel
diff --git a/src/Paragraph.cpp b/src/Paragraph.cpp
index b8819fdf1b..6ce3ce08ff 100644
On Tue, Dec 06, 2022 at 10:19:18PM +0100, Stephan Witt wrote:
> Am 06.12.2022 um 22:12 schrieb Pavel Sanda :
> >
> > On Tue, Dec 06, 2022 at 12:25:53PM -0500, Scott Kostyshak wrote:
> >> For a macOS user, can we tell whether they are on Ventura or not?
> >
> > I???ll try QSysInfo::pro
Am 06.12.2022 um 22:12 schrieb Pavel Sanda :
>
> On Tue, Dec 06, 2022 at 12:25:53PM -0500, Scott Kostyshak wrote:
>> For a macOS user, can we tell whether they are on Ventura or not?
>
> I???ll try QSysInfo::productVersion() ???
This will show up like that:
On Tue, Dec 06, 2022 at 12:25:53PM -0500, Scott Kostyshak wrote:
> > >>> For a macOS user, can we tell whether they are on Ventura or not?
> > >>
> > >> I???ll try QSysInfo::productVersion() ???
> > >
> > > This will show up like that:
> > >
> > >
> > >
> > > With Ventura it should be: 13.0
>
;> On Sun, Dec 04, 2022 at 10:13:11PM +0100, Jean-Marc Lasgouttes wrote:
> >>>> Le 04/12/2022 à 21:41, Scott Kostyshak a écrit :
> >>>>> When collecting information, it might be nice to have OS information.
> >>>>> That way, the user only has to go t
22 à 21:41, Scott Kostyshak a écrit :
>>>>> When collecting information, it might be nice to have OS information.
>>>>> That way, the user only has to go to Help > About and click on "Copy
>>>>> Version Info" and all important information
nformation, it might be nice to have OS information.
>>>> That way, the user only has to go to Help > About and click on "Copy
>>>> Version Info" and all important information is copied; rather than
>>>> having to ask them to separately state it.
>>&
Am 06.12.2022 um 16:34 schrieb Scott Kostyshak :
>
> On Sun, Dec 04, 2022 at 10:13:11PM +0100, Jean-Marc Lasgouttes wrote:
>> Le 04/12/2022 à 21:41, Scott Kostyshak a écrit :
>>> When collecting information, it might be nice to have OS information.
>>> That way, t
On Sun, Dec 04, 2022 at 10:13:11PM +0100, Jean-Marc Lasgouttes wrote:
> Le 04/12/2022 à 21:41, Scott Kostyshak a écrit :
> > When collecting information, it might be nice to have OS information.
> > That way, the user only has to go to Help > About and click on "Copy
&g
Le 04/12/2022 à 21:41, Scott Kostyshak a écrit :
When collecting information, it might be nice to have OS information.
That way, the user only has to go to Help > About and click on "Copy
Version Info" and all important information is copied; rather than
having to ask them to separa
When collecting information, it might be nice to have OS information.
That way, the user only has to go to Help > About and click on "Copy
Version Info" and all important information is copied; rather than
having to ask them to separately state it.
Is it OK if I add OS information?
On Sat, Nov 26, 2022 at 04:32:31PM +0100, Jürgen Spitzmüller wrote:
> Am Samstag, dem 26.11.2022 um 09:30 -0500 schrieb Scott Kostyshak:
> > Thanks, Jürgen. One of the weird things that happens if I change
> > TocLevel to 3 is that when I execute outline-in (e.g., clicking on
> > the button in the
Am Samstag, dem 26.11.2022 um 09:30 -0500 schrieb Scott Kostyshak:
> Thanks, Jürgen. One of the weird things that happens if I change
> TocLevel to 3 is that when I execute outline-in (e.g., clicking on
> the button in the outliner) on a Section, it changes "Frame" to
> "AgainFrame" for some reason
On Sat, Nov 26, 2022 at 11:30:35AM +0100, Jürgen Spitzmüller wrote:
> Am Samstag, dem 26.11.2022 um 08:58 +0100 schrieb Jürgen Spitzmüller:
> > In theory, this should also work via the layout by increasing the
> > layout's SecNumDepth value (to 4), but it doesn't work for me.
>
> No, the layout's
Am Samstag, dem 26.11.2022 um 08:58 +0100 schrieb Jürgen Spitzmüller:
> In theory, this should also work via the layout by increasing the
> layout's SecNumDepth value (to 4), but it doesn't work for me.
No, the layout's SecNumDepth only determines the default depth set in
the class (this decides w
Am Freitag, dem 25.11.2022 um 21:55 -0500 schrieb Scott Kostyshak:
> This change causes some annoyances and in theory I don't think it
> should be needed. However, without the change the LabelString doesn't
> show up at all. Is it a LyX bug that the LabelString in the patch
> doesn't show up when T
The attached patch (thanks to racoon!) is one of my favorite patches
that I apply locally. I find it helpful to know the frame numbers of the
frames, especially when I'm going back and forth with the PDF output.
The main problem with the patch is that for some reason to get it to
work we needed to
On Sat, 18 Jun 2022, 11:04 Kornel Benko, wrote:
> Am Sat, 18 Jun 2022 18:22:34 +0300
> schrieb Andrew Gaidukevich <3du...@mail.ru>:
>
> >
> > Hello! My name is Andrew!
> > I need help!
> > I cant compile LMMS without this!
> > I got this error
Am Sun, 19 Jun 2022 11:18:07 -0700
schrieb Thibaut Cuvelier :
> On Sat, 18 Jun 2022, 11:04 Kornel Benko, wrote:
>
> > Am Sat, 18 Jun 2022 18:22:34 +0300
> > schrieb Andrew Gaidukevich <3du...@mail.ru>:
> >
> > >
> > > Hello! My name is Andr
Am Sat, 18 Jun 2022 18:22:34 +0300
schrieb Andrew Gaidukevich <3du...@mail.ru>:
>
> Hello! My name is Andrew!
> I need help!
> I cant compile LMMS without this!
> I got this error… help me to solve this
> -- Could NOT find Qt6X11Extras (missing: Qt6X11Extras_DIR)
> CM
On Fri, Jan 14, 2022 at 07:25:31AM +0200, Dr Eberhard Lisse wrote:
> I came across the reference in the UserGuide to Program Listings in the
> Embedded Objects Manual, due to a recent thread, and noticed that that
> reference is not a (Clickable) Cross Reference.
>
> Would making all those referen
Hi,
I came across the reference in the UserGuide to Program Listings in the
Embedded Objects Manual, due to a recent thread, and noticed that that
reference is not a (Clickable) Cross Reference.
Would making all those references cross references be worth of a
request-for feature?
I realize the
Le 07/05/2021 à 07:57, Andreas Nicolai a écrit :
Hi,
sorry, this question is unrelated to ongoing Lyx development, but I have
a question regarding the setup of the Lyx package repository. I
basically want to setup a similar PPA repository as Lyx does it for our
project, but I need some help
oject, but I need some help. Who would be the person to direct my
> questions to?
Liviu Andronic; not sure how much responsive he is nowadays.
Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Hi,
sorry, this question is unrelated to ongoing Lyx development, but I have
a question regarding the setup of the Lyx package repository. I
basically want to setup a similar PPA repository as Lyx does it for our
project, but I need some help. Who would be the person to direct my
questions to
On 1/13/21 12:45 PM, Lorenzo Bertini wrote:
> Il 13/01/21 18:22, Richard Kimberly Heck ha scritto:
>> Hi, everyone,
>>
>> We hope to release LyX 2.4.0 in the next couple months. Before then,
>> there is some work that needs to be done on the documentation. If you've
>> always wanted to contribute t
Il 13/01/21 18:22, Richard Kimberly Heck ha scritto:
> Hi, everyone,
>
> We hope to release LyX 2.4.0 in the next couple months. Before then,
> there is some work that needs to be done on the documentation. If you've
> always wanted to contribute to LyX but haven't because you don't know
> how to
Hi, everyone,
We hope to release LyX 2.4.0 in the next couple months. Before then,
there is some work that needs to be done on the documentation. If you've
always wanted to contribute to LyX but haven't because you don't know
how to code, then this is your chance!
The main task that needs doing i
On Friday, 5 June 2020 20.27.28 WEST Richard Kimberly Heck wrote:
> Mostly I just wanted to make sure you knew about the re-packaging. It's such
> a trivial change that I wasn't sure I wanted to do it myself
>
> Riki
BTW as followup to this message, I have updated to 2.3.5.2.
The packages ar
On 6/5/20 5:43 AM, José Abílio Matos wrote:
>
> On Friday, 5 June 2020 05.06.19 WEST Richard Kimberly Heck wrote:
>
> > Please ignore the date in Help> About LyX That will be fixed.
>
>
>
> Honestly soon no one will care about the date. :-)
&g
On Friday, 5 June 2020 05.06.19 WEST Richard Kimberly Heck wrote:
> Please ignore the date in Help> About LyX That will be fixed.
Honestly soon no one will care about the date. :-)
As long as it is in the past.
> Speaking of which, José, you might want to rebuild
No I do
On 5/3/20 1:08 PM, Jürgen Spitzmüller wrote:
> Am Sonntag, den 03.05.2020, 10:40 -0400 schrieb Scott Kostyshak:
>> Just compiled current master (544770a5) and when I do Help > User
>> Guide
>> I get an error "Incompatible command name."
> I think it still do
Am Sonntag, den 03.05.2020, 10:40 -0400 schrieb Scott Kostyshak:
> Just compiled current master (544770a5) and when I do Help > User
> Guide
> I get an error "Incompatible command name."
I think it still documents a counter inset type that has been removed.
Jürgen
>
Am Sun, 3 May 2020 10:40:46 -0400
schrieb Scott Kostyshak :
> Just compiled current master (544770a5) and when I do Help > User Guide
> I get an error "Incompatible command name."
>
> Scott
Same here.
Kornel
pgpapEgRv3RvJ.pgp
Description: Digitale Signatur
Just compiled current master (544770a5) and when I do Help > User Guide
I get an error "Incompatible command name."
Scott
signature.asc
Description: PGP signature
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Sonntag, den 03.05.2020, 09:14 +0200 schrieb Jürgen Spitzmüller:
> (Also the counters should be sorted alphabetically by [localized]
> GUIstring rather than by key)
This one's done.
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel
Am Sonntag, den 03.05.2020, 02:12 +0200 schrieb Richard Kimberly Heck:
> diff --git a/src/insets/InsetCounter.cpp
> b/src/insets/InsetCounter.cpp
>
> index 32f7c64..a6e4d0d 100644
>
> --- a/src/insets/InsetCounter.cpp
>
> +++ b/src/insets/InsetCounter.cpp
>
> @@ -60,12 +60,11 @@ InsetCounter::I
:
> > >
> > > > > Nice! Can we add "Qt version" to the CMake output? In case it is
> > > > > helpful, here are my current outputs for master with CMake and with
> > > > > autotools:
> > > > >
> > > > >
ut? In case it is
> > > > helpful, here are my current outputs for master with CMake and with
> > > > autotools:
> > > >
> > > >
> > >
> > > The QT-version and 'LyX files dir' is also at Help->About->Versi
r with CMake and with
> > > autotools:
> > >
> > >
> >
> > The QT-version and 'LyX files dir' is also at Help->About->Version. Why
> > should it go
> > here too?
> >
> > Kornel
>
> OK, the 'LyX files dir&#x
Am Wed, 25 Mar 2020 14:44:09 +0100
schrieb Kornel Benko :
> > Nice! Can we add "Qt version" to the CMake output? In case it is
> > helpful, here are my current outputs for master with CMake and with
> > autotools:
> >
> >
>
> The QT-version and &
Am Wed, 25 Mar 2020 09:35:03 -0400
schrieb Scott Kostyshak :
> On Wed, Mar 25, 2020 at 01:33:15PM +0100, Kornel Benko wrote:
> > commit 3df9525a13de33b235d41a94cac9d2b1b8546c9b
> > Author: Kornel Benko
> > Date: Wed Mar 25 13:48:16 2020 +0100
> >
> > Cmake
On Wed, Mar 25, 2020 at 01:33:15PM +0100, Kornel Benko wrote:
> commit 3df9525a13de33b235d41a94cac9d2b1b8546c9b
> Author: Kornel Benko
> Date: Wed Mar 25 13:48:16 2020 +0100
>
> Cmake build: Extend build info in Help>About
>
> Added list of used cmake opt
and have
> > a flag for
> > developers?
>
> Yes. Sometimes (while bisecting for example) it is faster to test.
>
> > These are questions that cmake users might have and having answers to these
> > in
> > INSTALL.cmake will help orient them
> spend the time
> building extra things? If so, why wasn’t LYX_INSTALL the default and have a
> flag for
> developers?
Yes. Sometimes (while bisecting for example) it is faster to test.
> These are questions that cmake users might have and having answers to these in
> INSTALL.cm
for development, you don’t want to spend
the time building extra things? If so, why wasn’t LYX_INSTALL the default and
have a flag for developers?
These are questions that cmake users might have and having answers to these in
INSTALL.cmake will help orient them with the lyx viewpoint of how cmake
build
> >> ninja-build install
> >>
> >> This fails with
> >> CMake Error at po/cmake_install.cmake:45 (file):
> >> file INSTALL cannot find "/tmp/lyx/build/po/ar.gmo"
> >>
> >> So I tried
> >>
> &g
t;>
>> So I tried
>>
>> ninja-build translations
>> ninja-build install
>>
>> This seems to work and lyx2.3 runs, but /tmp/install does not contain
>> UserGuide or any of the other help documentation.
>>
>> What am I missing?
>>
&g
> So I tried
>
> ninja-build translations
> ninja-build install
>
> This seems to work and lyx2.3 runs, but /tmp/install does not contain
> UserGuide or any of the other help documentation.
>
> What am I missing?
>
> Thanks - Vince
>
Kornel
pgp
Am Mon, 21 Oct 2019 17:46:41 -0400
schrieb Vincent Lucarelli :
> Hi,
>
> I tried to use cmake on CentOS 7 to build and install lyx from a
> clone of the git repo. The binary built and installed fine, but if I
> try to access in the gui "Help > User's Guide"
Hi,
I tried to use cmake on CentOS 7 to build and install lyx from a clone of
the git repo. The binary built and installed fine, but if I try to access
in the gui "Help > User's Guide" I get the error "Lyx: unable to find
`UserGuide'. Bad installation?"
There
Am Samstag, den 29.12.2018, 09:28 -0500 schrieb Paul A. Rubin:
> Wow, that was quick! Incidentally, I had a suspicion about the blank
> in
> the layout name, so I tried using a hyphen (which seems to work for
> LyX-Code), but the problem persisted. The modified name
> ("Declare-input/output") st
On 12/29/18 7:43 AM, Jürgen Spitzmüller wrote:
Am Freitag, den 28.12.2018, 17:54 -0500 schrieb Paul A. Rubin:
I've also run into a failure
with Edit > Undo that baffles me.
This is most probably
https://www.lyx.org/trac/ticket/11292
Jürgen
Looks like the fix is in for this problem as well. Th
try things out). The module is in the
local layout section of the document settings, and requires the
algorithmicx.sty LaTeX package.
Thanks for any help or advice.
There were some bugs involved: the problem of the erroneously output
separator and parsing problems of Autonests and IsAutonestedB
Am Freitag, den 28.12.2018, 17:54 -0500 schrieb Paul A. Rubin:
> I've also run into a failure
> with Edit > Undo that baffles me.
This is most probably
https://www.lyx.org/trac/ticket/11292
Jürgen
signature.asc
Description: This is a digitally signed message part
e to try things out). The module is in the
> local layout section of the document settings, and requires the
> algorithmicx.sty LaTeX package.
>
> Thanks for any help or advice.
There were some bugs involved: the problem of the erroneously output
separator and parsing problems of A
e
algorithmicx.sty LaTeX package.
Thanks for any help or advice.
Paul
mwe.lyx
Description: application/lyx
Can someone on Windows help this person?
https://www.lyx.org/trac/ticket/11173
Riki
Le 08/06/2018 à 19:40, Richard Kimberly Heck a écrit :
Riki, can I backport ?
OK, and congratulations for figuring that out.
Done thanks. And about the congratulations, I am the one who created
this event mess, so I have to look after it.
JMarc
1 - 100 of 1751 matches
Mail list logo
