|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Thu, 29 Dec 1994 18:06:31 +0200 From: Lars Wirzenius <wirzeniu@cc.helsinki.fi> To: linux-activists@niksula.hut.fi, linux-announce@vger.rutgers.edu X-Mn-Key: announce From: Wolfram Gloger <wmglo@Dent.MED.Uni-Muenchen.DE> Subject: Linux a.out DLL support for Khoros 2.0.1 DR Keywords: Khoros, Linux, DLL, shared library, image processing Newsgroups: comp.os.linux.announce Organization: ? Approved: linux-announce@tc.cornell.edu (Lars Wirzenius) Followup-to: comp.os.linux.misc =============================================================== Linux shared libraries for the Khoros 2.0.1 development release =============================================================== Wolfram Gloger (wmglo@dent.med.uni-muenchen.de) Dec 1994 INTRODUCTION The image processing system Khoros 2.0.1 is now available for ftp as a 'developers release' (sources only) from ftp.khoros.unm.edu (and other sites, see comp.soft-sys.khoros for announcements). It will compile without changes on Linux, but there are surely bugs remaining in the libraries and applications. If you want to get a stable and reasonably complete package, I would still recommend Khoros 1.0.5. 'K2' offers some very promising new features - e.g. it has a nice GUI builder and a 3D renderer - but it is still under development. Just to give you a short hint on what kind of a package I am talking about, you will need at least 100MB of disk space and 16MB of RAM to work effectively with K2. There are so many features and applications that I couldn't possibly test them all. If you experience a crash and you are not sure it is due to the Linux DLL support (i.e. my bad porting), report it to khoros-bugs@khoros.unm.edu, too. I would recommend the following strategy: Compile a complete set of binaries with the DLLs (optimization turned on), and a set of static libraries with debug info (yes, these are huge). When you hit a problem you can quickly relink the program in question statically and try to debug. I have added support for Linux shared libraries for the 'bootstrap', 'data services' and 'design' toolboxes in K2.0.1. Adding jump files etc. for the other toolboxes seems like a waste of time to me, since the saving in binary disk usage would be minimal. Also I expect the ELF support in Linux to be rolling when the next release of K2 is happening. CHANGES COMPARED TO THE PREVIOUS VERSION I had to edit the jump.* DLL config files for new symbols and to remove no-longer existent ones. In doing so I most probably broke backward compatibility with the 2.0.0 libraries. If you think this is too tough then please stick with 2.0.0 or explain to me why you can't recompile. WHAT AND WHERE TO GET - COPYRIGHT ISSUES khoros2.0.1-linux.tar.gz at sunsite.unc.edu:pub/Linux/incoming (now) pub/Linux/X11/xapps (later) tsx-11.mit.edu:pub/Linux/ports (hopefully soon) ftp.khoros.unm.edu:pub/khoros/contrib/ports (maybe) ftp.e20.physik.tu-muenchen.de:pub/K2 (probably soon) ftp.lrz-muenchen.de:/local/khoros/khoros-2.0/khoros-2.0/contrib/ports (probably soon) Khoros 2.0 comes with its own license. My patches are copyrighted and freely distributable according to the GNU public license. In particular, I assume no responsibility of any kind as to the functionality of K2 compiled with these patches. HOW TO APPLY THE PATCH To create Linux DLLs, please get and install DLL tools 2.16, e.g. from tsx-11.mit.edu:pub/linux/packages/GCC/src/tools-2.16.tar.gz. First unpack Khoros as described in the 'release/install' file found on K2 ftp servers. Unpack khoros2.0.1-linux.tar.gz, e.g. in the K2 home directory. This will create a 'linux' directory. Before running bin/installit, go to the Khoros 2.0.1 home directory and apply the patch with: % KHOROS_HOME=/your/path/to/K2; export KHOROS_HOME % cd $KHOROS_HOME % patch -p0 < .../linux/patch.Linux % tar xvf .../linux/jump.tar Then, as described in the K2 docs, % PATH=$KHOROS_HOME:$PATH % installit should compile the bootstrap toolbox, which is really the base of the system. For the other toolboxes and their installation, see the K2 docs. Good luck with Khoros, Wolfram. P.S. I forgot to mention that I am still using XFree86 2.1.1. But I think you should have little trouble compiling with 3.1; except there may be some problems with K2 relying on pre-X11R6 features. But I don't know about any. -- Send submissions for comp.os.linux.announce to: linux-announce@news.ornl.gov PLEASE remember Keywords: and a short description of the software.
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |