scratch team mailing list archive

[Bert Freudenberg <bert@xxxxxxxxxxxxxxx>]

Ah right, the vm-* plugins might have some tighter integration with the VM than regular plugins.

But it should still work to just copy all needed vm header files to a directory and compile the plugin's source to a shared library. And since this would be specific to a single Linux distro, it wouldn't even need fancy makefile magic, you could just hard-code all the arguments.

I have not actually done this myself for a vm-* plugin, but it shouldn't be much harder than this:

http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html#AEN95

- Bert -

On 17.02.2010, at 15:25, John Maloney wrote:
> 
> Hi, Bert.
> 
> Re: Actually, you would just need some Squeak VM header files to build the plugin.
> 
> I know this is the case in theory, and I've built other plugins that way. But I've never quite figured out how to build a VM plugin like the vm-sound-pulse plugin without using the entire VM source tree. Do you happen to know what header files we'd need and what commands we'd use to compile it? I know all that info is there somewhere in the make system for the VM, but it's not obvious and I've never had the patience to dig it out.
> 
> 	-- John
> 
> On Feb 16, 2010, at 3:54 PM, Bert Freudenberg wrote:
> 
>> On 16.02.2010, at 18:42, Amos Blanton wrote:
>>> Hi All -
>>> 
>>> Derek and I talked a bit about this on another thread.
>>> I removed the source for the pulse plugin because it doesn't really get built as part of the packaging process (that would require us to have an environment setup in which we could build the squeak-vm).
>> 
>> Actually, you would just need some Squeak VM header files to build the plugin. Those could be included in a source package. Plugins are designed to work with different VM versions so this should be fine.
>> 
>> The better way would still be to make the plugin be part of the VM proper, but this could be an interim solution.
>> 
>> - Bert -
>> 
>> 
>> 
>