Skip to content
This repository was archived by the owner on Feb 4, 2020. It is now read-only.

Commit

Permalink
Mention how to integrate clcache with Visual Studio
Browse files Browse the repository at this point in the history
It's apparently not too easy to make Visual Studio pick up clcache. I
don't use the IDE myself, but others described that replacing the
original binary works. So let's at least mention this approach.

Resolves #18.
  • Loading branch information
Frerich Raabe committed Jun 24, 2016
1 parent b2fcde4 commit e6d7255
Show file tree
Hide file tree
Showing 2 changed files with 13 additions and 0 deletions.
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,8 @@ clcache changelog

* Improvement: better protection against storing corrupt objects in the cache
in case clcache is terminated in the middle of storing a new cache entry.
* Improvement: The README now explains an approach to making Visual Studio
pick up clcache.
* Bugfix: Command files with multiple lines are now handled correctly.
* Bugfix: Properly handle non-ASCII compiler output (GH #64)

Expand Down
11 changes: 11 additions & 0 deletions README.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,17 @@ renamed and forward all the arguments to the real compiler executable.
This way, simply running 'cl' will invoke the script instead of the real
compiler.

Installation For Visual Studio
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Some users have reported (see e.g. GitHub issue #18) that in order to make Visual Studio pick up `clcache`, the original compiler binary needs to be moved out of the
way and replaced with the executable generated via the `py2exe` script:

1. Rename `cl.exe` to e.g. `cl_original.exe`
2. Rename `cl.exe.config` to e.g. `cl_original.exe.config`
3. Copy `clcache.exe` to `cl.exe`
4. Set `CLCACHE_CL` environment variable to point to `cl_original.exe`.

Options
~~~~~~~

Expand Down

0 comments on commit e6d7255

Please sign in to comment.