jchoi@ics.uci.edu (John Choi) (07/03/90)
Okay, first some questions and then possibly some answers.
Questions:
1. Does anyone know how to make shared libraries? The manual
makes mention of how to use existing shared libraries, but
how can I create a new one?
2. Can 'atom' be used to convert a.out executables complied on
a Sun3 into Mach-O objects?
3. Has anyone compiled X11R4 libraries on the NeXT?
The reason I ask these questions is that I compiled the X11R4 libraries
on the NeXT last weekend. I even compiled a few X programs with the
new libraries (xterm,xclock,xedit, etc.) and ran them with the R3 XNeXT
server. Guess what? They worked. But, (there's always a but) the
X programs are extremely large (400-600K). Xclipboard.R4 on the Sun is
only 32K and XTerm is 188K. The NeXT versions were 467K and 520K,
respectively. I'm guessing it might be because I didn't use shared
libraries. Is this reasonable? Is there something I'm missing?
Possible answers to previously posted XNeXT questions:
1. imake -
a. try removing all the null comments (/**/); these
seem to make the cpp insert spaces and other garbarge.
b. manually hack the resultant Makefile; usually all that's
necessary is "cc -O -bsd ..." It helps to have all the
headers and libraries in the standard locations.
c. sometimes -O causes problems; ommit as necessary.
2. why XNeXT doesn't run xterm or show cursor -
a. it can't find the necessary fonts and/or bitmaps.
b. did you run Xinstall?
Summary:
I think this question of how to create shared libraries is one
which might be easily answered by someone who knows (NeXT employee?).
Please respond to the net. Thanks.doug@dept.csci.unt.edu (Douglas Scott) (07/03/90)
I didnt want to quote a lot from the original article--I just wanted to say that I was able to compile XR4 complete without a single error on my NeXT, without any modifications other than a small set of patches that I got from someone at UC Berkeley. These patches create a new NeXT.cf file, change some things in mit/utils/scripts, and one or two other things. After applying the patch, make World did its thing, uninterrupted. Imake and whatever cpp the make decided to use all worked fine. If this magic patch is not already out there, I will compress and uuencode it and post it in comp.sources.x. I know of at least two versions of the neccessary patches, because they were sent to me when I asked for them some months ago. I too am very interested in shared libraries on the NeXT if it is possible! -- ___________________________________________________________________________ Douglas Scott doug@dept.csci.unt.edu