<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    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...<br>
    <br>
    <div class="moz-cite-prefix">On 4/5/2016 10:43 AM, Alexandre Torres
      Porres wrote:<br>
    </div>
    <blockquote
cite="mid:CAEAsFmjJpkgpXj3zbjrRXSwD3fwea8yqLQ=77EBbDPmX5CU3aA@mail.gmail.com"
      type="cite">
      <div dir="ltr"><br>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">2016-04-05 5:08 GMT-03:00 Roman
            Haefeli <span dir="ltr"><<a moz-do-not-send="true"
                href="mailto:reduzent@gmail.com" target="_blank">reduzent@gmail.com</a>></span>:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> If
              you're simply interested in knowing how things work
              technically, fine.</blockquote>
            <div><br>
            </div>
            <div>I'd love to know, for sure, that's why I'm asking :)</div>
            <div>
              <div> </div>
              <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Now
                that we have a chance to get rid of all hexloader
                related kludges,<br>
                now you come and bring it up again.</blockquote>
              <div><br>
              </div>
              <div>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? </div>
              <div><br>
              </div>
              <div>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...</div>
            </div>
            <div><br>
            </div>
            <div>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: <span style="font-size:12.8px"><i>zexy-v0-0extended-(Darwin-</i></span><span
                style="font-size:12.8px"><span
                  style="font-style:italic;font-size:12.8px">i386-32)(Darwin-PowerPC-32)(</span><span
                  style="font-style:italic;font-size:12.8px">Darwin-x86_64-32)-externals.</span><span
                  style="font-size:12.8px"><i>tar</i>). And it didn't
                  need a [hexloader] object too, by the way.</span></span></div>
            <div><span style="font-size:12.8px"><span
                  style="font-size:12.8px"><br>
                </span></span></div>
            <div><span style="font-size:12.8px"><span
                  style="font-size:12.8px">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!</span></span></div>
            <div><span style="font-size:12.8px"><span
                  style="font-size:12.8px"><br>
                </span></span></div>
            <div><span style="font-size:12.8px"><span
                  style="font-size:12.8px">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, </span></span><span
                style="font-size:12.8px">pd vanilla </span><span
                style="font-size:12.8px">0.46-7 32 bits</span><span
                style="font-size:12.8px"> and also Pd-Extended 0.42-5 (<b><u>without</u></b> the
                need of the [hexloader] object by the way). </span><span
                style="font-size:12.8px">All you need is the
                ==~.pd_darwin object in a search path.</span></div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>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.</div>
            <div><br>
            </div>
            <div>But anyway, yeah, I wanna know what are the dangers and
              all...</div>
            <div><br>
            </div>
            <div>cheers</div>
            <div><br>
            </div>
            <div><br>
            </div>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
<a class="moz-txt-link-abbreviated" href="mailto:Pd-list@lists.iem.at">Pd-list@lists.iem.at</a> mailing list
UNSUBSCRIBE and account-management -> <a class="moz-txt-link-freetext" href="https://lists.puredata.info/listinfo/pd-list">https://lists.puredata.info/listinfo/pd-list</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>