Skip to content

Explicitly export exception types. - #332

Closed
oraluben wants to merge 1 commit into
osmcode:masterfrom
oraluben:export-exception
Closed

Explicitly export exception types.#332
oraluben wants to merge 1 commit into
osmcode:masterfrom
oraluben:export-exception

Conversation

@oraluben

@oralubenoraluben commented Jun 1, 2021

Copy link
Copy Markdown
Contributor

@codecov-commenter

codecov-commenter commented Jun 1, 2021

Copy link
Copy Markdown

Codecov Report

Merging #332 (81d16d9) into master (b263ba5) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@ Coverage Diff @@## master #332 +/- ##
=======================================
Coverage 79.25% 79.25% =======================================
Files 282 282 Lines 20712 20712 =======================================
Hits 16416 16416 Misses 4296 4296 
FlagCoverage Δ
data_tests56.50% <ø> (ø)
examples51.57% <ø> (ø)
unit_tests75.13% <ø> (-0.08%)⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted FilesCoverage Δ
include/osmium/geom/factory.hpp97.45% <ø> (ø)
include/osmium/geom/util.hpp100.00% <ø> (ø)
include/osmium/handler/check_order.hpp93.75% <ø> (ø)
include/osmium/index/index.hpp50.00% <ø> (ø)
include/osmium/index/map.hpp86.84% <ø> (ø)
include/osmium/io/error.hpp100.00% <ø> (ø)
include/osmium/memory/buffer.hpp74.27% <ø> (ø)
include/osmium/osm/item_type.hpp26.53% <ø> (ø)

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 b263ba5...81d16d9. Read the comment docs.

@oraluben

oraluben commented Jun 1, 2021

Copy link
Copy Markdown
ContributorAuthor

Working on CI failure.

I'm not able to reproduce the CI failures, would someone have any hint about what happened?

@joto

joto commented Jun 6, 2021

Copy link
Copy Markdown
Member

Looks to me like you probably didn't include the compatibility.hpp everywhere that's needed. For instance in include/osmium/memory/buffer.hpp.

@oraluben

Copy link
Copy Markdown
ContributorAuthor

Looks to me like you probably didn't include the compatibility.hpp everywhere that's needed. For instance in include/osmium/memory/buffer.hpp.

Thanks for your reply! They already included the file (e.g. in buffer.hpp), and I also successfully compiled the project. Is there anything different I should notice between local and the CI's environment?

joto added a commit to joto/gdalcpp that referenced this pull request Sep 25, 2021
@joto

joto commented Sep 25, 2021

Copy link
Copy Markdown
Member

I have merged this now (in slightly different form). Sorry it took so long, but I needed to understand what's happening here first.

@jotojoto closed this Sep 25, 2021
@joto

joto commented Sep 27, 2021

Copy link
Copy Markdown
Member

Because VS is generating warnings I wrapped the code defining OSMIUM_EXPORT into an #ifdef OSMIUM_DEFINE_EXPORT. So you have to compile with -DOSMIUM_DEFINE_EXPORT if you need this functionality. Can you provide a PR for Pyosmium if that works for you?

@oraluben

Copy link
Copy Markdown
ContributorAuthor

@joto thanks! I'll try to draft a PR there.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Test failure when build with libc++

3 participants

@oraluben@codecov-commenter@joto