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
pkgconfig support #919
Comments
Original Redmine Comment Thanks for making a patch, seems reasonable. Is it really correct that there are no "Requires" or "Libs"? |
Original Redmine Comment As there is no libverilator.so or similar I suppose there is no useful value for Libs. Instead the user compiles the files in $pkgdatadir/include with his program. As the Requires only accounts for other pkgconfig files I can only see systemc as a candidate here, but it is not mandatory, so I left it out. I use it like this for the runtime files:
And like this for my program:
Linking does not require further pkgconfig information. I hope I don't "misuse" Verilator :) |
Original Redmine Comment I was thinking more along the lines of a dependance on the c libraries. Here's what debian uses, which are correct for this file?
|
Original Redmine Comment There is no pkgconfig variable for such "low level" libraries; it needs to be assumed that as you built verilator you have them available or if it is installed via a package manager this has to track this (like in the Debian file). The Requires in pkgconfig is rarely used, on my Ubuntu only for fixesproto.pc ("Requires: xextproto >= 7.0.99.1"). Summarized, pkgconfig requirements are only for such cases where we for example depend on another library to be linked with (say libusb >= 1.0), but not for the basic C runtime etc. Best, |
Original Redmine Comment Thanks again for the patch, pushed to git towards 3.873. |
Original Redmine Comment Hi again, sorry, I missed one point: The auto-generated files include @svdpi.h@ and need the path for this. This fixes this:
Sorry for missing this. Best, |
Original Redmine Comment Fixed, thanks |
Original Redmine Comment In 3.874. |
Original Redmine Comment Is the 'libdir' field needed ? |
Original Redmine Comment You are right, actually it is not used. I am not sure if it is required to provide the variable at least (so that prefix, libdir etc. can be checked). If you think it is not required to put it in a pkgconfig file, we can remove it. Best, |
Author Name: Stefan Wallentowitz (@wallento)
Original Redmine Issue: 919 from https://www.veripool.org
Original Date: 2015-05-13
Hi Wilson,
attached please find my proposed patch for a verilator pkg-config file. I unfortunately found that the method with VERILATOR_ROOT does not work properly with the Debian package and I believe pkgconfig is more flexible. It is installed in /usr/local/share/pkgconfig by default and /usr/share/pkgconfig with /usr prefix, both are properly found with pkg-config by default.
Best,
Stefan
The text was updated successfully, but these errors were encountered: