<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 2, 2014 at 1:33 PM, gettimothy <span dir="ltr"><<a href="mailto:gettimothy@zoho.com" target="_blank">gettimothy@zoho.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br><u></u><div><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></div></div></blockquote> <br><div>My guess on hacking it would be on the class side of VMMaker under the accessing protocol: coreVMDirName, machinesDirName, etc...</div></div></div></blockquote><div><br></div><div><br>
</div><div>Hi tty,</div><div><br></div><div>That's surprising. I would have thought that loading plugins would be a platform-specific operation. I didn't think to look at VMMaker. Surely that's about generating plugin code, and not loading shared libraries?</div>
<div><br></div><div>On the other hand, I *did* fix filenames. I'll have to track down the author of that comment. :-)</div><div><br></div><div>Thanks!</div><div><br></div><div>Colin</div></div><br></div></div>