Reputation: 39
I am working on a template that makes use of Premake and GoogleTest, but I am having issues finding any documentation on a standardized method of implementing Premake. The source that I have been using to design my workspace places a core
Build.lua that connects to secondary Build.lua files inside each individual project in the workspace.
Would it be considered better implementation to place a Build.lua into the GoogleTest Repository, even if it isn't locally managed? Would it be better to create an all encompassing Build.lua file for all vendors within my vendor directory? Or should I place individual build files outside of my vendor repositories, even if it breaks my current standards? Is there a solution that I am not considering that could resolve this without any of the aforementioned drawbacks?
I have attempted placing a Build.lua file inside of the vendor's directory - however, I was concerned that this was a bad practice as it could cause interferences if I needed to update the repository in the future, and it could be misleading to individuals that recognize the vendor and assume the repository to be a mirror of the vendor's.
Upvotes: 0
Views: 47
Reputation: 39
For anyone else who sees this - the solution I'm using for the time being is as follows.
Instead of saving GoogleTest as GoogleTest
, I am saving GoogleTest as GoogleTest/src
and saving my build file as GoogleTest/Build-GoogleTest.lua
.
Upvotes: 0