Le 06/01/2016 11:09, Kornel Benko a écrit :
It would be nice if we could converge to the same algorithm in the two
build systems. If you disagree on what autotools do, we can discuss
adaptations.
In cmake it is an option, which is set _before_ we know the compiler.
Actually it is the same in
Am Mittwoch, 6. Januar 2016 um 10:26:24, schrieb Jean-Marc Lasgouttes
> Le 05/01/2016 18:04, Kornel Benko a écrit :
> >> Isn't LYX_ENABLE_CXX11=ON the default for clang?
> >
> > By default it is OFF for any compiler.
> >
> >> I have to use —-disable-cxx11 with auto tools.
>
Le 05/01/2016 18:04, Kornel Benko a écrit :
Isn't LYX_ENABLE_CXX11=ON the default for clang?
By default it is OFF for any compiler.
I have to use —-disable-cxx11 with auto tools.
Why is it working with cmake for you?
Where is your Qt5 framework?
What compiler are you using?
Kornel, it
Scott Kostyshak wrote:
> (although I still don't understand why). I get another instance of the
> same error though when using a build directory instead of an in-source
> build.
Recipe? P
Am 06.01.2016 um 14:23 schrieb Kornel Benko:
Am Mittwoch, 6. Januar 2016 um 14:15:22, schrieb Stephan Witt
Am 06.01.2016 um 13:35 schrieb Peter Kümmel :
Am 03.01.2016 um 20:05 schrieb Georg Baum:
So far we have never released any 64bit windows
Am 03.01.2016 um 20:05 schrieb Georg Baum:
So far we have never released any 64bit windows binary. This is fine, since
64bit windows can execute 32bit binaries, and nobody complained yet about
LyX hitting the 32bit memory limit (around 3.5 GB on windows). I would not
switch to 64bit at this
Am 03.01.2016 um 17:09 schrieb Kornel Benko:
It creates LyX22-2.2.0-win32.zip.
Probably not an installer like used in windows.
Yes, only the files generated my "make install".
I added "make install" to the script, and the NSIS
installer should use the files in LYX_INSTALLED/
Kornel
Le 06/01/2016 13:25, Peter Kümmel a écrit :
Am 05.01.2016 um 12:28 schrieb Jean-Marc Lasgouttes:
Le 20/12/2015 15:07, Peter Kümmel a écrit :
Recently I gave away the computer which I've used when I was
very busy on LyX. It was an Athlon XP 2GHz singlecore.
I was interested how the hardware
4. Do we also want to try releasing an installer built with mingw?
(Does that build an installer? or just LyX?)
It builds just LyX. Building an installer needs a built LyX, it should not
matter whether it was built by MSVC or mingw (except for the MSVC
prerequisites, these are not needed to be
Am Mittwoch, 6. Januar 2016 um 14:15:22, schrieb Stephan Witt
> Am 06.01.2016 um 13:35 schrieb Peter Kümmel :
> >
> >
> >
> > Am 03.01.2016 um 20:05 schrieb Georg Baum:
> >>
> >> So far we have never released any 64bit windows binary. This is fine, since
Am 06.01.2016 um 14:15 schrieb Stephan Witt:
Am 06.01.2016 um 13:35 schrieb Peter Kümmel :
Am 03.01.2016 um 20:05 schrieb Georg Baum:
So far we have never released any 64bit windows binary. This is fine, since
64bit windows can execute 32bit binaries, and nobody
Am 05.01.2016 um 12:28 schrieb Jean-Marc Lasgouttes:
Le 20/12/2015 15:07, Peter Kümmel a écrit :
Recently I gave away the computer which I've used when I was
very busy on LyX. It was an Athlon XP 2GHz singlecore.
I was interested how the hardware progress looks like from
the LyX perspective,
Am 06.01.2016 um 13:35 schrieb Peter Kümmel :
>
>
>
> Am 03.01.2016 um 20:05 schrieb Georg Baum:
>>
>> So far we have never released any 64bit windows binary. This is fine, since
>> 64bit windows can execute 32bit binaries, and nobody complained yet about
>> LyX hitting
Am Mittwoch, 6. Januar 2016 um 14:27:24, schrieb Peter Kümmel
> Am 03.01.2016 um 17:09 schrieb Kornel Benko:
> >
> > It creates LyX22-2.2.0-win32.zip.
> > Probably not an installer like used in windows.
>
> Yes, only the files generated my "make install".
>
> I added "make
Le 06/01/2016 14:23, Kornel Benko a écrit :
Is there a reason why we cannot use int64_t instead of long long?
Or maybe just use size_t and ptrdiff_t? I suspect these are the ones we
really need.
JMarc
Am 06.01.2016 um 14:45 schrieb Jean-Marc Lasgouttes:
Le 06/01/2016 13:25, Peter Kümmel a écrit :
Am 05.01.2016 um 12:28 schrieb Jean-Marc Lasgouttes:
Le 20/12/2015 15:07, Peter Kümmel a écrit :
Recently I gave away the computer which I've used when I
was
very busy on LyX. It was an Athlon
Le 06/01/2016 16:54, Peter Kümmel a écrit :
Is this 2.1 or 2.2? In release mode?
The one shipped by Ubuntu, so I assume some 2.1 version.
Then hopefully the performance with 2.2 will be better.
JMarc
Am 06.01.2016 um 14:35 schrieb Kornel Benko:
Am Mittwoch, 6. Januar 2016 um 14:27:24, schrieb Peter Kümmel
Am 03.01.2016 um 17:09 schrieb Kornel Benko:
It creates LyX22-2.2.0-win32.zip.
Probably not an installer like used in windows.
Yes, only the files generated my
Am 06.01.2016 um 13:32 schrieb Peter Kümmel:
4. Do we also want to try releasing an installer built
with mingw?
(Does that build an installer? or just LyX?)
It builds just LyX. Building an installer needs a built
LyX, it should not
matter whether it was built by MSVC or mingw (except for
the
Am 28.12.2015 um 14:48 schrieb Scott Kostyshak:
Ah, the cmakebin variable is not set, a rest of the bot script. Replacing the
variable by cmake should fix it.
committed this.
Yes this was the problem. There seem to be several unset variables. Can
we use
set -u
with /bin/sh or is that
Guenter Milde wrote:
> Without special code for tex2lyx, \AA and \aa is the better
> lib/unicodesymbols replacement, as there is a fallback for \r{A}, \r{a}
> but not for \aa, \AA.
>
> With the special code, it is a matter of taste - maybe best decided by a
> native speaker of a Scandinavian
Georg Baum wrote:
> Pavel Sanda wrote:
>
> > Scott Kostyshak wrote:
> >> (although I still don't understand why). I get another instance of the
> >> same error though when using a build directory instead of an in-source
> >> build.
> >
> > Recipe? P
>
> Starting from the top level source
Jean-Marc Lasgouttes wrote:
> >Sadly, moving cursor in paragraph is considerably slower than
> >in my current 2.0 build :(
>
> And how does this compare to a 2.1 build?
>
> Could you provide a profile log for 2.2 being slow?
Ok, I made two profiles for sysprof.
The way to reproduce:
my
Pavel Sanda wrote:
> Scott Kostyshak wrote:
>> (although I still don't understand why). I get another instance of the
>> same error though when using a build directory instead of an in-source
>> build.
>
> Recipe? P
Starting from the top level source directory:
./autogen.sh
mkdir buildtest
cd
Guillaume Munch wrote:
> Le 03/01/2016 11:04, Georg Baum a écrit :
>>
>> Really? The amount of code changes is big, and I cannot see from the
>> patch that it has no influence on the .tex input/output or mathml/xhtml
>> output. If it can not be 100% guaranteed that only the display is changed
>>
25 matches
Mail list logo