-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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 doxygen #2135
Add doxygen #2135
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Need a review and help here. |
That's unfortunate. Sounds like we may have a bug in |
I think cmake is good. When flex and bison are listed in build reqs, they are installed and cmake finds them. If not listed as build req, it cmake finds the system ones on Mac and fails to find them on Linux. But, when they are installed via yum_requirements.txt, then cmake finds them. IMO, problem is with conda-forge's flex and/or bison. Not sure when I can dig up the logs and report on flex and bison feedstocks. |
Or, I could demonstrate the problem here in this PR. Would you rather keep this PR clean and merge it as is, maybe? The failure on Appveyor is another story. conda-build complains about the license. So, I just skipped Windows, but it is still built. I am not sure if that is, yet another problem. So, we got a stack of problems in our hands here. 😜 |
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/doxygen:
|
-DCMAKE_INSTALL_PREFIX=$PREFIX \ | ||
-DCMAKE_BUILD_TYPE=Release \ | ||
.. | ||
make -j |
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.
Please add $CPU_COUNT
if you wish to build in parallel.
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.
Not building in parallel. Done.
- vc14 # [win and py35] | ||
|
||
requirements: | ||
build: |
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.
Needs python
as a build requirement on Windows for features to work.
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.
And if want to skip Windows, should I remove features? Or can they stay for future use?
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.
They can stay. Just suggesting we get all the pieces in place.
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.
Done.
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.
Thanks.
|
||
test: | ||
commands: | ||
- test -f "${PREFIX}/bin/doxygen" # [not win] |
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.
Couldn't we just run doxygen --help
and drop the selector?
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.
Done.
- test -f "${PREFIX}/bin/doxygen" # [not win] | ||
|
||
about: | ||
home: http://www.stack.nl/~dimitri/doxygen/index.html |
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.
Please add license
. It looks like it is GPL2.
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.
What is the license_family?
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.
That's optional. Sadly it is also GPL2 so a bit redundant. Would skip it if I were you.
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.
Done.
The license complaint is valid. So that needs to be addressed. I'd really like to understand the issues with |
Only Windows complains, the rest passes though. I'll add GPL2 for license field as you suggested. |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Mac and Linux fail with this message: |
How about updating test 12 using |
I can't follow the code. What is it supposed to do? |
Here's a brainteaser for you. Why does pinning conda-build to 2.0.12 fix builds? I'm pretty sure, I saw successful builds with 2.1 in this PR, but after some point things started getting weird. I'm giving up for now. 😩 😫 |
It will first update the test 12 with the output from doxygen. python runtests.py --updateref --id 12 --inputdir=testing
make tests |
@@ -19,7 +19,7 @@ conda install --yes --quiet conda-forge-build-setup | |||
source run_conda_forge_build_setup | |||
|
|||
# install conda-build 2.x to build with a long prefix | |||
conda install --yes --quiet conda-build=2 | |||
conda install --yes --quiet conda-build=2.0.12 |
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 don't think this repo is using conda-build=2, even though that line is there. Previously it was downgraded to 1.21.
The following packages will be DOWNGRADED due to dependency conflicts:
conda-build: 2.1.0-py35_0 defaults --> 1.21.14-py35_0 defaults
When pinned to 2.0.12 instead of 2, it actually works.
cc @ocefpaf
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.
That was a mistake, it was downgraded and then upgraded.
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.
Yeah, that's happening when running source run_conda_forge_build_setup
. This line is after that so it shouldn't matter what conda-forge-build-setup
does.
I couldn't find a build log with conda-build 2.1 that worked. |
You're right, I can't find any either. So, I guess, it is safe to say that conda-build 2.1 breaks things here, but 2.0.12 is OK? |
Yes, it's strange though that 2.1 breaks stuff. I've managed to compile with 2.1 by adding, |
It is very possible there is a bug or at least an unexpected change of behavior. Could you guys please raise an issue on the |
This seems to be a bug in doxygen and the bug was hidden in |
shadowwalkersb/staged-recipes#2 |
FindIconv.cmake patch
@isuruf , would you be interested in being a maintainer? Maybe, even the only maintainer? |
Sure, I can help with maintaining |
To be clear, if you don't mind, I'll remove myself. |
@jakirkham , @isuruf played it nicely, and kindly fixed CMakelLists, but I just removed the problematic part from CMakeLists. Even if it works, please, let me know if you want me to back out my changes. Considering @isuruf is going to be the only maintainer, it may be better to go with his solution, but I still wanted to put it out there. 😉 |
I, just, need a final confirmation that the license is GPL2, please. |
Yes, it's GPL2. Btw, there was a new release doxygen-1.8.13 after this PR was open. |
Ready to merge now. |
Thanks all! |
Closes #1733 .