http://www.eclipse.org/downloads/
https://github.com/DDT-IDE/DDT/blob/latest/documentation/UserGuide.md
https://github.com/DDT-IDE/DDT/blob/latest/documentation/Installation.md#installation
http://zhidao.baidu.com/link?url=GNBcn99VMm2YiVcgQIp7u71Woug0Qmh19zbL48W3zuPGeNzW8QG2gW9teG7o-OxCq2mliS612X_ANKbo6Pa-TxpjjDEMcF3c-XKHKkNGV-_
http://stackoverflow.com/questions/25811824/ddt-error-standard-library-not-found
http://forum.dlang.org/post/kdmnwcozcwrjwzfdaetx@forum.dlang.org
http://qiita.com/hayashikun/items/3b29e76d83e822c5ca24
# cd /usr/share/dmd
# mkdir dummy
# mkdir dummy/bin
# touch dummy/bin/dmd
# launchctl setenv DUB_COMPILERS_PATH /usr/share/dmd/dummy/bin
# killall Dock
What's Happen?
El Capitanにしたら、DDTが動かなくなった
DDTはEclipseのD Development Toolで個人的には数少ないDのIDE中一番好きなんだけど、El Capitanにしたら/usr/まわりが変わった影響か突然動かなくなった
下のConsoleには
>> Running: /usr/local/bin/dub describe
Failed to invoke the compiler dmd to determine the build platform: /bin/sh: dmd: command not found
と出て絶望
D Standard LibaryとかもError not foundになってる
変更してCmd+Sしたあとに走るbuildは生きてる
ターミナルから
$ /Applications/Eclipse.app
ってして起動すれば問題無く動く
試したこと
- 環境設定 > DDT > DUB pathを
/usr/local/Cellar/dmd/2.068.2/bin/dubにする → buildも死ぬ - .zshrcで環境変数に
DUB_COMPILERS_PATH="/usr/local/bin"を追加 → 特に変化なし
結論
mac app 環境変数とかでググったらFinderとかLaunchpad経由で起動されるアプリにパスを足す方法が書いてあるけどめんどくさいのでコンソールから起動することにする
https://gcc.gnu.org/onlinedocs/gnat_ugn/Codesigning-the-Debugger.html
Up: Mac OS Topics
9.4.1 Codesigning the Debugger
The Darwin Kernel requires the debugger to have special permissions before it is allowed to control other processes. These permissions are granted by codesigning the GDB executable. Without these permissions, the debugger will report error messages such as:
Starting program: /x/y/foo
Unable to find Mach task port for process-id 28885: (os/kern) failure (0x5).
(please check gdb is codesigned - see taskgated(8))
Codesigning requires a certificate. The following procedure explains how to create one:
- Start the Keychain Access application (in /Applications/Utilities/Keychain Access.app)
- Select the Keychain Access -> Certificate Assistant -> Create a Certificate... menu
- Then:
- Choose a name for the new certificate (this procedure will use "gdb-cert" as an example)
- Set "Identity Type" to "Self Signed Root"
- Set "Certificate Type" to "Code Signing"
- Activate the "Let me override defaults" option
- Click several times on "Continue" until the "Specify a Location For The Certificate" screen appears, then set "Keychain" to "System"
- Click on "Continue" until the certificate is created
- Finally, in the view, double-click on the new certificate, and set "When using this certificate" to "Always Trust"
- Exit the Keychain Access application and restart the computer (this is unfortunately required)
Once a certificate has been created, the debugger can be codesigned as follow. In a Terminal, run the following command:
$ codesign -f -s "gdb-cert" <gnat_install_prefix>/bin/gdb
where "gdb-cert" should be replaced by the actual certificate name chosen above, and <gnat_install_prefix> should be replaced by the location where you installed GNAT. Also, be sure that users are in the Unix group _developer.