<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style='font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;'>Hi Colin,<br><br><div>>I've been working on a custom build of Cog (rev 2886) on Linux. I notice that the VM always looks for plugins in the same directory as the VM binary, and thus we need a wrapper script to set SQUEAK_PLUGINS and LD_LIBRARY_PATH correctly. </div> <div>>I'd like to do away with the wrapper script in my specific case, since I know in advance where everything will be installed. Is there a way to specify the plugin directory at compile time?<br></div> <div><br></div><br><br>At the bottom of the class comment of VMMaker is a discussion of plugins.<br><br>In there is this little snippet:<br><br><br><blockquote style="border: 1px solid rgb(204, 204, 204); padding: 7px; background-color: rgb(245, 245, 245);"><div>Known problems:-<br>a) since Squeak has really poor filename handling, you can't simply change the directory names to '/foo/bar/myEvilCodeBase' and expect it to work. You fix file names and I'll fix VMMaker :-)<br><div id="1"></div></div></blockquote> <br><div id="1">My guess on hacking it would be on the class side of VMMaker under the accessing protocol: coreVMDirName, machinesDirName, etc...<br><br><br>That's just conjecture on my part.<br><br>cheers.<br><br>tty<br></div></div></body></html>