Am 19.09.2010 um 03:33 schrieb BH:

> On Mon, Sep 6, 2010 at 7:56 AM, Stephan Witt <st.w...@gmx.net> wrote:
>> Am 06.09.2010 um 13:46 schrieb BH:
>> 
> 
> I tried this out with a new Mac, and it works well. I did not compile
> aspell or test Tiger or 64-bit support.
> 

Thanks for your comments.

> A couple of minor comments, with my numbering following that of 
> INSTALL.MacOSX:
> 
> PREREQUISITES
> 
> 1. Can Qt be installed from Nokia's .dmg, or must it be self-compiled?
> I followed the instructions to compile it myself, and it worked with
> no problems, but if that's not necessary, it might be worth making it
> clearer.

Yes, you're right. I'll check and add that - if LyX can be compiled with 
Nokia's .dmg.
I think it's the case - but I want to be sure. So, I'll test it.

> 2. The version of automake macports installed is 2.67, which
> autogen.sh rejected. (It wants only automake < 2.65.) So I had to edit
> autogen.sh to allow 2.67, which worked fine.

Do you mean *autoconf* 2.67?
That one I didn't notice since I have an older version.
Didn't update macports a while.

We should test that on Linux and change autogen.sh if it works.
Pavel, what do you think?

> 
> BUILD INSTRUCTIONS
> 
> 1. Environment
> 
> (a) ... "We have to change that with if on that build system". Should
> this be: "We have to change that if not on that build system"?

I'm not sure about the grammar... I meant

"We have to change the default if using that build system."

> That's it. Nice job with the clear documentation ... and nice work on
> LyX/Mac quite generally. It's coming along great!

Thanks.


Am 19.09.2010 um 06:26 schrieb Jens Nöckel:

> 
> On Sep 18, 2010, at 6:33 PM, BH wrote:
>> 
>> That's it. Nice job with the clear documentation ... and nice work on
>> LyX/Mac quite generally. It's coming along great!
> 
> Hi Bennett,
> I agree the INSTALL.MacOSX is now much more comprehensive and useful!
> I had to make some adjustments though, because I compiled on a machine where 
> I use fink instead of MacPorts (our newest Mac uses MacPorts, but I'm not 
> compiling LyX on that one... just to make life more interesting). 

This configuration I don't have. Nice to get some feedback from you.

> So in my case, here is a summary of the steps, assuming you have autoconf, 
> gettext and pkgconfig from fink:
> 
> 1)
> Compile qt-everywhere-opensource-src-4.6.3 (universal without Tiger) as in 
> step 1 of INSTALL.MacOSX. The download location for the source is 
> ftp://ftp.qt.nokia.com/qt/source/ (which may be a little hard to find if 
> you're following the link given in INSTALL.MacOSX)

I'll add that link.

> 2)
> Then to build LyX from SVN, download the source using 
> svn co svn://svn.lyx.org/lyx/lyx-devel/trunk lyx-devel

I'm not sure if I'd like to mention that.
If one is able to read INSTALL.MacOSX it is somehow done - and may very well be 
a tarball download instead.

> Set I the following flags (assuming bash syntax): 
> export CFLAGS="-arch i386"
> export CXXFLAGS="-arch i386"
> export OBJCFLAGS="-arch i386"
> export LDFLAGS="-framework Carbon -framework AppKit -arch i386" 
> This differs from INSTALL.MacOSX because my version of pkgconfig wasn't 
> clever enough to detect the framework dependencies automatically.

My current version of INSTALL.MacOSX mentions here:
export LDFLAGS="$LDFLAGS -framework ApplicationServices -framework Cocoa 
-framework AppKit"

I've learned it from pkgconfig guesses for Qt4.
So, you're saying "-framework ApplicationServices" is not needed?
I'll remove it from INSTALL.MacOSX then...

> Next, in the lyx-devel directory, I did:
> ./autogen.sh
> ./configure --with-version-suffix=-2.0 --disable-stdlib-debug 
> --prefix=PATH/TO/LyX.app --with-qt4-dir=/path/to/QT4 
> --with-libiconv-prefix=/usr
> make
> make install-strip
> 
> The libiconv prefix needed to be specified on the configure line to avoid 
> loading an older version of that library installed by fink.

This is a good idea.
The --with-libiconv-prefix=/usr option should be used in any case. I had 
problems with the macports version, too.
I'll add that.

> That's how things worked for me.

Thank you for the feedback.

Stephan

Reply via email to