On Wednesday August 31 2016 17:25:18 Lawrence Velázquez wrote:
> You opened a ticket about this a while ago. One of Eric's comments hints at
> what a pain it might be to get it working with code signing.
> https://trac.macports.org/ticket/45251
I remembered, and apparently it was (over) 2y ago,
> On Aug 31, 2016, at 5:06 PM, Brandon Allbery wrote:
>
>> On Wed, Aug 31, 2016 at 4:57 PM, René J.V. Bertin
>> wrote:
>>
>> The real problem is going to be with the code-signing. This is done
>> automagically by lldb's Xcode projects so it's not entirely clear which
>> files have to be sign
> On Aug 31, 2016, at 4:57 PM, René J.V. Bertin wrote:
>
> I noticed that Apple don't ship an lldb-mi executable (at least they don't
> for OS X 10.9).
Xcode 7.3 includes it (`xcrun --run lldb-mi`) but Xcode 4.6.3 does not. Someone
else is welcome to bisect on that.
> Has anyone looked at bu
On Wed, Aug 31, 2016 at 4:57 PM, René J.V. Bertin
wrote:
> The real problem is going to be with the code-signing. This is done
> automagically by lldb's Xcode projects so it's not entirely clear which
> files have to be signed ... nor if an "ad-hoc" signing identify ("-") will
> lead to a usable
Hi,
I noticed that Apple don't ship an lldb-mi executable (at least they don't for
OS X 10.9). Lldb-mi is used by KDevelop5's lldb debugger plugin, so I'm trying
to hack together a PoC port:lldb-3.8 .
Has anyone looked at building an lldb port before? My current approach is to
apply the applic
