Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!wuarchive!udel!haven!decuac!pa.dec.com!may.pa.dec.com!may
From: may@may.pa.dec.com (G. May Yip)
Newsgroups: comp.windows.x.motif
Subject: Making Motif applications MORE Portable
Summary: Determining which Motif files an application needs.
Message-ID: <1990Dec6.022449.23322@pa.dec.com>
Date: 6 Dec 90 02:24:49 GMT
Sender: news@pa.dec.com (News)
Reply-To: may@may.pa.dec.com (G. May Yip)
Followup-To: comp.windows.x.motif
Organization: "I speak for myself and no one else."
Lines: 25

Hello!
I'd like to have our application program - which is huge byself but
doesn't use a large part of the Motif library - be capable of being
ported onto many hardware platforms AS EASILY & QUICKLY AS POSSIBLE. 
I'm planning to identify just what files in the Motif source directory
the application needs, compile them, and then link them to the
application, without having to compile the whole Motif library, which
will take a lot of effort if I'm to have to do it for various many
architectures.

Does this sound reasonable?  I've looked at Motif source before but I'm
not certain that I can easily find the "minimal subset" needed.  Did
anyone try this before?  Any experience you can share with me?  Any
comment, general or specific? Any criticism, or encouragement?   Thanks
a lot in advance.

Aside: I understand that this is a short-sighted solution for a
short-sighted problem.  I'm not concerned with future development of the
application in the  Motif environment yet.  The biggest immediate
concern is to get it running on different machines, given some time and
resource constraints.  And I figure sooner or later there'll be
compiled, bug-free Motif libraries everywhere :-) that are done by
people who're good at porting Motif.

/may