<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 05/09/2021 20:57, Christo Crause
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAGOmfbHrzoT2hC6Nh4mdgG_aKDLNcZR=-HT8g_Amvw9TQ5+5WQ@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr"><br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Sun, Sep 5, 2021 at 8:24
            PM Martin Frb via lazarus <<a
              href="mailto:lazarus@lists.lazarus-ide.org"
              moz-do-not-send="true">lazarus@lists.lazarus-ide.org</a>>
            wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <div>I ve seen it. I am really rather busy ...<br>
              </div>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>No worries, I do realise there are a lot of changes to
            work through.  <br>
          </div>
          <div> </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <div> I had a look at the first 2 or 3 commits some weeks
                ago.<br>
                From what I recall<br>
                <br>
                1) adding to the IDE options. Looks that then every user
                using fpdebug, will see options for host/port? <br>
                While really convenient for avr users, rather confusing
                for others?<br>
              </div>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>I am starting to agree with this view. There are quite a
            few extra remote options that should eventually be
            implemented, so the IDE options will become more busy.  My
            simplistic view is that a new remote Lazarus debugger will
            inherit just about all its core functionality from the
            existing FpDebugDebugger, with added remote config options.<br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    There are 2 ways here:<br>
    <br>
    1) find a way to pass a custom config to whatever T[avr]DbgProcess.<br>
    <br>
    2) Instantiate a process class, before starting the controller, and
    push that in.<br>
    That also has the advantage that it allows to choose between several
    process classes, if more than one can handle the target.<br>
    <br>
    <br>
    <blockquote type="cite"
cite="mid:CAGOmfbHrzoT2hC6Nh4mdgG_aKDLNcZR=-HT8g_Amvw9TQ5+5WQ@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_quote">
          <div><br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>
              <div> 2) global vars (iirc for host/port)<br>
                That is due to the lack of config that can be passed
                in....<br>
                <br>
                FpDebug (package) can not see the IDE conf. FpDebug
                should have minimum package depenencies.<br>
                It needs its own conf that can be passed....<br>
                I have some ideas there, ....<br>
              </div>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>Will gladly await your ideas.  This can wait, it is just
            a bad practise on my side currently, but workable.<br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    (2) above would deal with this.<br>
    <br>
    <br>
    <br>
  </body>
</html>