-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
expose lilv_free() with features, for windows compatibility #14
Comments
I was too quick. A plugin does not link against liblilv and cannot call lilv_free() directly. A plugin receives abstract_path(), absolute_path() via the LV2_State_Map_Path |
@x42 I've updated this on current master, and it seems fine as far as the (relatively limited) tests go. Did you have a specific motivating case it would be good to check before merging this stuff? |
All state restore methods that use |
I don't have a setup at the moment that can build stuff outside lv2kit and friends on Windows. Let me rephrase: is there a specific motivating case you would like to check before this stuff gets merged? :) |
API-wise, as is so often the case, I really regret LV2 not having the ability to just jam stuff on the end of structs, getting a feature for this is pretty annoying, but... given reality, this seems fine to me. |
What is the envisaged way to test at compile-time if |
I didn't think about that. The LV2 version I guess? |
You could also just keep the fallback ifdeffed out as you did there I suppose. |
is the URI guarenteed to be a
might work |
Same as anything else, really. I guess having an LV2_VERSION declared in the header would be handy, but it's annoying to have generated stuff in the headers, and that's what build systems are for... Anyway, I guess I can stick this stuff on master and it can get hammered out a bit in practice in Ardour before release since IIRC you aren't using releases anyway. |
I will do that for a while, at least until debian/stable picked up new LV2 headers. As far as I'm concerned, this issue can be closed. Thanks! |
This fixes a memory-leak issue for Windows builds. see also lv2/lilv#14
This fixes a memory-leak issue for Windows builds. see also lv2/lilv#14
This fixes a memory-leak issue for Windows builds. see also lv2/lilv#14
Addressed in ac562ca |
This fixes a memory-leak issue for Windows builds. see also lv2/lilv#14
This should fix problems on windows: - lv2/lilv#14 Signed-off-by: Stefan Westerfeld <[email protected]>
Various functions e.g.
abstract_path()
make the caller responsible for freeing the returned value with free().On Windows this is not an option. Memory allocated by a library must be free()ed by that library/module
The text was updated successfully, but these errors were encountered: