Gem automatically loads a path? (was Re: How to declare custom libraries in abstractions)
2018-04-14 17:39 GMT-03:00 IOhannes m zmölnig zmoelnig@iem.at:
Gem is special, as it adds its own path to Pd's search path and the user shouldn't manually do that.
Hi, how can I test this and check it? I was doing this on my own but it seems I just got confused.
Can I test it in Pd Vanilla with one of the libraries available in deken? Can I test it with Pd Extended? And how exactly?
thanks
On 2018-04-20 05:54, Alexandre Torres Porres wrote:
2018-04-14 17:39 GMT-03:00 IOhannes m zmölnig zmoelnig@iem.at:
Gem is special, as it adds its own path to Pd's search path and the user shouldn't manually do that.
Hi, how can I test this and check it? I was doing this on my own but it seems I just got confused.
- remove all (Gem-related) paths and libs from your startup settings (or
start Pd with "-noprefs".
- instantiate one of Gem's abstractions, e.g. [hsv2rgb] -- it should fail
- load the Gem library (e.g. "-lib Gem" or [declare -lib Gem])
- instantiate one of Gem's abstractions, e.g. [hsv2rgb] -- it should
instantiate.
fgmasdr IOhannes
hi, thanks for the answer, but this still doesn't work for me
I'm running Pd 0.48-1-i386 on a macOS 10.12.6, I installed Gem 0.93-3 from deken. I can load Gem objects just fine, but no hsv2rgb, only if I do something like [Gem/hsv2rgb].
My path is clear, and my externals are in ~/Documents/Pd/externals
Gem also doesn't show up as path after using declare.
cheers
2018-04-20 3:40 GMT-03:00 IOhannes m zmoelnig zmoelnig@iem.at:
On 2018-04-20 05:54, Alexandre Torres Porres wrote:
2018-04-14 17:39 GMT-03:00 IOhannes m zmölnig zmoelnig@iem.at:
Gem is special, as it adds its own path to Pd's search path and the user shouldn't manually do that.
Hi, how can I test this and check it? I was doing this on my own but it seems I just got confused.
- remove all (Gem-related) paths and libs from your startup settings (or
start Pd with "-noprefs".
- instantiate one of Gem's abstractions, e.g. [hsv2rgb] -- it should fail
- load the Gem library (e.g. "-lib Gem" or [declare -lib Gem])
- instantiate one of Gem's abstractions, e.g. [hsv2rgb] -- it should
instantiate.
fgmasdr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
I can load [hsv2rgb] in Pd Extended 0.42-5, but it actually load markex/hsv2rgb instead, which is a compiled object, not an abstraction - these are the loaded objects in the help file of gem/hsv2rgb by the way, so that was very confusing, making me believing you could "lock" an abstraction somehow with Gem, leading me to question on how can one do that in that other thread...
Anyway, all I tried here, with Extended and new Vanilla, didn't really work, but I see there's code in Gem 0.93-3 that tries to do that, and also that currently Gem uses a different approach from https://github.com/pure-data/pure-data/commit/c917dd1938e8b48927dc6414916bdc...
I tested the "new way" with cyclone and it kinda works, despite the consistency error. So maybe you mean about a new version of Gem that wasn't released yet, and that you'd have to compile yourself?
Anyway, I'm really confused and curious to know if this is being done, if there's a bug, whatever's going on.
cheers
2018-04-20 3:50 GMT-03:00 Alexandre Torres Porres porres@gmail.com:
hi, thanks for the answer, but this still doesn't work for me
I'm running Pd 0.48-1-i386 on a macOS 10.12.6, I installed Gem 0.93-3 from deken. I can load Gem objects just fine, but no hsv2rgb, only if I do something like [Gem/hsv2rgb].
My path is clear, and my externals are in ~/Documents/Pd/externals
Gem also doesn't show up as path after using declare.
cheers
2018-04-20 3:40 GMT-03:00 IOhannes m zmoelnig zmoelnig@iem.at:
On 2018-04-20 05:54, Alexandre Torres Porres wrote:
2018-04-14 17:39 GMT-03:00 IOhannes m zmölnig zmoelnig@iem.at:
Gem is special, as it adds its own path to Pd's search path and the
user
shouldn't manually do that.
Hi, how can I test this and check it? I was doing this on my own but it seems I just got confused.
- remove all (Gem-related) paths and libs from your startup settings (or
start Pd with "-noprefs".
- instantiate one of Gem's abstractions, e.g. [hsv2rgb] -- it should fail
- load the Gem library (e.g. "-lib Gem" or [declare -lib Gem])
- instantiate one of Gem's abstractions, e.g. [hsv2rgb] -- it should
instantiate.
fgmasdr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/li stinfo/pd-list
2018-04-20 4:06 GMT-03:00 Alexandre Torres Porres porres@gmail.com:
I tested the "new way" with cyclone and it kinda works, despite the consistency error.
yeah, to avoid the error, the path just needs to start with a "+" character. I learned that after I opened an issue about it here https://github.com/pure-data/pure-data/issues/351 - which I guess I can close as there's nothing too weird about all this, but i'd like an answer why the "+" is needed.
So, anyway, if the thing about Gem comes from this new code, I already figured it out and am including it in Cyclone, so we're good. I'm just curious if this was supposed to be working on old Pd extended and with the Gem available in deken.
cheers
-
Alexandre Torres Porres -
IOhannes m zmoelnig