Welcome to TalkGraphics.com
Page 1 of 8 123 ... LastLast
Results 1 to 10 of 72
  1. #1
    Join Date
    Mar 2006
    Posts
    6

    Question MacOS X building instructions

    Dear All,

    Very excited, but unable to build for OSX here:

    WX widgets built as per instructions ... but then:

    Macintosh:~ simonyoung$ ranlib /Users/simonyoung/XaraLX/libs/darwin/libCDraw.a
    ranlib: for architecture i386 object: /Users/simonyoung/XaraLX/libs/darwin/libCDraw.a(libCDrawStatic.a-i386-master.o) malformed object (unknown flavor for flavor number 0 in LC_UNIXTHREAD command 3 can't byte swap it)

    ... any help gratefully received.

    Kind regards,

    Simon
    IP

  2. #2

    Default Re: MacOS X building instructions

    Could you report your Mac OS version and XCode version.

    At the moment, to complete the build using standard methods entails quite extreme restrictions on the versions that work.

    There was a similar message last month, videlicet:
    http://www.xaraxtreme.org/maillists/.../msg00150.html

    Could I trouble you to review the Build Instructions page at
    http://www.xaraxtreme.org/developers...tructions.html

    I am not saying that that page will solve the problem for you (though it might), but it would be helpful to hear of any imperfections and or omissions within it, that relate to your efforts.

    When you do get Mac Xara LX running, it would be appreciated if you could check
    Bug 935 "APPLICATION CLOSE".

    Ben
    IP

  3. #3
    Join Date
    Mar 2006
    Posts
    6

    Default Re: MacOS X building instructions

    Dear Ben,

    Thank you for your help; version of Xcode upgraded to 2.2.1 solved the ranlib problem.


    Proceeding to XaraLX unfortuately generates errors at the autoreconf command. Please see below:

    System: Mac OS X 10.4.6 18.GHz PowerPC G5
    Xcode: 2.2.1

    packages:
    Macintosh:~/XaraLX simonyoung$ sudo fink list pkgconfig automake autoconf libpng libjpeg
    Information about 2065 packages read in 1 seconds.
    autoconf 2.13-5 System for generating configure scripts, ...
    (i) autoconf2.5 2.59-7 System for generating configure scripts
    autoconf2.54 2.54-4 System for generating configure scripts
    automake1.4 1.4-5 Tool for generating GNU Standards-complia...
    automake1.5 1.5-6 Tool for generating GNU Standards-complia...
    automake1.6 1.6.3-6 Tool for generating GNU Standards-complia...
    automake1.7 1.7.6-6 Tool for generating GNU Standards-complia...
    automake1.8 1.8.5-3 Tool for generating GNU Standards-complia...
    (i) automake1.9 1.9.4-2 Tool for generating GNU Standards-complia...
    p automaken [virtual package]
    i libjpeg 6b-16 JPEG image format handling library
    i libjpeg-bin 6b-16 Executables for libjpeg package
    i libjpeg-shlibs 6b-16 Shared libraries for libjpeg package
    libpng-shlibs 1.0.12-7 PNG image format handling library (old ve...
    i libpng3 1:1.2.8-1 PNG image format handling library
    i libpng3-shlibs 1:1.2.8-1 Shared libraries for libpng3 package
    i pkgconfig 0.15.0-2 Manager for library compile/link flags


    executing autoreconf:

    Macintosh:~/XaraLX simonyoung$ pwd
    /Users/simonyoung/XaraLX
    Macintosh:~/XaraLX simonyoung$ autoreconf -f -i -s
    /sw/share/aclocal/pkg.m4:5: warning: underquoted definition of PKG_CHECK_MODULES
    run info '(automake)Extending aclocal'
    or see http://sources.redhat.com/automake/a...ending-aclocal
    /sw/share/aclocal/gtk.m4:7: warning: underquoted definition of AM_PATH_GTK
    aclocal:configure.in:9: warning: macro `AM_BINRELOC' not found in library
    /sw/share/aclocal/pkg.m4:5: warning: underquoted definition of PKG_CHECK_MODULES
    run info '(automake)Extending aclocal'
    or see http://sources.redhat.com/automake/a...ending-aclocal
    /sw/share/aclocal/gtk.m4:7: warning: underquoted definition of AM_PATH_GTK
    aclocal:configure.in:9: warning: macro `AM_BINRELOC' not found in library
    Macintosh:~/XaraLX simonyoung$


    Help gratefully received.

    Kind regards,

    Simon
    IP

  4. #4

    Default Re: MacOS X building instructions

    You can ignore the warnings, I think that they are outside of our control and indicate that the m4 macros used by the folks who who built GTK et cetera were using an older version of m4 or autotools.

    The AM_BINRELOC probably means that there is a package missing on from your setup, which we need but have not specified as being needed. I'll look into it.

    Ben
    IP

  5. #5

    Default Re: MacOS X building instructions

    Do you have a file called binreloc.m4 in your XaraLX directory?
    IP

  6. #6

    Default Re: MacOS X building instructions

    For the avoidance of doubt, and again, I am not suggesting this is a part of getting the solution to this problem (though it might be), could you state which version of the GNU gettest tools you have, and if you wish, whether there have been any problems running autopoint.

    Ben
    IP

  7. #7
    Join Date
    Mar 2006
    Posts
    6

    Default Re: MacOS X building instructions

    Quote Originally Posted by BPFowler
    You can ignore the warnings, I think that they are outside of our control and indicate that the m4 macros used by the folks who who built GTK et cetera were using an older version of m4 or autotools.

    The AM_BINRELOC probably means that there is a package missing on from your setup, which we need but have not specified as being needed. I'll look into it.

    Ben
    OK, try 1; no joy - then make clean, etc a good start. Then compilation halts with:

    [snip a lot]In file included from pngfiltr.h:104, from pngfiltr.cpp:106:
    outptpng.h:109:17: error: png.h: No such file or directory
    outptpng.h:166: error: 'png_structp' does not name a type
    outptpng.h:167: error: 'png_infop' does not name a type
    pngutil.h:151: error: 'png_colorp' has not been declared
    make[2]: *** [pngfiltr.o] Error 1
    make[1]: *** [all] Error 2
    make: *** [all-recursive] Error 1
    Macintosh:~/XaraLX simonyoung$
    IP

  8. #8
    Join Date
    Mar 2006
    Posts
    6

    Default Re: MacOS X building instructions

    Quote Originally Posted by BPFowler
    Do you have a file called binreloc.m4 in your XaraLX directory?
    Yes
    IP

  9. #9
    Join Date
    Mar 2006
    Posts
    6

    Default Re: MacOS X building instructions

    Quote Originally Posted by BPFowler
    For the avoidance of doubt, and again, I am not suggesting this is a part of getting the solution to this problem (though it might be), could you state which version of the GNU gettest tools you have, and if you wish, whether there have been any problems running autopoint.

    Ben
    Ben, I'm not sure if you mean gettext or gettest. Of the latter I can find no evidence so I'm going to assume the former (please accept my appologies in advance of being a silly newbie) ...

    flagged status name installed version binary category summary
    NO current gettext 0.10.40-19 0.10.40-19 0.10.40-19 base Message localization support
    NO current gettext-bin 0.10.40-19 0.10.40-19 0.10.40-19 base Executables for gettext package
    NO current gettext-dev 0.10.40-19 0.10.40-19 0.10.40-19 base Developer files for gettext package
    NO current gettext-tools 0.10.40-19 0.10.40-19 0.10.40-19 base Developer executables for gettext package


    I'm afraid that being a newbie I will not have encountered autopoint problems; is there something you would like me to run to test?

    Kind regards,

    Simon
    IP

  10. #10

    Default Re: MacOS X building instructions

    This is the same problem that Pekele had, videlicet,
    http://www.talkgraphics.com/showpost...9&postcount=16

    This has been discussed on the mailing list: there are several ways of getting the png headers for your compilation, but unfortunately all of them have some disadvantages or will cause problems down the line.

    Apple actually provide the libraries as part of the Core Foundation, and if I knew where the corresponding headers were, we could use those.

    I suspect that Xara LX will need to provide its own png library (just as it provides its own wxWidgets library), and whilst this means a little more work at this stage, you could certainly do this now. (The instructions will probably be amended to contain this advice).

    Otherwise, you could add the fink include directory as above, which is the quickest way past this obstacle (and is what I do still)!

    Ben
    IP

 

 

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •