search

banditcpp / bandit

Human-friendly unit testing for C++11
https://banditcpp.github.io/bandit/
Other
259 stars 37 forks source link

snowhouse.h: No such file or directory #125

Closed k2snowman69 closed 6 years ago

k2snowman69 commented 6 years ago

Newbie question here... I'm moving all my code from being MSVC to something more flexible and came upon your repo. Love the concept and how similar to Mocha js it!

I did run into an issue when I was trying to build my project. My repro steps are:

  1. git clone https://github.com/banditcpp/bandit
  2. Copy/paste the example code on home page into main.cpp
  3. Build (I'm on windows so I'm using mingw32)
C:\Users\RickyPatel\Desktop\TestApp\client.shared.test>mingw32-make
g++ -c src\main.cpp -o debug_obj\src\main.o -I..\..\bandit -I..\client.shared\debug\headers -L..\client.shared\debug -lclient.shared -O0 -g3
In file included from ..\..\bandit/bandit/adapters.h:4:0,
                 from ..\..\bandit/bandit/grammar.h:4,
                 from ..\..\bandit/bandit/bandit.h:12,
                 from src\main.cpp:1:
..\..\bandit/bandit/adapters/snowhouse.h:6:71: fatal error: bandit/assertion_frameworks/snowhouse/snowhouse/snowhouse.h: No such file or directory
 #include <bandit/assertion_frameworks/snowhouse/snowhouse/snowhouse.h>
                                                                       ^
compilation terminated.
makefile:44: recipe for target 'debug_obj/src/main.o' failed

Looking at the source code in GitHub looks like there is a reference to another repository https://github.com/banditcpp/bandit/tree/master/bandit/assertion_frameworks

When I do a git pull, my assertion_frameworks folder is empty. Anyone know how I'm supposed to properly pull this from master so that snowhouse gets populated?

k2snowman69 commented 6 years ago

Apparently you need to run: git submodule update --init For git to download all the required submodules.

This would be super useful to document somewhere for new people using the system who may not have used submodules (e.g. me!)

k2snowman69 commented 6 years ago

Leaving this open as the bug to update the getting started documentation

sbeyer commented 6 years ago

The even better recommendation is to use git clone --recursive instead of simple git clone. It's a problem among all git commands that the useful things are not set as defaults.

sbeyer commented 6 years ago

Is #126 good enough? ;)

k2snowman69 commented 6 years ago

Looks perfect! I am extremely impressed with your turn around time!