Unable to Include cppzmq Library in OMNeT++ Project Makefile Description
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- build-system
Research direction
Start with the project Makefile's makefiles target and the generated src/Makefile, then compare the include and library flags with the cppzmq README and the reported Windows vcpkg paths. Reproduce the zmq.hpp not found error in the OMNeT++ project. Done means the generated build can locate the cppzmq headers and compile the project.
Written by the indexing model from the issue text.
Description
I'm encountering an issue while trying to include the cppzmq library in my OMNeT++ project Makefile. My goal is to use cpppzmq as a messaging library for co-simulation between Carla and OMNET++ CARLANeT (https://github.com/carlanet). I followed the instructions in the project's README (https://github.com/zeromq/cppzmq) and installed cppzmq using vcpkg. However, when I add the necessary flags to the Makefile to link against cppzmq, I'm still unable to access the header files, and the compilation fails with the error message "zmq.hpp file not found" (project's workspace screenshot with error attached below)
Here's (the bold lines) the relevant portion of my Makefile where I added the flags to include cppzmq:
all: checkmakefiles
cd src && $(MAKE)
clean: checkmakefiles
cd src && $(MAKE) clean
cleanall: checkmakefiles
cd src && $(MAKE) MODE=release clean
cd src && $(MAKE) MODE=debug clean
rm -f src/Makefile
makefiles:
#cd src && opp_makemake -f --make-so --deep -o carlanet -O out -KINET4_4_PROJ=../../inet4.4 -DINET_IMPORT -I$$(INET4_4_PROJ)/src -L$$(INET4_4_PROJ)/src -lzmq -lINET$$(D)
cd src && opp_makemake -f --make-so --deep -o carlanet -O out -KINET4_4_PROJ=../../inet4.4 -DINET_IMPORT -I$(INET4_4_PROJ)/src -L$(INET4_4_PROJ)/src -lINET$(D) -LC:/Users/uqipali/Documents/omnet/omnetpp-6.0.2/vcpkg/packages/zeromq_x64-windows/lib -llibzmq-mt-4_3_5 -IC:/Users/uqipali/Documents/omnet/omnetpp-6.0.2/vcpkg/installed/x64-windows/include
checkmakefiles:
@if [ ! -f src/Makefile ]; then
echo;
echo '=======================================================================';
echo 'src/Makefile does not exist. Please use "make makefiles" to generate it!';
echo '=======================================================================';
echo;
exit 1;
fi
Could you please advise on what needs to be corrected in order to successfully use cppzmq in my OMNeT++ project? Any assistance would be greatly appreciated. Thank you in advance :)
- Dominant language
- C++
- Stars
- 2.3k
- Forks
- 799
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from zeromq/cppzmq
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Add CURVE default keys constantsPossibly taken @cacharle claimed this 256 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
-
Difficulty 1/5 Under an hour Newbie friendliness 15/100
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Similar issues
-
bug derived types format I/O medium priority semantics
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Incorrect Link in README.mdPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 95/100
flameshot-org/flameshot#4996 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
utopia-rise/godot-jvm#1004 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day