README: update location of built files
This commit is contained in:
parent
4eaac79ec2
commit
9cb03a3708
@ -44,7 +44,7 @@ $ make -f Makefile.e300artydevkit verilog
|
|||||||
$ make -f Makefile.e300artydevkit mcs
|
$ make -f Makefile.e300artydevkit mcs
|
||||||
```
|
```
|
||||||
|
|
||||||
These will place the files under `builds/e300artydevkit`.
|
These will place the files under `builds/e300artydevkit/obj`.
|
||||||
|
|
||||||
Note that in order to run the `mcs` target, you need to have the `vivado`
|
Note that in order to run the `mcs` target, you need to have the `vivado`
|
||||||
executable on your `PATH`.
|
executable on your `PATH`.
|
||||||
@ -77,7 +77,7 @@ $ make -f Makefile.u500vc707devkit verilog
|
|||||||
$ make -f Makefile.u500vc707devkit mcs
|
$ make -f Makefile.u500vc707devkit mcs
|
||||||
```
|
```
|
||||||
|
|
||||||
These will place the files under `builds/u500vc707devkit`.
|
These will place the files under `builds/u500vc707devkit/obj`.
|
||||||
|
|
||||||
Note that in order to run the `mcs` target, you need to have the `vivado`
|
Note that in order to run the `mcs` target, you need to have the `vivado`
|
||||||
executable on your `PATH`.
|
executable on your `PATH`.
|
||||||
|
Loading…
Reference in New Issue
Block a user