-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add swig/4.0.1 #1717
Add swig/4.0.1 #1717
Conversation
Some configurations of 'swig/4.0.1' failed in build 1 (
|
Some configurations of 'swig/4.0.1' failed in build 2 (
|
All green in build 3 (
|
@uilianries I don't want a debug swig build. |
@madebr interesting, because the original version (Conan Community) doesn't offer that option. Perhaps msvc runtime is wrong there and we need to remove. |
@uilianries Conan community's version does not have this problem, because the |
I think adding |
Some configurations of 'swig/4.0.1' failed in build 4 (
|
… avoid debug runtime)
All green in build 5 (
|
All green in build 6 (
|
recipes/swig/all/conanfile.py
Outdated
|
||
def package_id(self): | ||
# Verilator is a executable-only package, so the compiler version does not matter | ||
del self.info.settings.compiler.version |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
very interesting ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this recipe needs the same treatment as cmake: #1783
All green in build 7 (
|
return os.path.join(self.package_folder, "bin", "swiglib").replace("\\", "/") | ||
|
||
def package_info(self): | ||
# FIXME: Don't set cmake_find_package name because conan cmake generators do not define SWIG_EXECUTABLE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this <PKG-NAME>_EXECUTABLE
something standard in CMake? What happens if the sources provide more than one executable? Asking this just to know if it makes sense to add this as a feature in the CMake generators
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I's quite common:
SWIG_EXECUTABLE
: https://cmake.org/cmake/help/latest/module/FindSWIG.htmlPYTHON_EXECUTABLE
: https://cmake.org/cmake/help/latest/module/FindPythonInterp.htmlDOXYGEN_EXECUTABLE
: https://cmake.org/cmake/help/latest/module/FindDoxygen.htmlPERL_EXECUTABLE
: https://cmake.org/cmake/help/latest/module/FindPerl.htmlWGET_EXECUTABLE
: https://cmake.org/cmake/help/latest/module/FindWget.html
Also, some provide more than one _EXECUTABLE variable:
Java_JAVA_EXECUTABLE
Java_JAVAC_EXECUTABLE
Java_JAVAH_EXECUTABLE
... https://cmake.org/cmake/help/latest/module/FindJava.html
But there are exceptions:
HTML_HELP_COMPILER
: https://cmake.org/cmake/help/latest/module/FindHTMLHelp.html
Also, it would be interesting to provide these as targets:
Doxygen::Doxygen
Doxygen::dot
Doxygen::mscgen
Doxygen::dia
: https://cmake.org/cmake/help/latest/module/FindDoxygen.html
It is stated there that the_EXECUTABLE
variables are getting deprecated.
(but conan should provide these for the sake of compatibility)
Specify library name and version: swig/4.0.1
Ported from Bincrafters' recipe: https://github.com/bincrafters/conan-swig_installer
@rea-yseop Fixes bincrafters/community#1031 (please check)
@rea-yseop Fixes bincrafters/community#1174
conan-center hook activated.