On Sat, Jun 24, 2023 at 07:28:59AM +0200, Christoph Schmitz wrote:
> Hello,
>
> Attached is my config.log.
The attachment looks corrupted. Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Hello,
Attached is my config.log.
Chris
<>
> Am 21.06.2023 um 12:50 schrieb Jean-Marc Lasgouttes :
>
> Le 21/06/2023 à 12:36, Christoph Schmitz a écrit :
>> Hello Scott,
>> Yes,
>> I deleted my local repository already a few times and started from scratch.
>
> Hello,
>
> Could you please
Le 21/06/2023 à 12:36, Christoph Schmitz a écrit :
Hello Scott,
Yes,
I deleted my local repository already a few times and started from scratch.
Hello,
Could you please send your config.log file?
JMarc
These are the commands I use:
cd ~/chris/Git
git clone git://git.lyx.org/lyx LyX
Hello Scott,
Yes,
I deleted my local repository already a few times and started from scratch.
These are the commands I use:
cd ~/chris/Git
git clone git://git.lyx.org/lyx LyX
cd LyX
./autogen.sh
./configure \
--with-version-suffix=-2.4 \
--with-libiconv-prefix=/usr \
On Wed, Jun 21, 2023 at 07:45:09AM +0200, Christoph Schmitz wrote:
>
> I have been unable to compile LyX 2.4 on macOS Sonoma for the past few days.
> The error message I am receiving is as follows:
>
> ...
> Making all in qt
> /Library/Developer/CommandLineTools/usr/bin/make all-am
> make[6]:
Le 11/11/2021 à 19:00, john kennan a écrit :
I don't know how to reply to messages on the list (I'm already subscribed)
Hello John,
What is the problem? That you answer to sender instead?
What are you using for your emails?
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
I don't know how to reply to messages on the list (I'm already subscribed)
Edited the wiki (https://wiki.lyx.org/Devel/Git) to say that one must
change to the lyx directory after the first couple of steps
John
On Thu, Nov 11, 2021 at 11:14 AM john kennan wrote:
> Hi
>
> I'd like to be able
On Thu, Nov 11, 2021 at 11:14:23AM -0600, john kennan wrote:
> Hi
>
> I'd like to be able to compile LyX (on Mac OS Big Sur).
>
> I tried following the instructions on https://wiki.lyx.org/Devel/Git
> Got as far as this:
>
> (base) jk@jkmac-3 ~ % git config --global user.name jkennan
> (base)
Peter Kümmel wrote:
> For iconv and hunspell one can find some CMakeLists.txt at github, not
> ready for MSVC but usable as starting point. AFAIk zlib already ships
> with cmake files.
>
> Would it be an option to add tripped down iconv, hunspell and zlib sources
> to lyx and to build them as
Am 01.11.2015 um 22:02 schrieb Georg Baum:
Peter Kümmel wrote:
For iconv and hunspell one can find some CMakeLists.txt at github, not
ready for MSVC but usable as starting point. AFAIk zlib already ships
with cmake files.
Would it be an option to add tripped down iconv, hunspell and zlib
on behalf of
PhilipPirrip <p...@net.hr>
Sent: Friday, October 30, 2015 8:16 PM
To: lyx-devel@lists.lyx.org
Subject: Re: Compiling LyX on Windows with more recent Visual Studio versions
Hello!
I'm trying to compile LyX for Windows: WinXP VirtualBox, Visual Studio
2010, Qt 5.5, all by the instructions i
Op 31-10-2015 om 14:44 schreef PhilipPirrip:
On 10/31/2015 09:27 AM, PhilipPirrip wrote:
Thanks, David. It did work with Qt 4.8.6
First thing I noticed, though, is that most icons are missing. Have to
investigate. I remember seeing a similar issue here on the list
recently.
The errors
Am 14.10.2015 um 21:52 schrieb Georg Baum:
David Hyde wrote:
I'm interested in looking into this at least a bit (may become deterred
if some dependency nightmare occurs!). I've looked at the current MSVC
dependencies that are in the archive on sourceforge. Which of these
are things that
On 10/31/2015 09:27 AM, PhilipPirrip wrote:
Thanks, David. It did work with Qt 4.8.6
First thing I noticed, though, is that most icons are missing. Have to
investigate. I remember seeing a similar issue here on the list recently.
The errors reported in the message pane are of this kind
Thanks, David. It did work with Qt 4.8.6
First thing I noticed, though, is that most icons are missing. Have to
investigate. I remember seeing a similar issue here on the list recently.
On 10/31/2015 03:53 AM, David Hyde wrote:
I experienced this error as well when setting up my LyX
Hello!
I'm trying to compile LyX for Windows: WinXP VirtualBox, Visual Studio
2010, Qt 5.5, all by the instructions in INSTALL.Win32
No matter what I do in CMake config, the compilation ends with the
messages I give below, and I have no idea what's happening and how to
fix it.
24> --
Le 14/10/2015 07:27, David Hyde a écrit :
Which of these
are things that should actually be downloaded and compiled on the fly?
For example, do you think that Python and ghostscript should be
compiled from source, or do you think it suffices to just include up-to
-date Windows binaries? Same
David Hyde wrote:
> I'm interested in looking into this at least a bit (may become deterred
> if some dependency nightmare occurs!). I've looked at the current MSVC
> dependencies that are in the archive on sourceforge. Which of these
> are things that should actually be downloaded and compiled
Hi Georg,
Thanks for your reply!
> This is possible, but needs some work.
>
> The current MSVC build instructions use some pre-compiled third party
> libraries. Of course these work only for exactly one MSVC version.
> Therefore
> I would propose the following procedure instead of just
David Hyde wrote:
> Hi there,
>
>
> I'm interested in compiling LyX on Windows. I've read through the
> INSTALL.Win32 file and was able to get LyX to compile from source using
> Visual C++ Express 2010, following the instructions in that file.
Great!
> I'm
> wondering though, is it possible
Am 26.04.2013 um 18:46 schrieb Elmar Hinz t3el...@googlemail.com:
On Fri, Apr 26, 2013 at 6:29 PM, Kornel Benko kor...@lyx.org wrote:
Am Freitag, 26. April 2013 um 18:23:56, schrieb Elmar Hinz
t3el...@googlemail.com
Hello,
IMHO there is no libc6 for mac. There is a
Am 26.04.2013 um 18:46 schrieb Elmar Hinz :
>
> On Fri, Apr 26, 2013 at 6:29 PM, Kornel Benko wrote:
> Am Freitag, 26. April 2013 um 18:23:56, schrieb Elmar Hinz
>
> > Hello,
> >
> > IMHO there is no libc6 for mac. There is a
> >
Hi,
here is the command line I use (with cmake, out of source build) in a build
directory (different from LyX main directory). It works with QT installed via
the QT installer package (not from source):
cmake -DLYX_BUNDLE=ON -DLYX_COCOA=ON -DLYX_INSTALL=ON -DLYX_RELEASE=OFF
-DLYX_DEBUG=ON
here is the command line I use (with cmake, out of source build) in a build
directory (different from LyX main directory). It works with QT installed
via the QT installer package (not from source):
cmake -DLYX_BUNDLE=ON -DLYX_COCOA=ON -DLYX_INSTALL=ON -DLYX_RELEASE=OFF
-DLYX_DEBUG=ON
Summary:
* QT 4.8.4 installed via the QT installer package (not from source)
* brew install cmake
* cmake -DLYX_NLS=OFF -DLYX_BUNDLE=ON -DLYX_COCOA=ON -DLYX_INSTALL=ON
-DLYX_RELEASE=OFF -DLYX_DEBUG=ON -DLYX_EXTERNAL_LIBINTL=OFF .
* make
* make install
Errors from cmake:
CMake Error: Target LyX
Am Freitag, 26. April 2013 um 16:44:22, schrieb Elmar Hinz
t3el...@googlemail.com
here is the command line I use (with cmake, out of source build) in a build
directory (different from LyX main directory). It works with QT installed
via the QT installer package (not from source):
cmake
The second one seems to be cased by the first one.
OK didn't follow the instruction:
make LyX2.1 (to build the binary only)
or
make package (to get a mac bundle)
Elmar
--
Elmar Hinz
Freiherr-vom-Stein-Str. 1
33014 Bad Driburg
TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m
or prefered:
b.) Install the devel package for libc6 (on ubuntu libc6-dev)
Elmar
Kornel
Hello,
IMHO there is no libc6 for mac. There is a
/usr/lib/libSystem.dylib - libSystem.B.dylib
Elmar
--
Elmar Hinz
Freiherr-vom-Stein-Str. 1
33014 Bad Driburg
TYPO3 community contact:
Am Freitag, 26. April 2013 um 18:23:56, schrieb Elmar Hinz
t3el...@googlemail.com
Hello,
IMHO there is no libc6 for mac. There is a
/usr/lib/libSystem.dylib - libSystem.B.dylib
Elmar
Is there also a appropriate devel *package*?
Kornel
signature.asc
Description: This is a
OK didn't follow the instruction:
make LyX2.1 (to build the binary only)
or
make package (to get a mac bundle)
Anyway, That doesn't bring in the missing Info.plist.
Question: Why is there no Info.plist in the source?
--
Elmar Hinz
Freiherr-vom-Stein-Str. 1
33014 Bad Driburg
TYPO3
On Fri, Apr 26, 2013 at 6:29 PM, Kornel Benko kor...@lyx.org wrote:
**
Am Freitag, 26. April 2013 um 18:23:56, schrieb Elmar Hinz
t3el...@googlemail.com
Hello,
IMHO there is no libc6 for mac. There is a
/usr/lib/libSystem.dylib - libSystem.B.dylib
Elmar
Is there
Am Freitag, 26. April 2013 um 18:31:11, schrieb Elmar Hinz
t3el...@googlemail.com
Anyway, That doesn't bring in the missing Info.plist.
Question: Why is there no Info.plist in the source?
There is. It should be created from Info.plist.in at configure time.
That file itself is in the
Am Freitag, 26. April 2013 um 18:46:17, schrieb Elmar Hinz
t3el...@googlemail.com
I find a _debug* and a _profile* variant:
No, what you found are files, not packages.
Check please to which package belongs a specified file.
(I don't know how, sorry)
Kornel
signature.asc
Description:
Hi,
here is the command line I use (with cmake, out of source build) in a build
directory (different from LyX main directory). It works with QT installed via
the QT installer package (not from source):
cmake -DLYX_BUNDLE=ON -DLYX_COCOA=ON -DLYX_INSTALL=ON -DLYX_RELEASE=OFF
-DLYX_DEBUG=ON
here is the command line I use (with cmake, out of source build) in a build
directory (different from LyX main directory). It works with QT installed
via the QT installer package (not from source):
>
> cmake -DLYX_BUNDLE=ON -DLYX_COCOA=ON -DLYX_INSTALL=ON -DLYX_RELEASE=OFF
> -DLYX_DEBUG=ON
Summary:
* QT 4.8.4 installed via the QT installer package (not from source)
* brew install cmake
* cmake -DLYX_NLS=OFF -DLYX_BUNDLE=ON -DLYX_COCOA=ON -DLYX_INSTALL=ON
-DLYX_RELEASE=OFF -DLYX_DEBUG=ON -DLYX_EXTERNAL_LIBINTL=OFF .
* make
* make install
Errors from cmake:
CMake Error: Target LyX
Am Freitag, 26. April 2013 um 16:44:22, schrieb Elmar Hinz
> here is the command line I use (with cmake, out of source build) in a build
> directory (different from LyX main directory). It works with QT installed
> via the QT installer package (not from source):
>
> >
>
> The second one seems to be cased by the first one.
>
OK didn't follow the instruction:
make LyX2.1 (to build the binary only)
or
make package (to get a mac bundle)
Elmar
--
Elmar Hinz
Freiherr-vom-Stein-Str. 1
33014 Bad Driburg
TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m
> or prefered:
>
> b.) Install the devel package for libc6 (on ubuntu libc6-dev)
>
>
>
> > Elmar
>
> >
>
> Kornel
>
Hello,
IMHO there is no libc6 for mac. There is a
/usr/lib/libSystem.dylib -> libSystem.B.dylib
Elmar
--
Elmar Hinz
Freiherr-vom-Stein-Str. 1
33014 Bad Driburg
TYPO3 community
Am Freitag, 26. April 2013 um 18:23:56, schrieb Elmar Hinz
> Hello,
>
> IMHO there is no libc6 for mac. There is a
>
> /usr/lib/libSystem.dylib -> libSystem.B.dylib
>
> Elmar
>
Is there also a appropriate devel *package*?
Kornel
signature.asc
Description:
> OK didn't follow the instruction:
> make LyX2.1 (to build the binary only)
> or
> make package (to get a mac bundle)
>
Anyway, That doesn't bring in the missing Info.plist.
Question: Why is there no Info.plist in the source?
--
Elmar Hinz
Freiherr-vom-Stein-Str. 1
33014 Bad Driburg
TYPO3
On Fri, Apr 26, 2013 at 6:29 PM, Kornel Benko wrote:
> **
>
> Am Freitag, 26. April 2013 um 18:23:56, schrieb Elmar Hinz <
> t3el...@googlemail.com>
>
> > Hello,
>
> >
>
> > IMHO there is no libc6 for mac. There is a
>
> >
>
> > /usr/lib/libSystem.dylib -> libSystem.B.dylib
>
> >
Am Freitag, 26. April 2013 um 18:31:11, schrieb Elmar Hinz
>
> Anyway, That doesn't bring in the missing Info.plist.
>
> Question: Why is there no Info.plist in the source?
There is. It should be created from Info.plist.in at configure time.
That file itself is in the
Am Freitag, 26. April 2013 um 18:46:17, schrieb Elmar Hinz
>
> I find a _debug* and a _profile* variant:
No, what you found are files, not packages.
Check please to which package belongs a specified file.
(I don't know how, sorry)
Kornel
signature.asc
On 21/11/2011 23:40, Vincent van Ravesteijn wrote:
And won't have, as long as the core steers the gui [ 1/2 ;-) ]
Andre'
And the core will be steering the GUI as long as we can't use qt
signals in the core.
And we won't use Qt signals in the core as long as nobody makes the
effort
On 22/11/2011 22:09, Abdelrazak Younes wrote:
On 21/11/2011 23:40, Vincent van Ravesteijn wrote:
And won't have, as long as the core steers the gui [ 1/2 ;-) ]
Andre'
And the core will be steering the GUI as long as we can't use qt
signals in the core.
And we won't use Qt signals in
On Mon, Nov 21, 2011 at 12:02:15AM +0100, Lars Gullik Bjønnes wrote:
Systemcall.cpp:337:65: error: inconsistent user-defined literal suffixes
‘__FILE__’ and ‘QTOSTRING’ in string literal
Systemcall.cpp:337:65: error: unable to find user-defined string literal
operator ‘operator __FILE__’
On 21/11/2011 23:40, Vincent van Ravesteijn wrote:
>
> And won't have, as long as the core steers the gui [ 1/2 ;-) ]
>
> Andre'
And the core will be steering the GUI as long as we can't use qt
signals in the core.
And we won't use Qt signals in the core as long as nobody makes the
On 22/11/2011 22:09, Abdelrazak Younes wrote:
On 21/11/2011 23:40, Vincent van Ravesteijn wrote:
>
> And won't have, as long as the core steers the gui [ 1/2 ;-) ]
>
> Andre'
And the core will be steering the GUI as long as we can't use qt
signals in the core.
And we won't use Qt
On Mon, Nov 21, 2011 at 12:02:15AM +0100, Lars Gullik Bjønnes wrote:
> Systemcall.cpp:337:65: error: inconsistent user-defined literal suffixes
> ‘__FILE__’ and ‘QTOSTRING’ in string literal
> Systemcall.cpp:337:65: error: unable to find user-defined string literal
> operator ‘operator""
Peter Kümmel syntheti...@gmx.net writes:
| On 21.11.2011 00:02, Lars Gullik Bjønnes wrote:
This is boost warning if I am not mistaken.
I guess the boost people can trivially change this to std::unique_ptr.
Systemcall.cpp: In constructor
Peter Kümmel syntheti...@gmx.net writes:
| On 21.11.2011 00:02, Lars Gullik Bjønnes wrote:
This seems to be our own problem.
Unless it is something we inherit from Qt.
Ahh nice... it is Qt. And the wonderfull non-c++ parts of Qt.
Oh well... I'll wait half a year before repeating that test.
On Mon, Nov 21, 2011 at 10:11:11AM +0100, Lars Gullik Bjønnes wrote:
Peter Kümmel syntheti...@gmx.net writes:
| On 21.11.2011 00:02, Lars Gullik Bjønnes wrote:
This is boost warning if I am not mistaken.
I guess the boost people can trivially change this to std::unique_ptr.
On 21.11.2011 10:10, Lars Gullik Bjønnes wrote:
Peter Kümmelsyntheti...@gmx.net writes:
| On 21.11.2011 00:02, Lars Gullik Bjønnes wrote:
This seems to be our own problem.
Unless it is something we inherit from Qt.
Ahh nice... it is Qt. And the wonderfull non-c++ parts of Qt.
Oh well... I'll
On 21.11.2011 20:50, André Pönitz wrote:
On Mon, Nov 21, 2011 at 10:11:11AM +0100, Lars Gullik Bjønnes wrote:
Peter Kümmelsyntheti...@gmx.net writes:
| On 21.11.2011 00:02, Lars Gullik Bjønnes wrote:
This is boost warning if I am not mistaken.
I guess the boost people can trivially change
On Mon, Nov 21, 2011 at 10:44:04PM +0100, Peter Kümmel wrote:
On 21.11.2011 20:50, André Pönitz wrote:
On Mon, Nov 21, 2011 at 10:11:11AM +0100, Lars Gullik Bjønnes wrote:
Peter Kümmelsyntheti...@gmx.net writes:
| On 21.11.2011 00:02, Lars Gullik Bjønnes wrote:
This is boost warning if I
And won't have, as long as the core steers the gui [ 1/2 ;-) ]
Andre'
And the core will be steering the GUI as long as we can't use qt signals in
the core.
Vincent
Peter Kümmel writes:
| On 21.11.2011 00:02, Lars Gullik Bjønnes wrote:
>
>> This is boost warning if I am not mistaken.
>> I guess the boost people can trivially change this to std::unique_ptr.
>>
>> Systemcall.cpp: In constructor
>>
Peter Kümmel writes:
| On 21.11.2011 00:02, Lars Gullik Bjønnes wrote:
>> This seems to be our own problem.
>> Unless it is something we inherit from Qt.
>> Ahh nice... it is Qt. And the wonderfull non-c++ parts of Qt.
>>
>> Oh well... I'll wait half a year before repeating
On Mon, Nov 21, 2011 at 10:11:11AM +0100, Lars Gullik Bjønnes wrote:
> Peter Kümmel writes:
>
> | On 21.11.2011 00:02, Lars Gullik Bjønnes wrote:
> >
> >> This is boost warning if I am not mistaken.
> >> I guess the boost people can trivially change this to std::unique_ptr.
On 21.11.2011 10:10, Lars Gullik Bjønnes wrote:
Peter Kümmel writes:
| On 21.11.2011 00:02, Lars Gullik Bjønnes wrote:
This seems to be our own problem.
Unless it is something we inherit from Qt.
Ahh nice... it is Qt. And the wonderfull non-c++ parts of Qt.
Oh well...
On 21.11.2011 20:50, André Pönitz wrote:
On Mon, Nov 21, 2011 at 10:11:11AM +0100, Lars Gullik Bjønnes wrote:
Peter Kümmel writes:
| On 21.11.2011 00:02, Lars Gullik Bjønnes wrote:
This is boost warning if I am not mistaken.
I guess the boost people can trivially
On Mon, Nov 21, 2011 at 10:44:04PM +0100, Peter Kümmel wrote:
> On 21.11.2011 20:50, André Pönitz wrote:
> >On Mon, Nov 21, 2011 at 10:11:11AM +0100, Lars Gullik Bjønnes wrote:
> >>Peter Kümmel writes:
> >>
> >>| On 21.11.2011 00:02, Lars Gullik Bjønnes wrote:
> >>>
>
>
> And won't have, as long as the core steers the gui [ 1/2 ;-) ]
>
> Andre'
And the core will be steering the GUI as long as we can't use qt signals in
the core.
Vincent
On 21.11.2011 00:02, Lars Gullik Bjønnes wrote:
This seems to be our own problem.
Unless it is something we inherit from Qt.
Ahh nice... it is Qt. And the wonderfull non-c++ parts of Qt.
Oh well... I'll wait half a year before repeating that test. Hopefully a
new version of Qt will have been
On 21.11.2011 00:02, Lars Gullik Bjønnes wrote:
This is boost warning if I am not mistaken.
I guess the boost people can trivially change this to std::unique_ptr.
Systemcall.cpp: In constructor
‘lyx::support::SystemcallPrivate::SystemcallPrivate(const string, const
string)’:
This seems to
On 21.11.2011 00:02, Lars Gullik Bjønnes wrote:
This seems to be our own problem.
Unless it is something we inherit from Qt.
Ahh nice... it is Qt. And the wonderfull non-c++ parts of Qt.
Oh well... I'll wait half a year before repeating that test. Hopefully a
new version of Qt will have been
On 21.11.2011 00:02, Lars Gullik Bjønnes wrote:
This is boost warning if I am not mistaken.
I guess the boost people can trivially change this to std::unique_ptr.
Systemcall.cpp: In constructor
‘lyx::support::SystemcallPrivate::SystemcallPrivate(const string&, const
string&)’:
This seems to
Maybe you need
./configure --with-libiconv-prefix=/usr/local
given that you have installed libiconv?
All right, it's no bug, only my lack of knowledge. I've managed to install a
whole lot of dependecies, then compile with gmake in about 15 minutes. I
thought configure would
> Maybe you need
>
> ./configure --with-libiconv-prefix=/usr/local
>
> given that you have installed libiconv?
All right, it's no bug, only my lack of knowledge. I've managed to install a
whole lot of dependecies, then compile with gmake in about 15 minutes. I
thought configure
I'm experimenting with PC-BSD, and looks like LyX 1.6.4 won't compile.
[...]
make: don't know how to make SignalSlotPrivate_moc.cpp. Stop
Either do a make clean, autogen, autoconf or manually remove this file.
The files *_moc.cpp are auto-generated (by qt) and were renamed to
moc_*.cpp some
rainel rai...@index.hu writes:
Hello all!
I'm experimenting with PC-BSD, and looks like LyX 1.6.4 won't compile. It's a
PC-BSD 7.1.1, based on FreeBSD 7.2, 64 bit, running on a Core 2 Duo.
Configure says everything's ok, then make errors out. Here are the last few
lines of time make:
Which 'make' is that? Not GNU make, I guess. I'd be will to work on
having our make infrastructure work in these case, but I do not know how
difficult this is. Typically, for moc files we use rules like this one
%_moc.cpp: %.h
$(MOC4) -o $@ $
which creates foo.moc.cpp from foo.h.
docstream.cpp:19:19: error: iconv.h: No such file or directory
Maybe you need
./configure --with-libiconv-prefix=/usr/local
given that you have installed libiconv?
Koji
>I'm experimenting with PC-BSD, and looks like LyX 1.6.4 won't compile.
>
> [...]
>
>make: don't know how to make SignalSlotPrivate_moc.cpp. Stop
>
Either do a make clean, autogen, autoconf or manually remove this file.
The files *_moc.cpp are auto-generated (by qt) and were renamed to
"rainel" writes:
> Hello all!
>
> I'm experimenting with PC-BSD, and looks like LyX 1.6.4 won't compile. It's a
> PC-BSD 7.1.1, based on FreeBSD 7.2, 64 bit, running on a Core 2 Duo.
> Configure says everything's ok, then make errors out. Here are the last few
> lines of time
> Which 'make' is that? Not GNU make, I guess. I'd be will to work on
> having our make infrastructure work in these case, but I do not know how
> difficult this is. Typically, for moc files we use rules like this one
> %_moc.cpp: %.h
>$(MOC4) -o $@ $<
> which creates foo.moc.cpp from
> docstream.cpp:19:19: error: iconv.h: No such file or directory
Maybe you need
./configure --with-libiconv-prefix=/usr/local
given that you have installed libiconv?
Koji
On Sat, 19 Apr 2008 21:01:44 +0200
Andre Poenitz [EMAIL PROTECTED] wrote:
...
(I.e., how does it look as total lines vs. unique lines)?
I don't understand the question. Our ~500 lines .cpp files typically
yield a ~5 lines compilation unit after the preprocessor expanded
all #includes.
So bigger compilation units are better, right? Any tricks around this?
Andre, do you have the ratio for monolithic builds?
pavel
Martin Vermeer wrote:
On Sat, 19 Apr 2008 21:01:44 +0200
Andre Poenitz [EMAIL PROTECTED] wrote:
...
(I.e., how does it look as total lines vs. unique lines)?
I don't understand the question. Our ~500 lines .cpp files typically
yield a ~5 lines compilation unit after the
On Mon, Apr 21, 2008 at 11:20:17AM +0300, Martin Vermeer wrote:
On Sat, 19 Apr 2008 21:01:44 +0200
Andre Poenitz [EMAIL PROTECTED] wrote:
...
(I.e., how does it look as total lines vs. unique lines)?
I don't understand the question. Our ~500 lines .cpp files typically
yield a
On Mon, Apr 21, 2008 at 10:24:34AM +0200, Pavel Sanda wrote:
So bigger compilation units are better, right? Any tricks around this?
Andre, do you have the ratio for monolithic builds?
No. But I can create a few numbers manually... hang on.
Revision 21692: non-monolithic
Total:
On Sat, 19 Apr 2008 21:01:44 +0200
Andre Poenitz <[EMAIL PROTECTED]> wrote:
...
> > (I.e., how does it look as total lines vs. unique lines)?
>
> I don't understand the question. Our ~500 lines .cpp files typically
> yield a ~5 lines compilation unit after the preprocessor expanded
> all
> So bigger compilation units are better, right? Any tricks around this?
Andre, do you have the ratio for monolithic builds?
pavel
Martin Vermeer wrote:
On Sat, 19 Apr 2008 21:01:44 +0200
Andre Poenitz <[EMAIL PROTECTED]> wrote:
...
(I.e., how does it look as total lines vs. unique lines)?
I don't understand the question. Our ~500 lines .cpp files typically
yield a ~5 lines compilation unit after the
On Mon, Apr 21, 2008 at 11:20:17AM +0300, Martin Vermeer wrote:
> On Sat, 19 Apr 2008 21:01:44 +0200
> Andre Poenitz <[EMAIL PROTECTED]> wrote:
>
> ...
>
> > > (I.e., how does it look as total lines vs. unique lines)?
> >
> > I don't understand the question. Our ~500 lines .cpp files typically
On Mon, Apr 21, 2008 at 10:24:34AM +0200, Pavel Sanda wrote:
> > So bigger compilation units are better, right? Any tricks around this?
>
> Andre, do you have the ratio for monolithic builds?
No. But I can create a few numbers manually... hang on.
Revision 21692: non-monolithic
Total:
On Sat, Apr 19, 2008 at 09:27:31AM +0200, Andre Poenitz wrote:
Just as a side note: For the first time we have a ratio of less then
100 when comparing total compiled lines of code vs our code:
Total: compiled: 16378361 real: 164656 ratio: 99
We had about 24630737 lines half a year
Andre Poenitz wrote:
Just as a side note: For the first time we have a ratio of less then
100 when comparing total compiled lines of code vs our code:
Total: compiled: 16378361 real: 164656 ratio: 99
We had about 24630737 lines half a year ago
What was the ratio half a year ago? I
On Sat, Apr 19, 2008 at 04:22:23PM +0300, Martin Vermeer wrote:
On Sat, Apr 19, 2008 at 09:27:31AM +0200, Andre Poenitz wrote:
Just as a side note: For the first time we have a ratio of less then
100 when comparing total compiled lines of code vs our code:
Total: compiled: 16378361
On Sat, Apr 19, 2008 at 06:25:05PM +0200, Abdelrazak Younes wrote:
Andre Poenitz wrote:
Just as a side note: For the first time we have a ratio of less then
100 when comparing total compiled lines of code vs our code:
Total: compiled: 16378361 real: 164656 ratio: 99
We had about 24630737
On Sat, Apr 19, 2008 at 09:27:31AM +0200, Andre Poenitz wrote:
>
> Just as a side note: For the first time we have a ratio of less then
> 100 when comparing "total compiled lines of code" vs "our code":
>
> Total: compiled: 16378361 real: 164656 ratio: 99
>
> We had about 24630737 lines half
Andre Poenitz wrote:
Just as a side note: For the first time we have a ratio of less then
100 when comparing "total compiled lines of code" vs "our code":
Total: compiled: 16378361 real: 164656 ratio: 99
We had about 24630737 lines half a year ago
What was the ratio half a year ago?
On Sat, Apr 19, 2008 at 04:22:23PM +0300, Martin Vermeer wrote:
> On Sat, Apr 19, 2008 at 09:27:31AM +0200, Andre Poenitz wrote:
> >
> > Just as a side note: For the first time we have a ratio of less then
> > 100 when comparing "total compiled lines of code" vs "our code":
> >
> > Total:
On Sat, Apr 19, 2008 at 06:25:05PM +0200, Abdelrazak Younes wrote:
> Andre Poenitz wrote:
>> Just as a side note: For the first time we have a ratio of less then
>> 100 when comparing "total compiled lines of code" vs "our code":
>>
>> Total: compiled: 16378361 real: 164656 ratio: 99
>>
>> We
Jean-Marc Lasgouttes wrote:
Stephan == Stephan Witt [EMAIL PROTECTED] writes:
Stephan Dear JMarc, after succesfully building an 1.5.0svn checkout
Stephan on the OpenSUSE 10.2 platform I tried to build the current
Stephan 1.4.4 stable release because the distribution is shipped with
Stephan
Jean-Marc Lasgouttes wrote:
>> "Stephan" == Stephan Witt <[EMAIL PROTECTED]> writes:
>
> Stephan> Dear JMarc, after succesfully building an 1.5.0svn checkout
> Stephan> on the OpenSUSE 10.2 platform I tried to build the current
> Stephan> 1.4.4 stable release because the distribution is
I'd check that you're finding the QT3 libraries. 1.5.svn uses QT4.
Stephan Witt wrote:
Dear JMarc,
after succesfully building an 1.5.0svn checkout on the OpenSUSE 10.2
platform I tried to build the current 1.4.4 stable release because the
distribution is shipped with 1.4.2. But I failed
Stephan == Stephan Witt [EMAIL PROTECTED] writes:
Stephan Dear JMarc, after succesfully building an 1.5.0svn checkout
Stephan on the OpenSUSE 10.2 platform I tried to build the current
Stephan 1.4.4 stable release because the distribution is shipped with
Stephan 1.4.2. But I failed miserably and
1 - 100 of 338 matches
Mail list logo