Open
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
Running make clean
from a build directory removes the following checked-in files from the source , resulting in unstaged changes in the git repo:
Unstaged changes (12)
deleted src/groups/mwc/mwcex/mwcex_bindutil_cpp03.cpp
deleted src/groups/mwc/mwcex/mwcex_bindutil_cpp03.h
deleted src/groups/mwc/mwcex/mwcex_future_cpp03.cpp
deleted src/groups/mwc/mwcex/mwcex_future_cpp03.h
deleted src/groups/mwc/mwcex/mwcex_promise_cpp03.cpp
deleted src/groups/mwc/mwcex/mwcex_promise_cpp03.h
deleted src/groups/mwc/mwcu/mwcu_noop_cpp03.cpp
deleted src/groups/mwc/mwcu/mwcu_noop_cpp03.h
deleted src/groups/mwc/mwcu/mwcu_objectplaceholder_cpp03.cpp
deleted src/groups/mwc/mwcu/mwcu_objectplaceholder_cpp03.h
deleted src/groups/mwc/mwcu/mwcu_operationchain_cpp03.cpp
deleted src/groups/mwc/mwcu/mwcu_operationchain_cpp03.h
Expected Behavior
Running make clean
from a build directory should not modify the source directory.
Steps To Reproduce
- Clone the repo at
main
. ./bin/build-darwin.sh
from an up-to-date Mac.(cd build/blazingmq && make clean) && ./bin/build-darwin.sh
BlazingMQ Version
HEAD
Anything else?
I will see if I can reproduce this on a Linux box this evening.
Deleting the blazingmq build directory obviates this problem (cd build && rm -r blazingmq
in place of the steps to reproduce). The _cpp03.h
files are generated as part of our build to provide C++03 compatible copies of C++11 or later constructs in MWC. Despite being generated, they should probably live in source control. My intuition is that CMake will be our savior here.