|
From: <de...@us...> - 2003-03-21 18:48:28
|
Update of /cvsroot/csp/APPLICATIONS/SimData
In directory sc8-pr-cvs1:/tmp/cvs-serv15456
Modified Files:
README CHANGES.current
Log Message:
no message
Index: README
===================================================================
RCS file: /cvsroot/csp/APPLICATIONS/SimData/README,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** README 20 Mar 2003 00:24:47 -0000 1.4
--- README 21 Mar 2003 18:23:16 -0000 1.5
***************
*** 75,78 ****
--- 75,122 ----
TESTING
+ As a quick test, change to the Source directory and run Python.
+ Try typing "import SimData". You should see a line similar to
+ "loaded @ 0x4883012". If not, something went wrong... post to
+ the CSP developer's forum and we can try to find the problem.
+
+
+ USING SIMDATA WITH CSPSIM
+
+ The new CSP application called CSPSim relies on SimData in
+ two ways. First, libSimData.a is statically linked to make
+ the CSPSim executable. Second, the simulation data for CSPSim
+ needs to be compiled from XML source files to a binary data
+ archive using the data compiler application included with
+ SimData. This Python program is found in the directory
+ Tools/DataCompiler. Once you have built your CSPSim executable,
+ go to Tools/DataCompiler and run Compiler.py (from a command
+ prompt on windows you would probably need to type something like
+ "python Compiler.py"). If the Compiler can't find CSPSim
+ initially, it will prompt you to enter a path to CSPSim. This
+ path is saved in a file named .csp_path so you shouldn't have
+ to do this more than once. The Compiler will then print a
+ usage message and exit. To compile the data for CSPSim, you
+ must specify the top level data directory to archive, and the
+ name of the output archive. Given the standard location of
+ the files in CVS, you would type:
+
+ ./Compiler.py ../../../CSPSim/Data/Sim ../../../CSPSim/Data/Sim.dar
+
+ This will parse all the XML files under CSPSim/Data/Sim and create
+ the binary archive (named Sim.dar) needed to run CSPSim. A
+ script named "make_simdar" that runs the above command is provided
+ for your convienience. This must be rerun whenever you modify
+ the XML data files to incorporate the changes into Sim.dar.
+
+
+ BUILDING on Windows with msvc++6(sp5), stlport-4.5.3 (hints)
+
+ 1) Install python2.2 and swig 1.3.17
+ 2) Add python path to your global path
+ 3) Load SimDataMSVC.dsw
+ 4) Build it in release mode; in process, it should create a new file
+ called cSimData_wrap.cpp (this file name should already be in
+ project/Source) from cSimData.i which is parsed by swig.
+ 5) Testing procedure is same as above:
As a quick test, change to the Source directory and run Python. Try
typing "import SimData". You should see a line similar to "loaded @
***************
*** 87,90 ****
--- 131,147 ----
available.
+ ----------
+
+ 2003-03-20: Edited - work on progress. On windows, you have to
+ do:
+
+ > python setup.py make_install_win
+
+ It will install files and folders in python directory (better to be
+ power user or admin for that on xp).
+
+ ----------
+
+
Under Linux, depending on which method you used to build SimData, do
either:
***************
*** 107,111 ****
#include <SimData/Types.h>
-
-
-
--- 164,165 ----
Index: CHANGES.current
===================================================================
RCS file: /cvsroot/csp/APPLICATIONS/SimData/CHANGES.current,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** CHANGES.current 20 Mar 2003 17:53:37 -0000 1.6
--- CHANGES.current 21 Mar 2003 18:23:17 -0000 1.7
***************
*** 1,8 ****
Version 0.3.1 (in progress)
===========================
2003-03-20: onsight
Fixed const cast in matrix * vector routines. Why doesn't
gcc 3.2.1 -Wall catch this? (!)
!
Changed cSimData.i in Source to include the main version in
Include/SimData. These differ in their %module directive.
--- 1,12 ----
Version 0.3.1 (in progress)
===========================
+
+ 2003-03-20: delta
+ Fixes for msvc.
+
2003-03-20: onsight
Fixed const cast in matrix * vector routines. Why doesn't
gcc 3.2.1 -Wall catch this? (!)
!
Changed cSimData.i in Source to include the main version in
Include/SimData. These differ in their %module directive.
***************
*** 42,45 ****
--- 46,56 ----
Fixes for building with MS VC.Net
+ Changes to hash stuff to make it compile with native stl .net
+ Restructured some header files
+
+ Added .net project
+
+ Added a test on using stlport with msvc <= 6.0 in hash_map.h
+
2003-03-16: onsight
Created a new setup.py script to allow SimData to be build and
***************
*** 101,105 ****
Big simplification of the various smart pointer types.
PathPointer<T> is gone; now just use Pointer<T> for all object
! references. PathPointerBase is not PointerBase, and what was
originally PointerBase is now ReferencedPointer (although you
shouldn't need to use these classed directly).
--- 112,116 ----
Big simplification of the various smart pointer types.
PathPointer<T> is gone; now just use Pointer<T> for all object
! references. PathPointerBase is now PointerBase, and what was
originally PointerBase is now ReferencedPointer (although you
shouldn't need to use these classed directly).
|