Hi all,

i have a question about the configuration context, when i run my CS project (debug build and started with --verbose) i get the following:

SCF_NOTIFY: scanning plugin directory: D:\build\mywork\CPP\CS\BsApplication\msvc-cs-1.4\Debug (context `app'; recursive no)
When i'm using the CRYSTAL_PLUGIN environment variable to load my plugins from my /plugins directory i also get:
SCF_NOTIFY: scanning plugin directory: D:\build\mywork\CPP\CS\BsApplication\msvc-cs-1.4\Debug (context `app'; recursive no)
SCF_NOTIFY: scanning plugin directory: D:\build\mywork\CPP\CS\BsApplication\msvc-cs-1.4\Debug\plugins (context `crystalspace'; recursive no)
SCF_NOTIFY: registering plugin D:\build\mywork\CPP\CS\BsApplication\msvc-cs-1.4\Debug\plugins\glwin32.dll in context `crystalspace'
...
etc
etc
...
When i have the CRYSTAL_SPACE env. variable set i get the following:

SCF_NOTIFY: scanning plugin directory: D:\build\mywork\CPP\CS\svn\branches\1.4 (context `{none}'; recursive no)

What are the different context types for ? Does it makes any difference in which context the plugins are loaded ? And if what's the difference ? Can i change this behavious somehow so i don't have a 'crystalspace' context -- so only one context for my application is there (if this makes sense at all).


ps: The "User Guide" is starting to get usefull -- http://www.byteshelter.org/wiki/CS_UserGuide/doku.php?id=introduction (the link is also on the crystalspace3d.org wiki)


greetings,
Steven Truppe
------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
Crystal-main mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/crystal-main
Unsubscribe: 
mailto:[email protected]?subject=unsubscribe

Reply via email to