How poac manage dependencies #931
-
| 
         Hi, If I understand correctly I put in my poac.toml : poac will pull the repo and what's he going to do next? Can you make an example with GLFW of how in theory poac will manage this dependency?  | 
  
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
| 
         Since GLFW has an include/ directory, Poac automatically passes the path to this directory when you build your project. However, Poac currently supports building a project with header-only dependencies. If you need to build GLFW to use, then it cannot be used. If it is a header-only library, then you can use it like  So, as long as your dependency is header-only and provides its headers within the repository root (toml11 case) or include/ (GLFW case) directory, you can use it via Poac.  | 
  
Beta Was this translation helpful? Give feedback.
Since GLFW has an include/ directory, Poac automatically passes the path to this directory when you build your project. However, Poac currently supports building a project with header-only dependencies. If you need to build GLFW to use, then it cannot be used. If it is a header-only library, then you can use it like
#inlcude <GLFW/glfw3.h>, according to its directory structure.So, as long as your dependency is header-only and provides its headers within the repository root (toml11 case) or include/ (GLFW case) directory, you can use it via Poac.