Dualbooting NeXTSTEP and OpenStep
J. Daniel Ashton
I'm wondering about setting up a NeXTSTEP/Intel 3.x (1? 3?) partition
beside my existing OpenStep 4.2 partition for purposes of compiling
code that can run on the earlier systems.
Will this work? What are the issues of concern?
Or is there a better way to provide code for the 3.x community?
--
J. Daniel Ashton ICQ# 9445142 mailto:jdas...@southern.edu
http://www.southern.edu/~jdashton mailto:jdas...@us.ibm.com
PGP key available send NeXTmail --> mailto:jdas...@bellsouth.net
Chuck Swiger
> I'm wondering about setting up a NeXTSTEP/Intel 3.x (1? 3?) partition
> beside my existing OpenStep 4.2 partition for purposes of compiling
> code that can run on the earlier systems.
>
> Will this work? What are the issues of concern?
> Or is there a better way to provide code for the 3.x community?
You'll want to use seperate hard drives. You can't configure multiple
NEXTSTEP filesystem partitions into the FDISK partition table. You can
configure multiple BSD slices within an FDISK partition, but it's easier to
use seperate physical devices.
-Chuck
Charles Swiger | ch...@codefab.com | Bad cop! No Donut.
---------------+-------------------+--------------------
I know you are an optimist if you think I'm a pessimist.
H.-R. Oberhage
: [...]
: Will this work? What are the issues of concern?
As Charles (Chuck) Swiger already said, you'd either need separate
drives (just one filesystem-type per drive is (automatically)
recognized) or, with two (or) more partitions on the same drive, you
would have to fiddle with the partition id-bytes, so that only one
looks like NS/OS at any one time and the others are 'hidden' (I don't
recommend this, though!)
: Or is there a better way to provide code for the 3.x community?
There are ways (also described in the FAQ???) to install two "development
environments" (NS3.3 and OS4.2) under OS 4.2; it is a bit tricky, but
if iirc, several people use it. Maybe one of them can further enlighten
you :-).
Greetings,
Ruediger Oberhage
--
H.-R. Oberhage
Mail: Univ.-GH Essen E-Mail: phy...@sp2.power.Uni-Essen.DE
Fachbereich 7 (Physik) rued...@Theo-Phys.Uni-Essen.DE
S05 V07 E88
Universitaetsstrasse 5 Phone: (+49) 201 / 183-2493
D-45117 Essen, Germany FAX: (+49) 201 / 183-2120
-bat.
> : Or is there a better way to provide code for the 3.x community?
>
> There are ways (also described in the FAQ???) to install two "development
> environments" (NS3.3 and OS4.2) under OS 4.2; it is a bit tricky, but
> if iirc, several people use it. Maybe one of them can further enlighten
> you :-).
I just out a copy of the 3.3 development enviornment from the CD into a
separate directory and use the following shell script (that I
call cc3) to compile with instead of cc. Works fine for me. I
got this off the net somewhere - the soyrce eludes me at present,
though the authors name is in the header comments.
-bat.
#! /bin/sh
#+++
# title: cc3
# abstract: Run NEXTSTEP 3.x compiler from OPENSTEP 4.x.
# author: Tom Hageman <t...@basil.icce.rug.nl>
# created: September 1996
# modified:
# copyleft:
#
# Copyright (C) 1996 Tom R. Hageman.
#
# This is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This software is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this software; see the file COPYING. If not, write to
# the Free Software Foundation, 59 Temple Place - Suite 330,
# Boston, MA 02111-1307, USA.
#
# description:
#
# This script should allow you to compile pre-OPENSTEP source code on
# an OPENSTEP system, assuming a NS3.3 developer system is mounted
# somewhere.
#
# Note that you get a lot of warnings when you use this script with the
# original 3.3 precompiled headers. To remedy this you can either add
# the -traditional-cpp option (but this can be slow), or re-precompile
# the 3.3 headers using this script. (you must probably be root to
# be allowed to do that).
#
# usage:
#
# Put this script anywhere in your execution path.
#
# From ProjectBuilder (presumably the 3.x version) set:
#
# CC=cc3
#
# in Arguments:, either in Builder [Options...] panel,
# or (just once) in PBs Preferences panel.
#
# From the commandline:
#
# make CC=cc3 ...
#
# bugs:
#
# Indubitably.
#---
### start of configuration section ###
## Where to find NS3.x developer.
ns3dev="/NextStep_33"
## Where to find NS3.x /LocalDeveloper directory.
ns3dev_LocalDeveloper="$ns3dev/LocalDeveloper"
#ns3dev_LocalDeveloper="/LocalDeveloper"
## Where to find NS3.x /usr/local directory.
ns3dev_usr_local="$ns3dev/usr/local"
#ns3dev_usr_local="/usr/local"
## Which compiler version to use.
# (You lose the ability to compile for hppa if you choose the 4.x compiler.
# OTOH you use a more recent version of the compiler tools if you do so.)
#CC="$ns3dev/bin/cc -B$ns3dev/lib/" # Use NS 3.x compiler
CC="/bin/cc -static" # Use OS 4.x compiler
### end of configuration section ###
CPLUSINCLUDES=
case " $* " in
*\ -ObjC++\ * | *\ -x\ c++\ * | *\ -x\ objective-c++\ * | \
*.C\ * | *.M\ * | *.cc\ * | *.cxx\ * )
CPLUSINCLUDES="-I $ns3dev/NextDeveloper/Headers/g++"
esac
exec $CC -nostdinc ${1+"$@"} \
-L$ns3dev/usr/lib \
-L$ns3dev/usr/local/lib \
-L$ns3dev/lib \
$CPLUSINCLUDES \
-I $ns3dev_usr_local/include \
-I $ns3dev/NextDeveloper/Headers \
-I $ns3dev/NextDeveloper/Headers/ansi \
-I $ns3dev/NextDeveloper/Headers/bsd \
-I $ns3dev_LocalDeveloper/Headers \
-I $ns3dev_LocalDeveloper/Headers/ansi \
-I $ns3dev_LocalDeveloper/Headers/bsd \
-I $ns3dev/NextDeveloper/2.0CompatibleHeaders
Detlev Droege
> phy...@power.uni-essen.de (H.-R. Oberhage) writes:
> > : Or is there a better way to provide code for the 3.x community?
> >
> > There are ways (also described in the FAQ???) to install two "development
> > environments" (NS3.3 and OS4.2) under OS 4.2; it is a bit tricky, but
> > if iirc, several people use it. Maybe one of them can further enlighten
> > you :-).
>
> I just out a copy of the 3.3 development enviornment from the CD into a
> separate directory and use the following shell script (that I
> call cc3) to compile with instead of cc. Works fine for me.
While this "cc3" Script provides you with a working Nextstep 3.3 cc,
you might also have need to use the NS 3.3 InterfaceBuilder etc.
In this case, you need a more complex setup. Christian Starkjohann
wrote it for a 3.3 <-> 4.0 environment. I modified it slightly and
adopted it for 3.3 <-> 4.2, it seems to work fine for me. I can
switch between the development environments using the commands
develop 3.3
and
develop 4.2
which gives me access to the full range of specific tools including
ProjectBuilder and InterfaceBuilder for each of the versions.
Since I don't want to put too much code into this news article
(although it is just some kilobytes) you can find the stuff at
ftp://ftphost.uni-koblenz.de/outgoing/People/droege/setup-dual-dev.tar.gz
Read the README and all comments in the files carefully before using !
Detlev
--
Detlev Droege, Universitaet Koblenz, FB Informatik | Fon:+49 261 287-2769
Rheinau 1, D-56075 Koblenz, Germany | Fax:+49 261 287-2745
[NeXT/MIME-Mail ok] | Email: det...@gmx.de