Jean-Marc Lasgouttes wrote:
> Le 08/01/2016 10:08, Stephan Witt a écrit :
>> Am 08.01.2016 um 09:28 schrieb Jean-Marc Lasgouttes :
>>> Yes, unless somone has a different brilliant idea.
>
>>> This problem will go away in 2.3.
>>
>> How? With your fix? Does it fix wrong LyX code or is it some work
Le 09/01/16 23:01, Scott Kostyshak a écrit :
I do not understand it. I'm fine as long as another developer gives an
explicit +1.
I see it is in now. It is fine for me.
JMarc
Am Samstag, 9. Januar 2016 um 15:02:14, schrieb Kornel Benko
> Am Samstag, 9. Januar 2016 um 14:27:46, schrieb Stephan Witt
> > Am 08.01.2016 um 10:26 schrieb Jean-Marc Lasgouttes :
> > >
> > > Le 08/01/2016 10:08, Stephan Witt a écrit :
> > >> Am 08.01.2016 um 09:28 schrieb Jean-Marc Lasgouttes
On Sat, Jan 09, 2016 at 02:27:46PM +0100, Stephan Witt wrote:
> Am 08.01.2016 um 10:26 schrieb Jean-Marc Lasgouttes :
> >
> > Le 08/01/2016 10:08, Stephan Witt a écrit :
> >> Am 08.01.2016 um 09:28 schrieb Jean-Marc Lasgouttes :
> >>> Yes, unless somone has a different brilliant idea.
> >>
> >> A
Am Samstag, 9. Januar 2016 um 14:27:46, schrieb Stephan Witt
> Am 08.01.2016 um 10:26 schrieb Jean-Marc Lasgouttes :
> >
> > Le 08/01/2016 10:08, Stephan Witt a écrit :
> >> Am 08.01.2016 um 09:28 schrieb Jean-Marc Lasgouttes :
> >>> Yes, unless somone has a different brilliant idea.
> >>
> >> A
Am 08.01.2016 um 10:26 schrieb Jean-Marc Lasgouttes :
>
> Le 08/01/2016 10:08, Stephan Witt a écrit :
>> Am 08.01.2016 um 09:28 schrieb Jean-Marc Lasgouttes :
>>> Yes, unless somone has a different brilliant idea.
>>
>> Am I right that it makes explicit what is otherwise implicit? So it is safe
Am 08.01.2016 um 10:26 schrieb Jean-Marc Lasgouttes :Le 08/01/2016 10:08, Stephan Witt a écrit :Am 08.01.2016 um 09:28 schrieb Jean-Marc Lasgouttes :Yes, unless somone has a different brilliant idea.Am I right that it makes explicit what is otherwise implicit? So it is safe to commit?Yes, I think s
Am 09.01.2016 um 13:12 schrieb Stephan Witt:
Am 08.01.2016 um 13:15 schrieb Kornel Benko :
Am Freitag, 8. Januar 2016 um 13:09:38, schrieb Stephan Witt
Am 08.01.2016 um 11:53 schrieb Kornel Benko :
Am Freitag, 8. Januar 2016 um 09:10:00, schrieb Stephan Witt
OR (maybe)
include_dire
Am 08.01.2016 um 13:15 schrieb Kornel Benko :
>
> Am Freitag, 8. Januar 2016 um 13:09:38, schrieb Stephan Witt
>> Am 08.01.2016 um 11:53 schrieb Kornel Benko :
>>>
>>> Am Freitag, 8. Januar 2016 um 09:10:00, schrieb Stephan Witt
>>>
> OR (maybe)
> include_directories((BEFORE
>
Am Freitag, 8. Januar 2016 um 13:09:38, schrieb Stephan Witt
> Am 08.01.2016 um 11:53 schrieb Kornel Benko :
> >
> > Am Freitag, 8. Januar 2016 um 09:10:00, schrieb Stephan Witt
> >
> >>> OR (maybe)
> >>> include_directories((BEFORE
> >>>${TOP_SRC_DIR}/src/tex2lyx
> >>>${TO
Am 08.01.2016 um 11:53 schrieb Kornel Benko :
>
> Am Freitag, 8. Januar 2016 um 09:10:00, schrieb Stephan Witt
>>> OR (maybe)
>>> include_directories((BEFORE
>>>${TOP_SRC_DIR}/src/tex2lyx
>>>${TOP_SRC_DIR}/src/support/minizip)
>>> include_directories(${ZLIB_INCLUDE_DIR})
Am Freitag, 8. Januar 2016 um 09:10:00, schrieb Stephan Witt
> > OR (maybe)
> > include_directories((BEFORE
> > ${TOP_SRC_DIR}/src/tex2lyx
> > ${TOP_SRC_DIR}/src/support/minizip)
> > include_directories(${ZLIB_INCLUDE_DIR})
>
> Yes, this works too. BTW, what is "src/su
Le 08/01/2016 10:08, Stephan Witt a écrit :
Am 08.01.2016 um 09:28 schrieb Jean-Marc Lasgouttes :
Yes, unless somone has a different brilliant idea.
Am I right that it makes explicit what is otherwise implicit? So it is safe to
commit?
Yes, I think so. The question is only maintainability.
Am 08.01.2016 um 09:28 schrieb Jean-Marc Lasgouttes :
>
> Le 08/01/2016 09:17, Stephan Witt a écrit :
>> A possible solution I’ve attached as patch.
>> Any better solution or ok to commit?
>
> Yes, unless somone has a different brilliant idea.
Am I right that it makes explicit what is otherwise
Le 08/01/2016 09:17, Stephan Witt a écrit :
A possible solution I’ve attached as patch.
Any better solution or ok to commit?
Yes, unless somone has a different brilliant idea. The problem is that
libc++ provides std::next even when not in C++11 mode.
This problem will go away in 2.3.
JMarc
Am 07.01.2016 um 15:39 schrieb Stephan Witt :
> ...
> The next problem now is an error when compiling src/Compare.cpp:
>
> Stephan
>
> ===
> CompileC
> /Users/stephan/git/lyx-build/cmake/2.2.0dev/src/LyX.build/Debug/LyX.build/Objects-normal/x86_64/Compare.o
> src/Compare.cpp normal x86_64 c
> Am 07.01.2016 um 16:00 schrieb Kornel Benko :
>
> Am Donnerstag, 7. Januar 2016 um 15:39:47, schrieb Stephan Witt
>
>> Am 07.01.2016 um 14:51 schrieb Kornel Benko :
>>>
>>> Am Donnerstag, 7. Januar 2016 um 14:30:58, schrieb Stephan Witt
>>>
The position of -I/opt/local/linclude in fro
Am 07.01.2016 um 14:51 schrieb Kornel Benko :
>
> Am Donnerstag, 7. Januar 2016 um 14:30:58, schrieb Stephan Witt
>
>> The position of -I/opt/local/linclude in front of
>> -I/Users/stephan/git/lyx/3rdparty/boost is the problem.
>> I wrote this in my previous mail.
>
> This should be easy
>
>
Stefan, are you sure using clean build-dir?
At least CMakeCache.txt may contain some include paths from previous run.
For instance changing -DLYX_EXTERNAL_BOOST=.. without removing CMakeCache.txt
is asking for trouble IMHO.
Am Donnerstag, 7. Januar 2016 um 13:46:42, schrieb Stephan Witt
> Am 07
Am 07.01.2016 um 11:01 schrieb Kornel Benko :
>
> Am Mittwoch, 6. Januar 2016 um 11:39:10, schrieb Jean-Marc Lasgouttes
>
>> 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 autotoo
Am Mittwoch, 6. Januar 2016 um 11:39:10, schrieb Jean-Marc Lasgouttes
> 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 cma
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.
> >> Why is it working w
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 would
Am 05.01.2016 um 18:20 schrieb Stephan Witt :
>
> Am 05.01.2016 um 18:04 schrieb Kornel Benko :
>>
>> Am Dienstag, 5. Januar 2016 um 17:59:10, schrieb Stephan Witt
>>
>>> Am 05.01.2016 um 15:07 schrieb Edwin Leuven :
On 05 Jan 2016, at 02:13, Stephan Witt wrote:
> Hi Lyxers,
>>>
Am 05.01.2016 um 18:04 schrieb Kornel Benko :
>
> Am Dienstag, 5. Januar 2016 um 17:59:10, schrieb Stephan Witt
>
>> Am 05.01.2016 um 15:07 schrieb Edwin Leuven :
>>>
>>> On 05 Jan 2016, at 02:13, Stephan Witt wrote:
Hi Lyxers,
it’s a long overdue task I had on my ToDo list:
>
Am Dienstag, 5. Januar 2016 um 17:59:10, schrieb Stephan Witt
> Am 05.01.2016 um 15:07 schrieb Edwin Leuven :
> >
> > On 05 Jan 2016, at 02:13, Stephan Witt wrote:
> >> Hi Lyxers,
> >>
> >> it’s a long overdue task I had on my ToDo list:
> >> the update of my system to latest OS X - El Capitan
Am 05.01.2016 um 15:07 schrieb Edwin Leuven :
>
> On 05 Jan 2016, at 02:13, Stephan Witt wrote:
>> Hi Lyxers,
>>
>> it’s a long overdue task I had on my ToDo list:
>> the update of my system to latest OS X - El Capitan.
>>
>> It’s accompanied by an update of many components including the
>> de
On 05 Jan 2016, at 02:13, Stephan Witt wrote:
> Hi Lyxers,
>
> it’s a long overdue task I had on my ToDo list:
> the update of my system to latest OS X - El Capitan.
>
> It’s accompanied by an update of many components including the
> development tools, the compiler, the IDE, etc.
>
> The situ
Hi Lyxers,
it’s a long overdue task I had on my ToDo list:
the update of my system to latest OS X - El Capitan.
It’s accompanied by an update of many components including the
development tools, the compiler, the IDE, etc.
The situation after doing so is as follows:
1. The build with autotools
30 matches
Mail list logo