This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Allow eosiocpp to run without make install #5206
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
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.
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.
I worry about packaging and installing a script that has the full CMAKE_BINARY_DIR in the resulting file. Won't that leak some information that could be considered sensitive about the system that built the binary package (like user name of the builder etc).
Can we do something where it discovers all of these paths relative to the directory where the script resides so that we don't have to hard code the absolute path? I realize this makes
eosiocpp
fragile when you copy/move it around but, that seems like a better trade?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.
It could leak information depending on how it's built. It does not have to be sensitive information, especially on dedicated build boxes. At present, we're not distributing any package format except Docker, which I don't think carries ownership or a home directory path within it. Finally, this is a stopgap until the wasmsdk repo is ready for prime time.
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.
yeah, docker should do a decent job of sanitizing paths... I'm checking right now and will release my objection if it looks benign.