A fix to "NAR: Compile failed: Output filename conflict" #178
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I generally follow #141 to insert a
hash(absoluteSourceFilePath)
between the object file basename and its extension. I found it quite difficult to mirror the folder structure of the source file into the object file (like discussed in #162 ), because thecompile
interface insrc/main/java/com/github/maven_nar/cpptasks/compiler/AbstractCompiler.java
make the output file invisiable tocommandlinecompiler
.What #141 seemed to miss is that c++ compiler should compile one source into one object file by one command. But the original code seems to feed several sources to one command and it makes
-o
to several objects invalid.It's a quick and dirty solution to the conflict problem however may works.