Re: [cdt-dev] Circular dependencies

[Doug Schaefer <dschaefer@xxxxxxx>]

LOL, Marc pointed out another cycle that I forgot about and unrelated to Arduino. The Remote Local command shell service now uses PTY and Spawner from CDT native as well. Even more reason to break it out.

I’ve committed my Arduino change which has the fix that will fix this as well. I’ve started a new cdt-master build and will check later tonight when I get home.

Thanks for your patience,

Doug.

From: Doug Schaefer <dschaefer@xxxxxxx>
Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: Monday, May 4, 2015 at 4:09 PM
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] Circular dependencies

I’m going to cheat for now. I’ve added the results from the last build as dependencies on the current build. Ugly and evil, but it seems to work :). I’ll create the native build post M7.

From: Doug Schaefer <dschaefer@xxxxxxx>
Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: Monday, May 4, 2015 at 3:28 PM
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Subject: [cdt-dev] Circular dependencies

Well, we hit it. The Arduino CDT plug-ins depend on the Remote plug-ins which depend on the CDT Native plug-ins. For some crazy reason I thought we’d get away with it, but it falls apart with the CDT builds that produce both ends of that.

It’s time to break out the native plug-ins into their own build. I’ll take a quick hack at that and hopefully plow through this by tomorrow.

Doug.