pcp
[Top] [All Lists]

Re: [pcp] OSX Build issues (#52)

To: performancecopilot/pcp <pcp@xxxxxxxxxxxxxxxxxx>
Subject: Re: [pcp] OSX Build issues (#52)
From: Paul Smith <notifications@xxxxxxxxxx>
Date: Thu, 26 Nov 2015 12:56:22 -0800
Delivered-to: pcp@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=github.com; h=from:reply-to:to:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=8rTcb/1vJxqJr5w3Sv+9P8/FI4g=; b=PNO9GpCZpn4S93R8 5ZlHk9i8oGRWjHKdi+k36fbp3iPht5oS8v7dsIJVpF4Bm6Od1NAyKIYz/TEXfeXq t22NczRRqjpBQp3UtZgD45zv7GUOX+hwy6EzZEBoV50WGl1Q2uKqB1TIkKZyiUx1 17u394trl6G6DuX4g6HatOS5vrM=
In-reply-to: <performancecopilot/pcp/issues/52@xxxxxxxxxx>
List-archive: https://github.com/performancecopilot/pcp
List-id: performancecopilot/pcp <pcp.performancecopilot.github.com>
List-post: <mailto:reply+00bd08b6241815be28f06ca41e5484feeb74b1f22885650c92cf00000001126f33f592a169ce06ed5c42@reply.github.com>
List-unsubscribe: <mailto:unsub+00bd08b6241815be28f06ca41e5484feeb74b1f22885650c92cf00000001126f33f592a169ce06ed5c42@reply.github.com>, <https://github.com/notifications/unsubscribe/AL0ItrpbjEVjglY6yM3_b1MJZwZXhBzxks5pJ2l1gaJpZM4Gf1sU>
References: <performancecopilot/pcp/issues/52@xxxxxxxxxx>
Reply-to: performancecopilot/pcp <reply+00bd08b6241815be28f06ca41e5484feeb74b1f22885650c92cf00000001126f33f592a169ce06ed5c42@xxxxxxxxxxxxxxxx>

I understand from #48 that things are looking healthier build PCP, and indeed if I do a pull/rebase I can now successfully 'build' PCP via ./Makepkgs --verbose .

I can see a generated build/mac directory, but no DMG, and if I try hacking around with the build-installer script (ensuring I have all the necessary things for it), I am stumped by one remaning thing: IDB file.

I cannot find one anywhere in the tree, and it doesn't seem to get generated by the Makepkgs so I'm at a loss as to what to do to feed this.

I've asked on IRC today, but thought I'd document my progress here in case someone else out there knows exactly what to do.


Reply to this email directly or view it on GitHub.

<Prev in Thread] Current Thread [Next in Thread>