Open Motif pkg for Darwin

This forum is read only. No new submissions are accepted.

Questions about motif? Contact us

4 posts / 0 new
Last post
Open Motif pkg for Darwin

Submitted by Anonymous on Sat, 01/24/2004 - 20:05. General Questions
Hi there,

It used to be possible to download a Darwin pkg file of OM 2.2.2 from motifzone.net, but the site just contains Linux stuff now. How come?

Martin

Anonymous

I would also like to know why there is no longer a Darwin pkg. Even if the old version were still available that would be better than nothing.
I have tried (and failed) to compile on Mac OSX from source.
If anyone knows where to get a pre-compiled version for OSX I would be grateful.
Peter.

Mark

OM 2.2.2 is known to have a problem compiling on Darwin. But the Fink distro has resolved this problem. You should be able to get an RPM there.

If you have a chance to download the OM 2.2.3 beta and build it on MacOS that would be great! We've integrated the Fink changes into OM 2.2.2, but do not have independent verification that it builds on MacOS.

Anonymous

Mark wrote:
OM 2.2.2 is known to have a problem compiling on Darwin. But the Fink distro has resolved this problem. You should be able to get an RPM there.
I've never had much luck with Fink's X11 libraries (as a replacement for Apple's).

Mark wrote:
If you have a chance to download the OM 2.2.3 beta and build it on MacOS that would be great! We've integrated the Fink changes into OM 2.2.2, but do not have independent verification that it builds on MacOS.
I did that and it built using the following script:

mkdir openmotif2.2.3
cd openmotif2.2.3
tar zxf ../openmotif2.2.3.tar.gz
ln -s /usr/bin/glibtool libtool
autogen.sh
make

There are a couple of nasties:
1) autogen.sh prints a few messages that look like errors, but it doesn't seem to matter :-/
2) The machine already has OM 2.2.2 installed in /usr/local so there is a slight chance that the build relied on that.

Anyway, periodic ran using the 2.2.3 shared library so I think the build is OK.

It doesn't actually solve my problem though, because users of my existing binary need libXm.2.dylib. Thank you at least for changing the library name to libXm.4.dylib in OM 2.2.3 so we don't get accidental binary incompatibility problems :-)

Martin