Similar to Brew's shellenv, this would simply output commands to set environment variables useful for Soar development:
SOAR_HOME
PATH
C++: libSoar path goes in (DY(LDLIBRARY))PATH
Python: add SOAR_HOME to PYTHONPATH
Java: perhaps set SOAR_JAVA_CLASSPATH and SOAR_JAVA_LIB_PATH and let the user decide how to use them (-Djava.library.path=$SOAR_JAVA_LIB_PATH, -cp SOAR_JAVA_CLASSPATH when running java)
This would allow someone to setup a Soar environment in a shell with eval "$(/path/to/soar shellenv)" (or whatever the Windows equivalent is). This would simplify switching between Soar versions (particularly when testing releases, or for developing Soar while also using the last major release for other Soar applications). This could also be used to simplify all of the app startup scripts that we ship (Eaters, TankSoar, SoarCLI, Debugger).
Similar to Brew's shellenv, this would simply output commands to set environment variables useful for Soar development:
java)This would allow someone to setup a Soar environment in a shell with
eval "$(/path/to/soar shellenv)"(or whatever the Windows equivalent is). This would simplify switching between Soar versions (particularly when testing releases, or for developing Soar while also using the last major release for other Soar applications). This could also be used to simplify all of the app startup scripts that we ship (Eaters, TankSoar, SoarCLI, Debugger).