Package files serdes.cp and serdes++.cp do not exist.
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
- Domain
- build-system
Research direction
Start with the make install rules shown in the issue and inspect how serdes.pc and serdes++.pc are generated and installed. Determine the package files required by CMake find_package, then verify installation places them under /usr/local/lib/pkgconfig or the appropriate CMake package directory and that a consumer can find the library.
Written by the indexing model from the issue text.
Description
When installing the library with "make install" the following output is printed:
Install libserdes to /usr/local
install -d $DESTDIR/usr/local/include/libserdes ;
install -d $DESTDIR/usr/local/lib ;
install serdes.h serdes-common.h serdes-avro.h $DESTDIR/usr/local/include/libserdes ;
install libserdes.a $DESTDIR/usr/local/lib ;
install libserdes.1.dylib $DESTDIR/usr/local/lib ;
[ -f "serdes.pc" ] && (
install -d $DESTDIR/usr/local/lib/pkgconfig ;
install -m 0644 serdes.pc $DESTDIR/usr/local/lib/pkgconfig
) ;
(cd $DESTDIR/usr/local/lib && ln -sf libserdes.1.dylib libserdes.dylib)
Install libserdes++ to /usr/local
install -d $DESTDIR/usr/local/include/libserdes ;
install -d $DESTDIR/usr/local/lib ;
install serdescpp.h serdescpp-avro.h $DESTDIR/usr/local/include/libserdes ;
install libserdes++.a $DESTDIR/usr/local/lib ;
install libserdes++.1.dylib $DESTDIR/usr/local/lib ;
[ -f "serdes++.pc" ] && (
install -d $DESTDIR/usr/local/lib/pkgconfig ;
install -m 0644 serdes++.pc $DESTDIR/usr/local/lib/pkgconfig
) ;
(cd $DESTDIR/usr/local/lib && ln -sf libserdes++.1.dylib libserdes++.dylib)
but no serdes.cp nor serdes++.cp are copied to /usr/local/lib/pkgconfig and therefore cannot be used by cmake find_package command.
- Dominant language
- C
- Stars
- 12
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
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 confluentinc/libserdes
-
Difficulty 3/5 Half a day Newbie friendliness 22/100
confluentinc/libserdes#68 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 15/100
confluentinc/libserdes#66 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
confluentinc/libserdes#64 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
confluentinc/libserdes#63 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
confluentinc/libserdes#59 · 2 comments ·
All issues in confluentinc/libserdes
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
arduino/ArduinoCore-mbed#1126 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
security
Difficulty 1/5 Under an hour Newbie friendliness 93/100
btclib-org/btclib-secp256k1#1427 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
esmuellert/codediff.nvim#594 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 67/100