You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
@melvinhe Thanks for checking this out for us. Could you let me know what the output of
pkg-config --libs benchmark,
uname -p, and
pkg-config --variable pc_path pkg-config
for me? The output you showed indicates that libbenchmark isn't installed/accessible on your system, and so it could be an issue with brew, libbenchmark, or pkg-config.
Is there an existing issue for this?
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:Expected Behavior
Running
make clean
from a build directory should not modify the source directory.Steps To Reproduce
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.The text was updated successfully, but these errors were encountered: