CMake generate manifests that contain absolute filenames and these
currently result in assertion error. This change ensures that we
handle these correctly.
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
Comment Actions
Looks ok to me.
Is it possible to construct a test for this somehow? We don't know the absolute paths on the system running the tests, but can we e.g. do something like echo "INCLUDE %p/Inputs/somefile" > %t.rc in order to exercise it?
Comment Actions
LGTM
llvm/test/tools/llvm-rc/absolute.test | ||
---|---|---|
5 | The negative check for assertion might be a bit overkill, as a failed assert would make the llvm-rc command itself fail (a plain ; RUN: llvm-rc %t.rc to see that it can successfully compile that file would be enough), but I don't mind this either. |
The negative check for assertion might be a bit overkill, as a failed assert would make the llvm-rc command itself fail (a plain ; RUN: llvm-rc %t.rc to see that it can successfully compile that file would be enough), but I don't mind this either.