-
Notifications
You must be signed in to change notification settings - Fork 180
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
Support of Cygwin #110
Comments
Thanks for the report. I admit I never tested with Cygwin, but I'll look into it. |
Cygwin should now work. I set up Cygwin on a VM and got the tests and examples to build and the tests where run successful. Still I would call Cygwin support preliminary as I'm not using it myself and I currently don't have the resources to do the research on how to add Cygwin support to the Appveyor CI configuration. Without CI support I wouldn't dare to call it officially supported. If anyone knows enough about that to manage this, PRs are welcome. 😉 Still, it works and I'll support it in the way that I look into bugs found on that platform and try to fix them. |
Thanks that is fast!! In the README.md I read it is possible to run some tests, but it is not clear how to run the tests. I followed the
Regarding Appveyor and Cygwin, unfortunately I have no experience with it, it looks like Appveyor is supporting the recent version of Cygwin (3.1.7) so it should be possible. |
Compiling the tests on Cygwin with GCC 10.0.2 gives me some warning / information messages:
Cmake generation information:
|
You are welcome, as a long time Doxygen user I am happy to be able to give something back. 😄
That is great.
Yeah, I should make that more clear. The
When building for Visual Studio or Xcode, the CMake configuration needs to be given (case is significant):
I was able to run those on my Cygwin Environment without errors.
Yeah, I expect my Travic-ci.org pipeline to stop working any week, but as long as it works and I don't migrate |
These warnings are actually in a way part of the test. The issue is, that |
I just ran the tests, no problems (203 tests on Cygwin, 270 on Windows). Besides starting the tests by means of |
This is now part of release v1.5.4 |
Describe the bug
Under Cygwin filesystem does not compile.
For doxygen an easy fix was possible by changing the line
into
though when applying this fix to the official repository and running
make
to check the tests we get:To Reproduce
Expected behavior
Official support for Cygwin
Additional context
Used GCC version: gcc (GCC) 10.2.0
The text was updated successfully, but these errors were encountered: