TheCloud/panda3d
1
0
Fork 0
mirror of https://github.com/panda3d/panda3d.git synced 2025-10-03 10:22:45 -04:00
Code Issues Packages Projects Releases Wiki Activity

*** empty log message ***

Browse Source
This commit is contained in:
cxgeorge 2002-02-03 02:12:08 +00:00
parent 45bfcc5d60
commit 9d331953fe
2 changed files with 81 additions and 81 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

81
panda/src/doc/howto.install_panda_on_windows
View File

@ -9,28 +9,19 @@ of the world, see INSTALL.txt in this directory.
To install Panda3D on WinNT/Win2000/Win98:
To install Panda3D on WinXP/Win2000/WinNT
-------------------------------------
Notes:
Lines preceeded by ">" are instructions to be typed on the command line.
On WinNT, make sure your system clock is not set to GMT (only worry about
this if your makedepend seems out of sync, i.e. you constantly reinstall
old files over more current ones).
Opengl appears to be installed with the os for both WinNT and Win98, but I
read somewhere that we might want to do our own version control for
this eventually using "VerInstallFile" to install our own version of
OpenGl.
"Touch" doesn't quite work properly on WinNT or Win98 currently.
Make sure you run ftp in "binary" mode to fetch tarballs.
"ftp" doesn't currently read "backspace" in rxvt, so you'll just have to be
precise at the ftp prompt for now ("delete" doesn't work either).
If this really bugs you, you can create a shortcut on the Desktop to
"tcsh.exe" and run ftp properly from there rather than from rxvt.
Occasionally, a freshly opened shell will hang in the middle of
attaching or something. This appears to be a race condition in
cshrc that appears only on multiprocessor machines. If this
happens, go ahead and kill the tcsh process (or ftp or rxvt
process) using the Task Manager and try again.
Make sure your machine has enough disk space - I'd start with the largest
open space on any of your partitions.
Make sure your machine has networking (IP, gateway, etc.) so you can use
@ -46,7 +37,7 @@ Step 1: Install Visual C++ (v6.0)
- Run V:\msvc-6.0\setup.exe, or install from CD.
For a faster install, select custom install and uncheck everything
but Visual C++, Data Access, ActiveX, and Tools
- On WinNT, you will be prompted to register environment variables for
- On WinNT/XP/2000, you will be prompted to register environment variables for
running the compiler from the command line - do it.
- Install MSVC Service Pack 5 by running V:\msvc-sp5\setupsp5.exe, or from CD
You may need to run v:\msvc-sp5\mdac_typ.exe first (setup will tell you if so)
@ -56,35 +47,64 @@ Step 1: Install Visual C++ (v6.0)
Index, VC++, Platform SDK, Knowledge Base, and All Other Files.
Step 2: Install MS Platform SDK to get updated VC libs and headers
- Install MS Platform SDK MSDN CD in default location.
- Install MS Platform SDK in default location.
- Run v:\platform-sdk\setup.exe to install the Feb 2001 Platform SDK.
(there may be problems with other versions of the Platform SDK)
This should prepend the Platform SDK paths to your PATH,INCLUDE, and
LIB dirs. Building libpandadx requires this step (needs DX7 headers/libs)
(there may be problems with other newer versions of the Platform SDK)
This should prepend the Platform SDK paths to your PATH,INCLUDE,
and LIB dirs. Building libpandadx requires this step (needs DX7
headers/libs)
Step 3: Install Cygwin (v1.0)
- Install Cygwin by running V:\cygwin-1.0\setup.exe, or from CD
Step 3: Install Cygwin (v1.3.5 or above should work)
- Install Cygwin by running V:\cygwin-1.3.5\setup.exe, and selecting
'install from local directory' (or go to cygwin.com and run setup.exe
from the link there to install the latest version from the internet).
Be careful to make sure that packages such as CVS, perl, bison,
etc. which are required to build PANDA are selected for installation.
Alternatively, you can install the latest Cygwin off the Internet from
http://cygwin.com.
- Open up a shell by running (and, if you desire, creating a shortcut to)
tcsh.exe in:
C:/Cygwin/contrib/bin
C:/Cygwin/bin
Known Problems with tcsh:
tcsh v6.09.00: (cygwin 1.0) long paths result in 'Word too long' errors
tcsh v6.10.00 (cygwin 1.3.3) uppercase filename executables not found on
path, so build fails (cant find 'CL.EXE')
tcsh v6.11.00 (cygwin 1.3.6) TAB filename completion sometimes fails
v6.09 and v6.11 should be stored on V:\cygwin-1.3.5, you can copy them
to c:\cygwin\bin if you want to use them
Alternately, you can run a bash shell by going to the "Start"
button at the bottom left of your screen, selecting "Programs",
"Cygwin" and "bash". You can then run "tcsh" at the bash prompt to make
things easier.
- Set up the Cygwin environment:
- all of the commands below have been collected in V:\win\install\wintools\etc\setup_env.csh. cd V:\win\install\wintools\etc, run tcsh, and
do 'source setup_env.csh' to do all of the below automatically
- Check for directories /bin /etc /tmp /usr and create them using
mkdir if they don't exist.
- Make the following directories:
> mkdir /c /f /g /h /i /j /v
> mkdir /msvc98 /mscommon /mspsdk
> mkdir /usr/local
> mkdir /usr/local/bin
> mkdir /usr/local/etc
> mkdir /msvc98 /mscommon /mspsdk /msvc7 /intel /ia32
> mkdir /usr/local /usr/local/bin /usr/local/etc
- Rename any cygwin-installed python.exe (if it exists) to avoid conflicts with required VRSTUDIO-compiled python,
which is custom-built to load sitecustomize.py and setup PYTHONPATH for our panda environment
> mv /bin/python.exe /bin/python-cygwin.exe
- Create some links expected by the attach scripts:
> ln -s /contrib/bin/tcsh /bin/csh
> ln -s /contrib/bin/perl /usr/local/bin/perl
> ln -s /bin/tcsh /bin/csh
> ln -s /bin/perl /usr/local/bin/perl
> ln -s /bin/bash /usr/local/bin/bash
- Connect the network drives:
Note that any of your drive letters are already in use, you
simply do a 'net use' to a different drive letter, then
change the 'mount' command to point the official '/[drivelet]' dir
at the real drive letter it's mounted to. It is not necessary
for /v to point to the v: drive.
> net use f: "\\nufat\fat" /persistent:yes
> net use g: "\\nufat\bit" /persistent:yes
> net use h: "\\dimbo\usr2" /persistent:yes
@ -103,6 +123,14 @@ Step 3: Install Cygwin (v1.0)
> mount -s C:/Program\ Files/Microsoft\ Visual\ Studio/VC98 /msvc98
> mount -s C:/Program\ Files/Microsoft\ Visual\ Studio/Common /mscommon
> mount -s C:/Program\ Files/Microsoft\ Platform\ Sdk /mspsdk
If VC7 is installed:
> mount -s C:/Program\ Files/Microsoft\ Visual\ Studio .NET/Vc7 /msvc7
If Intel C++ is installed:
> mount -s C:/Program\ Files/Intel /intel
> mount -s C:/Program\ Files/Intel/Compiler60/IA32 /ia32
- These are optional, but handy
> mkdir /fat
> mkdir /bit
@ -140,7 +168,7 @@ Step 4: Create your home directory
to use "edit.exe" in order to generate the correct "newline"
character (^M).
- Note: We've seen a problem where we can't source ~/.cshrc if the home
directory /usr/<yourname> does not match the user name exactly.
directory /usr/<yourname> does not match the user name %USERNAME% windows env var.
To be safe, be sure and name your home directory to be /usr/<yourname>.
- Copy important startup files into your home directory:
> cd /v/win/install/wintools/panda
@ -207,7 +235,8 @@ Step 8: (Optional) Build $PANDA
a texture on it, you'll need to be in $PANDA/src/all/testbed/ when
you run "demo".
Step 9: Install Emacs
Step 9: Install Emacs
(note: this emacs does not use Cygwin paths, "/" represents the real root not "C:\Cygwin".)
- get the tarball from /for/program/tarballs/emacs-20.7-fullbin-i386.tar.gz
- untar/install (This will install emacs into C:/emacs-20.7,
do not attempt to install it under a directory containing a space,

81
panda/src/doc/howto.install_panda_on_windows.cyg-1.3.2 → panda/src/doc/howto.install_panda_on_windows.cygwin-1.0
View File

@ -9,19 +9,28 @@ of the world, see INSTALL.txt in this directory.
To install Panda3D on WinXP/Win2000/WinNT
To install Panda3D on WinNT/Win2000/Win98:
-------------------------------------
Notes:
Lines preceeded by ">" are instructions to be typed on the command line.
On WinNT, make sure your system clock is not set to GMT (only worry about
this if your makedepend seems out of sync, i.e. you constantly reinstall
old files over more current ones).
Opengl appears to be installed with the os for both WinNT and Win98, but I
read somewhere that we might want to do our own version control for
this eventually using "VerInstallFile" to install our own version of
OpenGl.
"Touch" doesn't quite work properly on WinNT or Win98 currently.
Make sure you run ftp in "binary" mode to fetch tarballs.
"ftp" doesn't currently read "backspace" in rxvt, so you'll just have to be
precise at the ftp prompt for now ("delete" doesn't work either).
If this really bugs you, you can create a shortcut on the Desktop to
"tcsh.exe" and run ftp properly from there rather than from rxvt.
Occasionally, a freshly opened shell will hang in the middle of
attaching or something. This appears to be a race condition in
cshrc that appears only on multiprocessor machines. If this
happens, go ahead and kill the tcsh process (or ftp or rxvt
process) using the Task Manager and try again.
Make sure your machine has enough disk space - I'd start with the largest
open space on any of your partitions.
Make sure your machine has networking (IP, gateway, etc.) so you can use
@ -37,7 +46,7 @@ Step 1: Install Visual C++ (v6.0)
- Run V:\msvc-6.0\setup.exe, or install from CD.
For a faster install, select custom install and uncheck everything
but Visual C++, Data Access, ActiveX, and Tools
- On WinNT/XP/2000, you will be prompted to register environment variables for
- On WinNT, you will be prompted to register environment variables for
running the compiler from the command line - do it.
- Install MSVC Service Pack 5 by running V:\msvc-sp5\setupsp5.exe, or from CD
You may need to run v:\msvc-sp5\mdac_typ.exe first (setup will tell you if so)
@ -47,64 +56,35 @@ Step 1: Install Visual C++ (v6.0)
Index, VC++, Platform SDK, Knowledge Base, and All Other Files.
Step 2: Install MS Platform SDK to get updated VC libs and headers
- Install MS Platform SDK in default location.
- Install MS Platform SDK MSDN CD in default location.
- Run v:\platform-sdk\setup.exe to install the Feb 2001 Platform SDK.
(there may be problems with other newer versions of the Platform SDK)
This should prepend the Platform SDK paths to your PATH,INCLUDE,
and LIB dirs. Building libpandadx requires this step (needs DX7
headers/libs)
(there may be problems with other versions of the Platform SDK)
This should prepend the Platform SDK paths to your PATH,INCLUDE, and
LIB dirs. Building libpandadx requires this step (needs DX7 headers/libs)
Step 3: Install Cygwin (v1.3.5 or above should work)
- Install Cygwin by running V:\cygwin-1.3.5\setup.exe, and selecting
'install from local directory' (or go to cygwin.com and run setup.exe
from the link there to install the latest version from the internet).
Be careful to make sure that packages such as CVS, perl, bison,
etc. which are required to build PANDA are selected for installation.
Alternatively, you can install the latest Cygwin off the Internet from
http://cygwin.com.
Step 3: Install Cygwin (v1.0)
- Install Cygwin by running V:\cygwin-1.0\setup.exe, or from CD
- Open up a shell by running (and, if you desire, creating a shortcut to)
tcsh.exe in:
C:/Cygwin/bin
Known Problems with tcsh:
tcsh v6.09.00: (cygwin 1.0) long paths result in 'Word too long' errors
tcsh v6.10.00 (cygwin 1.3.3) uppercase filename executables not found on
path, so build fails (cant find 'CL.EXE')
tcsh v6.11.00 (cygwin 1.3.6) TAB filename completion sometimes fails
v6.09 and v6.11 should be stored on V:\cygwin-1.3.5, you can copy them
to c:\cygwin\bin if you want to use them
C:/Cygwin/contrib/bin
Alternately, you can run a bash shell by going to the "Start"
button at the bottom left of your screen, selecting "Programs",
"Cygwin" and "bash". You can then run "tcsh" at the bash prompt to make
things easier.
- Set up the Cygwin environment:
- all of the commands below have been collected in V:\win\install\wintools\etc\setup_env.csh. cd V:\win\install\wintools\etc, run tcsh, and
do 'source setup_env.csh' to do all of the below automatically
- Check for directories /bin /etc /tmp /usr and create them using
mkdir if they don't exist.
- Make the following directories:
> mkdir /c /f /g /h /i /j /v
> mkdir /msvc98 /mscommon /mspsdk /msvc7 /intel /ia32
> mkdir /usr/local /usr/local/bin /usr/local/etc
- Rename any cygwin-installed python.exe (if it exists) to avoid conflicts with required VRSTUDIO-compiled python,
which is custom-built to load sitecustomize.py and setup PYTHONPATH for our panda environment
> mv /bin/python.exe /bin/python-cygwin.exe
> mkdir /msvc98 /mscommon /mspsdk
> mkdir /usr/local
> mkdir /usr/local/bin
> mkdir /usr/local/etc
- Create some links expected by the attach scripts:
> ln -s /bin/tcsh /bin/csh
> ln -s /bin/perl /usr/local/bin/perl
> ln -s /contrib/bin/tcsh /bin/csh
> ln -s /contrib/bin/perl /usr/local/bin/perl
> ln -s /bin/bash /usr/local/bin/bash
- Connect the network drives:
Note that any of your drive letters are already in use, you
simply do a 'net use' to a different drive letter, then
change the 'mount' command to point the official '/[drivelet]' dir
at the real drive letter it's mounted to. It is not necessary
for /v to point to the v: drive.
> net use f: "\\nufat\fat" /persistent:yes
> net use g: "\\nufat\bit" /persistent:yes
> net use h: "\\dimbo\usr2" /persistent:yes
@ -123,14 +103,6 @@ do 'source setup_env.csh' to do all of the below automatically
> mount -s C:/Program\ Files/Microsoft\ Visual\ Studio/VC98 /msvc98
> mount -s C:/Program\ Files/Microsoft\ Visual\ Studio/Common /mscommon
> mount -s C:/Program\ Files/Microsoft\ Platform\ Sdk /mspsdk
If VC7 is installed:
> mount -s C:/Program\ Files/Microsoft\ Visual\ Studio .NET/Vc7 /msvc7
If Intel C++ is installed:
> mount -s C:/Program\ Files/Intel /intel
> mount -s C:/Program\ Files/Intel/Compiler60/IA32 /ia32
- These are optional, but handy
> mkdir /fat
> mkdir /bit
@ -168,7 +140,7 @@ Step 4: Create your home directory
to use "edit.exe" in order to generate the correct "newline"
character (^M).
- Note: We've seen a problem where we can't source ~/.cshrc if the home
directory /usr/<yourname> does not match the user name %USERNAME% windows env var.
directory /usr/<yourname> does not match the user name exactly.
To be safe, be sure and name your home directory to be /usr/<yourname>.
- Copy important startup files into your home directory:
> cd /v/win/install/wintools/panda
@ -235,8 +207,7 @@ Step 8: (Optional) Build $PANDA
a texture on it, you'll need to be in $PANDA/src/all/testbed/ when
you run "demo".
Step 9: Install Emacs
(note: this emacs does not use Cygwin paths, "/" represents the real root not "C:\Cygwin".)
Step 9: Install Emacs
- get the tarball from /for/program/tarballs/emacs-20.7-fullbin-i386.tar.gz
- untar/install (This will install emacs into C:/emacs-20.7,
do not attempt to install it under a directory containing a space,