-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent directory structure Help!! #409
Comments
I restructure it. What problem do you encounter with the new structure? |
i use https://github.com/apache/rocketmq-client-go/tree/v1.2.4 version |
@Shencw You need to use below command sudo cp rocketmq-client-cpp/include/c/* /usr/local/include/rocketmq instead of sudo cp rocketmq-client-cpp/include/* /usr/local/include/rocketmq |
@ifplusor I try to use the prompt like this and the result is as follows # github.com/apache/rocketmq-client-go/core
../../../go/pkg/mod/github.com/apache/[email protected]/core/pull_consumer.go:46:33: could not determine kind of name for C.E_BROKER_TIMEOUT |
@Shencw modify CPullResult.h with ifplusor@560f471 |
I want to remind you that the |
do I have anything I can use ? Mac M1 (Big Sur) or Mac intel (Big Sur) |
@Shencw PullConsumer is what you need to use? |
maybe you can have a try on the native go client. https://github.com/apache/rocketmq-client-go/tree/master/examples/consumer/pull |
The issue tracker is ONLY used for the CPP/C client (feature request of RocketMQ need to follow RIP process). Keep in mind, please check whether there is an existing same report before your raise a new one.
Alternately (especially if your communication is not a bug report), you can send mail to our mailing lists. We welcome any friendly suggestions, bug fixes, collaboration, and other improvements.
Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as to the following:
BUG REPORT
What did you do (The steps to reproduce)?
i used
re_dev
branchWhat did you expect to see?
The
master
branch and there_dev
branch have the same directory structureWhat did you see instead?
re_dev
include directory include/c and include/*master
include directory include/*The text was updated successfully, but these errors were encountered: