Is the cs-config script (in current CVS) meant to be usable without setting the CRYSTAL environmental variable like most other *-config scripts are?
If CS is installed to the default location /usr/local, cs-config will give bogus values for some options unless the CRYSTAL variable is set to the install location. stones$ which cs-config /usr/local/bin/cs-config stones$ cs-config --prefix . stones$ cs-config --libdir ././out/linuxx86/optimize/libs stones$ CRYSTAL=/usr/local cs-config --prefix /usr/local stones$ CRYSTAL=/usr/local cs-config --libdir /usr/local/lib If CRYSTAL is not set, the for loop near the top of cs-config tries looking in two directories for Crystal Space files: the install prefix, and the current directory. But it keeps going right past the right path. The manual (http://crystalspace3d.org/docs/online/manual/cs_4.22.1.php#4.22.1) states that we only "probably" need to set CRYSTAL, and only "If you installed Crystal Space in a non-standard location." Also, in the PATH_SEPARATOR test (generated by Jam from csConfigGen1 in scripts/cs-config/Jamfile) it looks like the line that does the actual test is under-escaped. The temporary shell script that cs-config creates will never be executed. Please CC any replies to me; I am not subscribed to the list. -- Michael Kaufman [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Crystal-main mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/crystal-main Unsubscribe: mailto:[EMAIL PROTECTED]
