You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Notable changes:
* OS X support
* Pure Go readline library
* Fixes issues debugged cgo enabled programs
* Substantial refactoring / code cleanup
Fixesgo-delve#3go-delve#29go-delve#70
Copy file name to clipboardExpand all lines: README.md
+21-3Lines changed: 21 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -10,13 +10,32 @@ This project is currently in beta. Most of the functionality is there, but there
10
10
11
11
### Building
12
12
13
-
Delve requires Go 1.4 to build, and currently only supports Linux, with OS X support coming soon.
13
+
Delve requires Go 1.4 to build.
14
14
15
15
```
16
16
go get -u github.com/derekparker/delve/cmd/dlv
17
17
```
18
18
19
-
You will need readline installed on your system. With apt simply: `sudo apt-get install libreadline-dev` .
19
+
#### Linux
20
+
21
+
You're done!
22
+
23
+
#### OS X
24
+
25
+
If you are on OS X a few extra steps must be taken. You must create a self signed certificate:
26
+
27
+
* Open application “Keychain Access” (/Applications/Utilities/Keychain Access.app)
28
+
* Open menu /Keychain Access/Certificate Assistant/Create a Certificate...
29
+
* Choose a name (dlv-cert in the example), set “Identity Type” to “Self Signed Root”, set “Certificate Type” to “Code Signing” and select the “Let me override defaults”. Click “Continue”. You might want to extend the predefined 365 days period to 3650 days.
30
+
* Click several times on “Continue” until you get to the “Specify a Location For The Certificate” screen, then set “Keychain to System”.
31
+
* If you can't store the certificate in the “System” keychain, create it in the “login” keychain, then export it. You can then import it into the “System” keychain.
32
+
* In keychains select “System”, and you should find your new certificate. Use the context menu for the certificate, select “Get Info”, open the “Trust” item, and set “Code Signing” to “Always Trust”.
33
+
* You must quit “Keychain Access” application in order to use the certificate and restart “taskgated” service by killing the current running “taskgated” process. Alternatively you can restart your computer.
34
+
35
+
All `make` commands assume a CERT environment variables that contains the name of the cert you created above.
36
+
Following that you can `CERT=mycert make install` which should install the binary and codesign it. For running tests, simply run `CERT=mycert make test`.
37
+
38
+
The makefile is only necessary to help facilitate the process of building and codesigning.
20
39
21
40
### Features
22
41
@@ -81,7 +100,6 @@ Once inside a debugging session, the following commands may be used:
0 commit comments