[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
projectile: Set compile-command
From: |
Florian Lindner |
Subject: |
projectile: Set compile-command |
Date: |
Tue, 24 Feb 2015 09:40:05 +0100 |
User-agent: |
KNode/4.14.5 |
Hello,
the projectile readme mentions the setting of compile-command twice:
https://github.com/bbatsov/projectile
Once by using .dir-locals.el und set it directly (Storing project settings).
Anothertime by using something like that:
((nil . ((eval . (progn
;; require projectile; the following code will fail
;; without it.
(require 'projectile)
;; provide a fake "recent" compilation cmd
;; which will be returned by the function
;; `projectile-compilation-command`
(puthash (projectile-project-root)
"./command-to-compile-your-project.sh"
projectile-compilation-cmd-map))))))
(Configure Project's Compilation Command)
The first does not really seem to work, upon C-c p c it asks me a for a
compile command which defaults to scons here. I'm suprised that merely
setting the compile-command is so complicated and why it does not take
compile-command into account.
Thanks,
Florian
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- projectile: Set compile-command,
Florian Lindner <=