Harry,

I'm following your updated instructions but still having trouble
getting libpano13 to compile for i386. I've rebuilt my entire
port library with the +universal variant turned on and
universal_archs set to "x86_64 i386", which all went smoothly.
However, when I try to follow this step in the updated wiki...

$ export CFLAGS="-I/opt/local/include -L/opt/local/lib"
$ ./bootstrap --with-jpeg=/opt/local/ --with-tiff=/opt/local/ --with-
png=/opt/local/ --without-java
$ ./configure
Snow Leopard: If you are on Snow Leopard you have to do an extra
step.
Open the "libtool" file with an editor and change all occurrences of
"-dynamiclib" to "-dynamiclib -arch i386" (4 occurrences).

...I have a few problems. First, it's still the case that bootstrap
seems to run
configure for me and if I try to run it manually afterward I get:

"checking for PNG support ...
configure: cannot find the png directory, assuming it is specified in
CFLAGS
checking png.h usability... no
checking png.h presence... no
checking for png.h... no
checking for png_get_io_ptr in -lpng... no
checking if PNG package is complete... no
configure: error:
        the png library must be installed on your system
        but configure could not find it."

So I'm not doing the "configure" step apart from "bootstrap."

Next, when I edit "libtool" I find only two instances of "dynamiclib"
to
edit, not four as you suggest. I also notice that after running "make"
my changes to "libtool" are gone (the references to "-arch i386").
It seems that make is wiping out my changed libtool and recreating
one that doesn't have the "-arch i386" changes.

Finally, I do a "make install" then a lipo in /usr/local/lib/
libpano13.dylib
and it's been build as an x86_64 lib. I.e.
$ lipo -info libpano13.dylib
Non-fat file: libpano13.dylib is architecture: x86_64

Am I missing something? How can I get an i386 compatible
version of libpano13.dylib?

Thanks,

Darrell

On Sep 5, 12:03 pm, Harry van der Wolf <[email protected]> wrote:
> Hi Darrel,
>
> 2010/9/5 T. Modes <[email protected]>
>
>
>
> > > My "wx" libs are in /opt/local/lib/wx-devel because I couldn't get
> > > anything working with wxWidgets @2.8.11 due to arch problems
> > > (there's a thread in this forum on this). wx-devel installed just
> > > fine. Here's the lipo on my installed version:
>
> > > dmac:wx-devel dstyner$ lipo -info /opt/local/lib/wx-devel/
> > > libwx_*.dylib
> > > Non-fat file: /opt/local/lib/wx-devel/libwx_osx_cocoau-2.9.0.0.0.dylib
> > > is architecture: x86_64
> > > Non-fat file: /opt/local/lib/wx-devel/libwx_osx_cocoau-2.9.0.dylib is
> > > architecture: x86_64
> > > Non-fat file: /opt/local/lib/wx-devel/libwx_osx_cocoau-2.9.dylib is
> > > architecture: x86_64
> > </snip>
>
> > Hugin does not (yet) work with wxWidgets 2.9. In this (development)
> > version there are some fundamental changes, which are incompatible
> > with the current version (2.8). If there is a stable version (aka 3.0)
> > then we will make the necessary change to hugin. Until then please use
> > 2.8.x
>
> > Thomas
>
>  You are here in an awkward position. All your libraries are compiled as
> x86_64 including your wxmac 2.9.
> Macports currently used wxmac 2.8.11. wxmac 2.8.11 can only be compiled as
> 32bit on mac. That's where your problems obviously came from.
> That's also exactly why I asked the "lipo -info" question, but I assumed all
> your libs were x86_64 and your wxmac (and I assumed the macports 2.8.11)
> would be i386. That would also cause problems.
> As Thomas points out the 2.9.x version can't be used yet with Hugin.
>
> So my suggestion is (and I did the same since I'm since a number of weeks on
> Snow Leopard as well and had to do some analyzing myself):
>
> - edit your "/opt/local/etc/macports/macports.conf" and set
> "universal_archs"  to "x86_64 i386" (off course without the double quotes).
>
> - recompile your macport libs and binaries as universal. This will allow you
> to use all your libs as x86_64 and as i386 for Hugin.
>
> - Use the wxmac 2.8.11 from macports. macports 2.8.11 will automatically be
> compiled as i386 only (set in the Portfile).
>
> - Do NOT use the macports libpano as it is too old (2.9.14). Recompile your
> current svn libpano as well. Note: libpano doesn't compile correctly as i386
> on an x86_64 platform. After the "./configure --without-java" step edit the
> "libtool" file and change all occurrences of "-dynamiclib"  to "-dynamiclib
> -arch i386" (4 occurrences). Then do a make and (sudo) make install. This
> will install your libpano as i386 (Check with "lipo -info").
>
> - rebuild Hugin, but before the cmake step do a:
> export CFLAGS="-arch i386 -I/opt/local/include -L/opt/local/lib"
> export CXXFLAGS="-arch i386 -I/opt/local/include -L/opt/local/lib"
> export LDFLAGS="-L/opt/local/lib -L/usr/local/lib"
>
> Then do the cmake ..; make; (sudo) make install
>
> Note: I will adapt the wiki as soon as possible, but I just didn't find the
> time yet.
> Note2: I have been working on a number of macports to upgrade them, being
> enblend/enfuse, autopano-sift-C, libpano, some dependencies and hugin
> itself. I will release my final hugin macports patch as soon as the 2010.2.0
> has been released. The other ports have not yet been "committed" to stable
> macports by the macports team. After 2010.2.0 release I will start pushing
> them (the macports team that is). Then it will be possible to build Hugin
> 2010.2.0 directly from macports.
>
> Harry

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Reply via email to