Skip to content

Conversation

griwes
Copy link
Member

@griwes griwes commented Jan 11, 2017

Will solve #3 and #10 once completed.

The C++ compiler in use is now detected; vendor-specific compiler flags
are now supported for C++ files.

C++ file's output now also depends on the compiler (so if you update the
compiler, everything will be rebuilt) and on the exact command line used
to build it; this, together with the fact that $CXXFLAGS is used in the
command line, means that changing that environment variable prompts a
rebuild.

At some point in the future I'll probably introduce a mode that fixes
the contents of CXXFLAGS from the first build that happens for an output
directory, plus some additional caching (like not having to respecify
the compiler via CXX), but it's not a priority right now.
@griwes griwes added this to the Release v0.1 milestone Jan 11, 2017
@griwes griwes self-assigned this Jan 11, 2017
@griwes griwes changed the title Compiler and linker detection. Compiler and linker detection for the C++ plugin. Jan 11, 2017
Also the dependency on the compiler isn't only on the exact path that is
used, but also on all the symlinks along the way. I wonder whether this
same approach should also be used for other dependencies, but let's
ignore this for now.
@griwes griwes changed the title Compiler and linker detection for the C++ plugin. WIP: Compiler and linker detection for the C++ plugin. Jan 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

1 participant