Let's wait to see if we ever get a bug report about that. AFAICT Pd-l2ork
loads what needs to be loaded-- "susceptible to" isn't a good reason to awaken
the makefile monster.
-Jonathan
On Tuesday, April 5, 2016 11:38 AM, Ivica Ico Bukvic <i...@vt.edu> wrote:
Another thought could be having hexloader be folded into core pd... It is
currently autoloaded in pd-l2ork but that approach is still susceptible to
overrides to the default config. Perhaps we should fold it into pd-l2ork? An
alternative is having aliases...
On 4/5/2016 10:43 AM, Alexandre Torres Porres wrote:
2016-04-05 5:08 GMT-03:00 Roman Haefeli <reduz...@gmail.com>:
If you're simply interested in knowing how things work technically, fine.
I'd love to know, for sure, that's why I'm asking :)
Now that we have a chance to get rid of all hexloader related kludges,
now you come and bring it up again.
You see, I don't really get what you mean by "hexloader" or its related
kludges. All I know is some [hexloader] object that is in my pd extended
0.42-5, and all I know is that I need to use it in order to load the [==~]
object from zexy. What you're talking about, somehow, relates to that?
Anyway, seems so to me... and if so, the thing is that what I'm asking and
doing has nothing to do with "hexloader"... (I never even mentioned about
"hexloader", btw) ... and I read about the "hex loader" discussion as
suggested, and found stuff that I didn't really think was related to my
questions. Yeah, like I said, I don't really know much and I'd like to know, so
I might be missing something, and someone can help me with it...
But the thing is, all I asked was how to compile an object like [==~] and
make it load without being part of a library. I found on deken a zexy version
that seemed to do that (specifically:
zexy-v0-0extended-(Darwin-i386-32)(Darwin-PowerPC-32)(Darwin-x86_64-32)-externals.tar).
And it didn't need a [hexloader] object too, by the way.
I didn't get an answer, but me and my colleague were checking the source code
from zexy and found some cues. We tried it... and it works!
Now I have an object that is compiled as [==~], it's not part of a library,
and it loads and works on pd vanilla 0.46-7 64 bits, pd vanilla 0.46-7 32 bits
and also Pd-Extended 0.42-5 (without the need of the [hexloader] object by the
way). All you need is the ==~.pd_darwin object in a search path.
Speaking and thinking as a user, I think it is easy and great to have a
working and compiled object that just loads and works, so that is what I 'm
after.
But anyway, yeah, I wanna know what are the dangers and all...
cheers
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
