Skip to content
This repository has been archived by the owner on Jan 6, 2022. It is now read-only.

README: Add reminder to keep shell environment clean #42

Merged
merged 1 commit into from
Dec 14, 2018

Conversation

andreaskurth
Copy link
Contributor

Close #40.

@@ -18,6 +18,8 @@ The HERO software development kit (SDK) contains the following submodules:
The HERO SDK currently supports the [Xilinx Zynq ZC706 Evaluation Kit](https://www.xilinx.com/products/boards-and-kits/ek-z7-zc706-g.html) as target hardware platform.

### Software
First, make sure your shell environment does not deviate from the system defaults regarding paths (`PATH`, `LD_LIBRARY_PATH`, etc) before setting up the SDK or sourcing the environment of the HERO SDK.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if I have to be honest, I think the disclaimer could be misleading. The root cause of the problem issued #40 is the fact that cmake version used was not compatible with our build flow. Then secondarily the problem was caused by the Vivado's environment that could change - in a stealth mode - the program versions compare the default ones.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see #40 as one specific instance of a more general workflow problem. A similar problem could have faced when a user sources the Vivado environment after sourcing the HERO environment, and the ARM compiler in the Vivado SDK is invoked instead of HERO's. So the very basic rule is: Non-default paths should be avoided.

@andreaskurth andreaskurth merged commit 84d7df4 into master Dec 14, 2018
@alessandrocapotondi alessandrocapotondi deleted the 40-readme-shell-env branch February 4, 2019 15:47
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants