-
Notifications
You must be signed in to change notification settings - Fork 37
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Allows to skip pre-compiling VC4CL stdlib at compile time
This is e.g. useful for packaging builds, where the pre-compilation should happen at install time. See #145
- Loading branch information
Showing
3 changed files
with
5 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1bb1b55
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If "VC4CL_STDLIB_PRECOMPILE" is absent or set to ON, the file "VC4CLStdLib.h.pch" is created in "VC4CL_STDLIB_DIR".
If "VC4CL_STDLIB_DIR" is set to "/usr/local/include/vc4cl-stdlib", the file cannot be created due to a permission issue:
The problem seems be caused by packaging and installing vc4cl-stdlib first, prior to building and packaging vc4c. When building and packaging vc4c one cannot rely the interim build results for vc4cl-stdlib being available.
Rather than setting VC4CL_STDLIB_PRECOMPILE to OFF, can "VC4CLStdLib.h.pch" be temporary stored somewhere else, relative to vc4c?
1bb1b55
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
VC4CLStdLib.h.pch
will be stored where VC4C expects it to be for the development build, otherwise you would not be able to run the development build directly.In the CI to build the debian packages, the same job to build the VC4C package also builds the VC4CLStdLib package, making the VC4CLStdLib sources available locally and also allowing the
VC4CLStdLib.h.pch
to be build into the local directories while still having the installedVC4CLStdLib.h.pch
built into/usr/local/include/vc4cl-stdlib
. Can't you do the same?If you have a build of VC4C without any VC4CLStdLib sources (or the sources already installed e.g. in
/usr/local/include/vc4cl-stdlib
), how should the VC4C determine some local path where theVC4CLStdLib.h.pch
is pre-built into?