Closed Eran-YT closed 3 years ago
Does GTEST really need to be part of this repository? Can't it be a submodule or an artifact being downloaded on demand?
Does GTEST really need to be part of this repository? Can't it be a submodule or an artifact being downloaded on demand?
I'll try to fix it
Gtest is now consumed via nuget package
@Neo23x0 This is ready for merge
As far as I can see there are quite a lot of noisy changes in this PR. Is all of this needed? Can the individual commits maybe be squashed in logical steps?
They can be squashed in the merge
Personally I prefer to squash all PR in projects I work on, but that's not my decision here
You can of course rewrite the history of this PR and then do a force-push to have a clean history before merge.
I rewrote the git history for this PR, is this what you meant?
Thanks a lot to you two. We've started this as a hacky PoC and now it gets more and more professional.
Create Raccine-Test and RaccineLib projects: Raccine-Test contains the unit tests RaccineLib contains the source Raccine is the project that build the executable, should contain no business logic (currently does, but needs to be moved) Added an example unit test