Eric Sunshine schrieb:
On Oct 5, 2007, at 7:00 AM, Pablo Martin wrote:
Lukas Erlinghagen wrote:
Pablo Martin schrieb:
res wrote:
On 04.10.2007 19:58, Pablo Martin wrote:
3.: pysimp can't load the cspace module. I changed
cspython.cpp to add
scripts/python/frozen to pythonpath in addition to scripts/
python.
However, I'm not sure whether this should be done
unconditionally.
scripts/python/frozen should not be added to pythonpath (unless
msvc
builds the python dlls there, but it shouldnt afaik, that dir
is only
intended for frozen files for users without swig). the dlls
should be in
DEFAULT_PYTHMOD_PATH. Maybe you can tell me where you have the
module
specific dlls? (note i have no idea about how msvc build works).
Hm, note that on MSVC the frozen files aren't automatically
copied to
the location the python modules are in ...
wouldn't there be a way to make this happen?
How about putting the frozen files into scripts/python itself
instead of
a subfolder? At least, that is where the frozen monolithic
cspace.py was
located.
Thats not a good idea, as then there is problems with pythonpath
having
half the cspace package in different folders (makes it really
difficult
I prefer everyone having the
modules in the same location (out/xxx/xxx/bindings/python/) and having
one standard way of using them (wether people is using swig, or
not, or
msvc).
It should presumably be possible to invoke the MSVC "copy" action to
copy the frozen files from the source directory into the 'out'
directory. This would require some addition to the msvcgen template
(probably), but it seems reasonable.
The problem here, as I see it, is that MSVC places the final output
files into the main CS directory, so the out/.../bindings folder doesn't
get created at all.
Anyway, adding $CRYSTAL/scripts/python/frozen to the $PYTHONPATH
variable seems to work fine here (WinXP, MSVC) without requiring any
changes to the code. Maybe this should be the recommended option for
MSVC users who want to work with the python bindings.
And one minor observation about pysimp.py: the currrent code causes only
the floor to be lit. The attached patch enables the shadow receiving
flag for the room's mesh so it is lit as expected.
Greetings,
Lukas E.
Index: pysimp.py
===================================================================
--- pysimp.py (revision 27861)
+++ pysimp.py (working copy)
@@ -32,6 +32,8 @@
walls = GeneralMeshBuilder.CreateFactoryAndMesh (engine, room,
"walls", "walls_factory", box)
+ walls_state = SCF_QUERY_INTERFACE(walls.GetMeshObject (),
iGeneralMeshState)
+ walls_state.SetShadowReceiving(True)
walls_factory = walls.GetMeshObject().GetFactory()
material = engine.GetMaterialList().FindByName(matname)
walls.GetMeshObject().SetMaterialWrapper(material)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Crystal-main mailing list
Crystal-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/crystal-main
Unsubscribe: mailto:[EMAIL PROTECTED]
