title: Vivado Libraries
body: <p>I am trying creating a library of components that I can use in Vivado(2014.2). I have many .vhd files and I would like to add more in the future, and so I'd prefer not to have to condense them
  all into a single .vhd.</p>
  
  <p>I may need to use a package...
  ie. </p>
  
  <pre><code>--File name: my_library_file
  package my_lib_package is 
  --All component declarations...
  end package my_lib_package;
  </code></pre>
  
  <p>But would all the entities and architectures also need to be in this file?</p>
  
  <p>Then I could use a "use" statement to reference these elements.
  ie. use my_lib.
  But would the my_library_file need to be located in the same project?</p>
  
  <p>I would like to be able to make this library once and be able to reference in
  any project with a call. </p>
  
  <p>Ideally it could be called like an IEEE library but with many vhd files being referenced.</p>
  
  <p>I would prefer not to explicitly add/include these individual source files to the project, but would instead prefer to just be able to use the “use” clause with library and/or package…if possible.</p>