Skip to content
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

Initial commit of doxy2swig #101

Closed
wants to merge 3 commits into from
Closed

Conversation

mattbement
Copy link

Following the pattern of PyTrilinos, creating a Doxygen directory which will eventually hold .i files for the wrapped packages. This directory also holds the doxy2swig python script, which has been slightly modified to warn that .i files it produces are auto-generated.

@codecov-io
Copy link

codecov-io commented Nov 16, 2017

Codecov Report

Merging #101 into develop will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop     #101   +/-   ##
========================================
  Coverage    25.11%   25.11%           
========================================
  Files           33       33           
  Lines        13574    13574           
========================================
  Hits          3409     3409           
  Misses       10165    10165

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8db57b5...6492862. Read the comment docs.

Copy link
Collaborator

@aprokop aprokop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets postpone this until we are sure that doxy2swig is the way to go. We need to figure out what's in swig/swig doxygen branch, and whether we should use that instead.

@aprokop
Copy link
Collaborator

aprokop commented Nov 28, 2017

Fix #80 when merged.

@mattbement mattbement closed this Nov 30, 2017
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants