Skip to content

Update documentation to use --detect-vendored. #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
csasarak wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update documentation to use --detect-vendored. #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions scripts.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
exit 0;

# Regenerate binaries
mkdir -p bin/libjson_internal bin/libauth_internal bin/jq
mkdir -p bin/libjson_internal bin/libauth_internal bin/jq internal-json-parser/vendor/
dd if=/dev/urandom bs=1 count=100000 of=bin/libjson_internal/libjson_internal.o
dd if=/dev/urandom bs=1 count=100000 of=bin/libauth_internal/libauth_internal.o
dd if=/dev/urandom bs=1 count=100000 of=bin/jq/jq.o
Expand All @@ -14,7 +14,7 @@ cp bin/libjson_internal/libjson_internal.o example-internal-project/include/libj
fossa analyze example-internal-project \
-e '<endpoint>' --fossa-api-key <api-key> \
--project internal-project --revision $(date +%s) \
--experimental-enable-vsi
--detect-vendored

# Notice that we discover two vendored dependencies: folly and tessaract.
# However, in our example, we also have some binaries that are built internally (in `include`) that we want to track.
Expand Down Expand Up @@ -43,13 +43,13 @@ fossa analyze internal-json-parser \
-e '<endpoint>' --fossa-api-key <api-key> \
--project internal-json-parser --revision $(date +%s) \
--experimental-link-project-binary bin/libjson_internal \
--experimental-enable-vsi
--detect-vendored

# Now that we've linked our dependencies, we can re-analyze our internal project:
fossa analyze example-internal-project \
-e '<endpoint>' --fossa-api-key <api-key> \
--project internal-project --revision $(date +%s) \
--experimental-enable-vsi
--detect-vendored

# We now should see the dependencies that were vendored as before, but this time we also show the new dependencies we've linked.
# We also see the deep dependencies in the case of the our internal JSON parsing library, since it is also a project in FOSSA!