Stream: git-wasmtime

Topic: wasmtime / PR #1425 Use relative path to access OUT_DIR

view this post on Zulip Wasmtime GitHub notifications bot (Mar 27 2020 at 20:55):

benbrittain opened PR #1425 from master to master:

This change is designed to be the minimal change necessary for compatibility with build systems that need to check in the metadata normally provided by build.rs scripts.

Context on why this is necessary:
Cargo outputs OUT_DIR as an absolute path to the resources generated by the custom-build target. This is generally not a problem, since other systems can provide a relative path, however codegen uses OUT_DIR from multiple depths in the tree.

view this post on Zulip Wasmtime GitHub notifications bot (Mar 27 2020 at 20:56):

benbrittain updated PR #1425 from master to master:

This change is designed to be the minimal change necessary for compatibility with build systems that need to check in the metadata normally provided by build.rs scripts.

Context on why this is necessary:
Cargo outputs OUT_DIR as an absolute path to the resources generated by the custom-build target. This is generally not a problem, since other systems can provide a relative path, however codegen uses OUT_DIR from multiple depths in the tree.

view this post on Zulip Wasmtime GitHub notifications bot (Mar 27 2020 at 20:57):

benbrittain updated PR #1425 from master to master:

This change is designed to be the minimal change necessary for compatibility with build systems that need to check in the metadata normally provided by build.rs scripts.

Context on why this is necessary:
Cargo outputs OUT_DIR as an absolute path to the resources generated by the custom-build target. This is generally not a problem, since other systems can provide a relative path, however codegen uses OUT_DIR from multiple depths in the tree.

view this post on Zulip Wasmtime GitHub notifications bot (Mar 27 2020 at 21:04):

benbrittain updated PR #1425 from master to master:

This change is designed to be the minimal change necessary for compatibility with build systems that need to check in the metadata normally provided by build.rs scripts.

Context on why this is necessary:
Cargo outputs OUT_DIR as an absolute path to the resources generated by the custom-build target. This is generally not a problem, since other systems can provide a relative path, however codegen uses OUT_DIR from multiple depths in the tree.

view this post on Zulip Wasmtime GitHub notifications bot (Mar 27 2020 at 22:45):

benbrittain closed without merge PR #1425.

Last updated: Nov 22 2024 at 17:03 UTC