Source files for vendored libraries#1156
Conversation
Current Aviator status
This PR was merged using Aviator.
See the real-time status of this PR on the
Aviator webapp.
Use the Aviator Chrome Extension
to see the status of your PR within GitHub.
|
|
Thanks. I'll review, can we discuss at around 16:00 if needed? |
Yes, sure. I trying to find a way to check that glpk in installed, but seems there is no straight forward solution. |
2aec3e7 to
0a2a6d6
Compare
| PKG_LIBS="$PKG_LIBS -lglpk" | ||
| else | ||
| echo "Using vendored GLPK" | ||
| PKG_CFLAGS="$PKG_CFLAGS -Ivendor/cigraph/vendor/glpk -Ivendor/cigraph/vendor/glpk/env -Ivendor/cigraph/vendor/glpk/minisat -Ivendor/cigraph/vendor/glpk/misc -Ivendor/cigraph/vendor/glpk/draft -Ivendor/cigraph/vendor/glpk/npp -Ivendor/cigraph/vendor/glpk/api -Ivendor/cigraph/vendor/glpk/mpl -Ivendor/cigraph/vendor/glpk/bflib -Ivendor/cigraph/vendor/glpk/amd -Ivendor/cigraph/vendor/glpk/simplex -Ivendor/cigraph/vendor/glpk/colamd" |
There was a problem hiding this comment.
-I flags should go in CPPFLAGS instead of CFLAGS, no?
There was a problem hiding this comment.
Need to define @cppflags below.
There was a problem hiding this comment.
Is this comment just about naming? As I understand it doesn't has functional meaning.
There was a problem hiding this comment.
We can leave it as is and resolve later if needed.
|
The PR has conflicts now. |
|
@Antonov548 is any help needed to fix the conflicts? |
I think it's better to start from scratch. Since part was already implemented in #1233 |
|
Ok so you want to close this PR and start a new one? I'm a bit lost as I don't know how you're generating the PR. (but I can learn!) |
Yes, I will create new one. Just need to clarify what still needs to be done regarding vendored libraries, since as I mentioned part is already done. |
b754a98 to
724985c
Compare
|
@krlmlr Seems it couldn't detect |
| PKG_LIBS="$PKG_LIBS -lglpk" | ||
| else | ||
| echo "Using vendored GLPK" | ||
| PKG_CFLAGS="$PKG_CFLAGS -Ivendor/cigraph/vendor/glpk -Ivendor/cigraph/vendor/glpk/env -Ivendor/cigraph/vendor/glpk/minisat -Ivendor/cigraph/vendor/glpk/misc -Ivendor/cigraph/vendor/glpk/draft -Ivendor/cigraph/vendor/glpk/npp -Ivendor/cigraph/vendor/glpk/api -Ivendor/cigraph/vendor/glpk/mpl -Ivendor/cigraph/vendor/glpk/bflib -Ivendor/cigraph/vendor/glpk/amd -Ivendor/cigraph/vendor/glpk/simplex -Ivendor/cigraph/vendor/glpk/colamd" |
There was a problem hiding this comment.
Need to define @cppflags below.
|
|
||
| generate_sources('/', 'sources', 'SOURCES', ignore_folders) | ||
| generate_sources('/vendor/cigraph/vendor/glpk', 'sources-glpk', 'GLPKSOURCES', [], ('.c', '.cc', '.cpp')) | ||
| generate_sources('/vendor/cigraph/vendor/mini-gmp', 'sources-mini-gmp', 'MINIGMPSOURCES') |
There was a problem hiding this comment.
No longer needed.
| generate_sources('/vendor/cigraph/vendor/mini-gmp', 'sources-mini-gmp', 'MINIGMPSOURCES') |
There was a problem hiding this comment.
Still needed here, but let's remove mini-gmp from ignore_folders in a separate PR.
| PKG_LIBS="$PKG_LIBS -lglpk" | ||
| else | ||
| echo "Using vendored GLPK" | ||
| PKG_CFLAGS="$PKG_CFLAGS -Ivendor/cigraph/vendor/glpk -Ivendor/cigraph/vendor/glpk/env -Ivendor/cigraph/vendor/glpk/minisat -Ivendor/cigraph/vendor/glpk/misc -Ivendor/cigraph/vendor/glpk/draft -Ivendor/cigraph/vendor/glpk/npp -Ivendor/cigraph/vendor/glpk/api -Ivendor/cigraph/vendor/glpk/mpl -Ivendor/cigraph/vendor/glpk/bflib -Ivendor/cigraph/vendor/glpk/amd -Ivendor/cigraph/vendor/glpk/simplex -Ivendor/cigraph/vendor/glpk/colamd" |
There was a problem hiding this comment.
We can leave it as is and resolve later if needed.
|
Oh, I missed. It's has errors in checking code rather than build the package. Can we try to avoid this issues with not including files which raise the warnings? |
|
@krlmlr is there any way to ignore warnings in vendor folder for the check step? P.S. still need to figure out why vendor version is chosen in GHA. |
|
@Antonov548: Turning off warnings for certain parts of the code will be difficult. @szhorvat: How did this even work with pre-2.0.0 without GLPK installed? Did Only CRAN is wary about these warnings, but they will never see them because they have GLPK installed. (Or so I hope.) We could just ignore those warnings on GHA, but we need multiple runs then: one with, and one without GLPK. |
It disabled GLPK. Do we need to care about R CMD check for anything except CRAN? CRAN has GLPK. We do turn off some warnings for the vendored GLPK with the C core's build system. It does use some outdated coding practices. GLPK has no issue tracker, not even a public repository. It is being developed the old-fashioned way on a GNU mailing list. I wouldn't take this up with upstream. |
|
I should point out that we go to great lengths to make sure that igraph doesn't print without permission. So the complaints about As for patching out all the |
|
@krlmlr I was wondering why on GHA it use vendored version of I found that the problem is in using I have changed it to use |
|
|
||
| generate_sources('/', 'sources', 'SOURCES', ignore_folders) | ||
| generate_sources('/vendor/cigraph/vendor/glpk', 'sources-glpk', 'GLPKSOURCES', [], ('.c', '.cc', '.cpp')) | ||
| generate_sources('/vendor/cigraph/vendor/mini-gmp', 'sources-mini-gmp', 'MINIGMPSOURCES') |
There was a problem hiding this comment.
Still needed here, but let's remove mini-gmp from ignore_folders in a separate PR.
7624a3e to
ab22467
Compare
Closes #1126.