Am 13.01.2016 um 02:06 schrieb Richard Heck :
>
> On 01/12/2016 06:32 PM, Scott Kostyshak wrote:
>> Dear all,
>>
>> There is a question of whether we should release our binary for Windows
>> compiled against Qt 5.5.1 or 5.6.0.
>>
>> My opinion is that we should release it with
lAm Mittwoch, 13. Januar 2016 um 08:57:39, schrieb Guenter Milde
> On 2016-01-12, Kornel Benko wrote:
> > Am Dienstag, 12. Januar 2016 um 22:07:59, schrieb Guenter Milde
> >
>
> Dear Kornel,
>
> ...
>
> >> with "default-output=DVI". However, the still
On 2016-01-12, Kornel Benko wrote:
> Am Dienstag, 12. Januar 2016 um 22:07:59, schrieb Guenter Milde
>
Dear Kornel,
...
>> with "default-output=DVI". However, the still listed tests with LuaTeX
>> (dvi3) seem like an oversight in the test-creation scripts.
> Yes, if
Am Mittwoch, 13. Januar 2016 um 14:41:04, schrieb Kornel Benko
> Am Mittwoch, 13. Januar 2016 um 00:47:57, schrieb Enrico Forestieri
>
> > On Tue, Jan 12, 2016 at 06:32:11PM -0500, Scott Kostyshak wrote:
> > > Dear all,
> > >
> > > There is a question of whether
Am Mittwoch, 13. Januar 2016 um 00:47:57, schrieb Enrico Forestieri
> On Tue, Jan 12, 2016 at 06:32:11PM -0500, Scott Kostyshak wrote:
> > Dear all,
> >
> > There is a question of whether we should release our binary for Windows
> > compiled against Qt 5.5.1 or 5.6.0.
> >
> >
Le 11/01/2016 20:53, Georg Baum a écrit :
The few times I did run that script it worked fine. If you look at a few
files in the diff and see no peculiar change I'd say it is safe to commit.
One thing we should keep in mind is that this would also produce a 3 MB
2.1.4->2.1.5 patch.
Richard, is
Le 13/01/2016 17:46, Richard Heck a écrit :
On 01/12/2016 04:36 PM, Guillaume Munch wrote:
diff --git a/lib/lyx2lyx/lyx_2_2.py b/lib/lyx2lyx/lyx_2_2.py
index 5a639cd..5361420 100644
--- a/lib/lyx2lyx/lyx_2_2.py
+++
Le 13/01/2016 01:00, Richard Heck a écrit :
On 01/12/2016 06:53 PM, Enrico Forestieri wrote:
On Tue, Jan 12, 2016 at 11:49:54PM +0100, Enrico Forestieri wrote:
On Mon, Jan 11, 2016 at 03:04:33AM +, Guillaume Munch wrote:
For the symbol itself, my suggestion was a very elongated version
Dear Kornel,
On 2016-01-13, Kornel Benko wrote:
> Am Mittwoch, 13. Januar 2016 um 16:54:05, schrieb Guenter Milde
>> After applying the second one (aas_sample), I experienced a test failure:
>> The following tests FAILED:
>> 1945 - EXAMPLES_export/examples/aas_sample_pdf4_systemF (Failed)
On Wed, Jan 13, 2016 at 02:44:27PM +0100, Kornel Benko wrote:
> Am Mittwoch, 13. Januar 2016 um 14:41:04, schrieb Kornel Benko
>
> > Am Mittwoch, 13. Januar 2016 um 00:47:57, schrieb Enrico Forestieri
> >
> > > I am not aware of any significant issues with 5.5.1
On Wed, Jan 13, 2016 at 06:40:21PM +, Guillaume Munch wrote:
> Le 13/01/2016 01:00, Richard Heck a écrit :
> >On 01/12/2016 06:53 PM, Enrico Forestieri wrote:
> >>On Tue, Jan 12, 2016 at 11:49:54PM +0100, Enrico Forestieri wrote:
> >>>On Mon, Jan 11, 2016 at 03:04:33AM +, Guillaume Munch
Am Mittwoch, 13. Januar 2016 um 21:50:15, schrieb Guenter Milde
> Dear Kornel,
>
> On 2016-01-13, Kornel Benko wrote:
> > Am Mittwoch, 13. Januar 2016 um 16:54:05, schrieb Guenter Milde
>
> >> After applying the second one (aas_sample), I experienced a test failure:
>
> >>
On 2016-01-13, Kornel Benko wrote:
> Am 13. Januar 2016 um 08:57:39, schrieb Guenter Milde
>> On 2016-01-12, Kornel Benko wrote:
Dear Kornel,
...
>> > Yes, if output is set to dvi, then all dvi formats are tested.
>> > The same is valid for pdf, ==> test all pdf formats
>>
On Tue, Jan 12, 2016 at 11:48:41PM +, Guillaume Munch wrote:
> Le 12/01/2016 22:49, Enrico Forestieri a écrit :
> >
> >Please, can you try the attached patch and report back whether it does
> >what you expect?
>
> It does, thank you. That was definitely the small issue that was the
> most
Am Mittwoch, 13. Januar 2016 um 22:50:58, schrieb Guenter Milde
> On 2016-01-13, Kornel Benko wrote:
> > Am 13. Januar 2016 um 08:57:39, schrieb Guenter Milde
> >> On 2016-01-12, Kornel Benko wrote:
>
> Dear Kornel,
>
> ...
>
> >> > Yes, if output is
Guillaume Munch wrote:
> Le 12/01/2016 01:42, Pavel Sanda a écrit :
>> Guillaume Munch wrote:
>>> Actually yes I am documenting a new rule, but it isn't mine. The new
>>> rule requires a LFUN format increment and a LyX format increment
>>
>> Do you have by chance link to LFUN format increment
Am 06.12.2015 um 22:07 schrieb Uwe Stöhr:
When I compile LyX 2.2git with Qt5.5 and MSVC 2013 in install mode this
command is executed:
msbuild INSTALL.vcxproj /p:Configuration=Release
But this leads now to these errors:
"D:\LyXGit\Master\compile-2013\INSTALL.vcxproj" (Standardziel) (1) ->
Am 13.01.2016 um 05:41 schrieb Peter Kümmel:
If 5.6 is to buggy, we can also use 5.5.1 build with mingw.
Apparently beta1 will be built with Qt 5.5.1. And now, after some hours
of fiddling with CMake I am able to build Qt 5.5.1 with MSVC 2010 and
the result looks promising - stable LyX
Am 12.01.2016 um 20:21 schrieb Peter Kümmel:
Hi Uwe, could you try development/cmake/mingw.bat.
Not yet. I only have max. 2 hours a day and need the time to prepare and
test the installer for beta 1. I will try this as soon as beta 1 is out OK?
regards Uwe
Am Donnerstag, 14. Januar 2016 um 00:23:30, schrieb Uwe Stöhr
> Am 06.12.2015 um 22:07 schrieb Uwe Stöhr:
>
> > When I compile LyX 2.2git with Qt5.5 and MSVC 2013 in install mode this
> > command is executed:
> >
> > msbuild INSTALL.vcxproj /p:Configuration=Release
> >
> > But
Am 13.01.2016 um 00:32 schrieb Scott Kostyshak:
There is a question of whether we should release our binary for Windows
compiled against Qt 5.5.1 or 5.6.0.
Hi Scott and Peter,
as the consensus is to use 5.5.1 I worked on that. I could compile LyX
2.2git with Qt 5.5.1 and MSVC 2010
Am 13.01.2016 um 01:20 schrieb Peter Kümmel:
Plain building should work now. But i dont know what comes after that, to get a
real installer.
- Download the installer source file:
http://ftp.lyx.de/LyX%202.2.0-test/LyXPackageComplete220-test.zip.filepart
- unzip it and follow the
Am 03.01.2016 um 17:15 schrieb Scott Kostyshak:
I don't understand how installers work for 32-bit vs 64-bit. Normally
does our Windows installer contain both 32-bit and 64-bit binaries?
It contains only a 32bit version. Only with MSVC 2013 or never it is
possible to compile LyX as 64bit
Am 12.01.2016 um 20:21 schrieb Peter Kümmel:
Hi Uwe, could you try development/cmake/mingw.bat.
Call it from any path. The script creates the build folder
"compile-mingw". Only requirement is that msvc2010-deps
is on the same level as the lyx source dir (and the C:\Qt
installation)
After the
Am 13.01.2016 um 09:43 schrieb Stephan Witt:
What do others think?
Under these conditions I’d prefer the use of Qt 5.5.1 over a 5.6.0 too.
OK, I updated the batch script to use Qt 5.5.1.
Perhaps one relevant point here is that we have often released a new
minor version pretty quickly.
Dear Scott,
maybe it is not the time now, yet there are two more patches for the ctests
and examples in the pipeline...
After applying the second one (aas_sample), I experienced a test failure:
The following tests FAILED:
1945 - EXAMPLES_export/examples/aas_sample_pdf4_systemF (Failed)
On 01/12/2016 04:36 PM, Guillaume Munch wrote:
>
> diff --git a/lib/lyx2lyx/lyx_2_2.py b/lib/lyx2lyx/lyx_2_2.py
> index 5a639cd..5361420 100644
> --- a/lib/lyx2lyx/lyx_2_2.py
> +++ b/lib/lyx2lyx/lyx_2_2.py
> @@ -2184,6 +2184,23
Am Mittwoch, 13. Januar 2016 um 16:54:05, schrieb Guenter Milde
> Dear Scott,
>
> maybe it is not the time now, yet there are two more patches for the ctests
> and examples in the pipeline...
>
>
> After applying the second one (aas_sample), I experienced a test failure:
>
28 matches
Mail list logo