Andre Poenitz wrote:
> Why copies, not references?
No particular reason. I'll change that.
Jürgen
Am Tuesday 13 October 2009 schrieb Jürgen Spitzmüller:
> Kornel Benko wrote:
>
> > They are in POTFILES.in (if you use cmake).
> > That said, the rules to create POTFILES.in are in po/Rules-lyx.
> > This file will be used in autogen.sh.
>
> Let me reformulate my question: how come that Changes.cp
Kornel Benko wrote:
> It should (for now) help to simply remove the old POTFILES.in.
Yes, indeed.
Jürgen
Kornel Benko wrote:
> They are in POTFILES.in (if you use cmake).
> That said, the rules to create POTFILES.in are in po/Rules-lyx.
> This file will be used in autogen.sh.
Let me reformulate my question: how come that Changes.cpp is not listed in
POTFILES.in even after ./autogen.sh?
Jürgen
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:
--
g++
>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
Jürgen Spitzmüller writes:
> Kornel Benko wrote:
>> It should (for now) help to simply remove the old POTFILES.in.
>
> Yes, indeed.
I guess autogen.sh should do it, then. But it would change the date even
when not needed (and force a partial rebuild). Hmmm...
JMarc
"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 make:
Which 'mak
Javier Matos Odut schrieb:
If I try convert.exe in MS-DOS I get an error, Windows show a pop-up
with title "convert.exe Error in the application" with message "The
application was unable to start correctly (0xc0150002). Click OK to
close the application".
Very strange because my installer in
> 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 fo
> 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
Uwe Stöhr wrote:
Very strange because my installer includes the Imagemagick files without
any changes. It might be that the ImageMagick version that I included
has a bug that only affects a few systems like yours. (You are the first
one reporting that ImageMagick fails.)
Did you include the c
12 matches
Mail list logo
