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

wmain: build as c++ instead of c #2453

Merged
merged 1 commit into from
Jan 4, 2023
Merged

wmain: build as c++ instead of c #2453

merged 1 commit into from
Jan 4, 2023

Conversation

neheb
Copy link
Collaborator

@neheb neheb commented Jan 4, 2023

Allows to keep exiv2 c++ only.

Signed-off-by: Rosen Penev [email protected]

Allows to keep exiv2 c++ only.

Signed-off-by: Rosen Penev <[email protected]>
@codecov
Copy link

codecov bot commented Jan 4, 2023

Codecov Report

Merging #2453 (70e5867) into main (f981c51) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2453   +/-   ##
=======================================
  Coverage   62.10%   62.10%           
=======================================
  Files         122      122           
  Lines       22937    22937           
  Branches    11244    11244           
=======================================
  Hits        14245    14245           
  Misses       6475     6475           
  Partials     2217     2217           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Copy link
Collaborator

@piponazo piponazo left a comment

Choose a reason for hiding this comment

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

LGTM! Was this the last .c file in the project? In that case we need to also review the CMake code to make sure that we remove additional support/checks for C files.


args = HeapAlloc(heap, 0, nbytes);
args[0] = (char*)(args + argc + 1);
args = reinterpret_cast<char**>(HeapAlloc(heap, 0, nbytes));
Copy link
Collaborator

Choose a reason for hiding this comment

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

[question] I am just curious about this. Was this producing some warnings with some compilers? Is this about a recommendation suggested by clang-tidy?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

The latter. Wonder why double pointer now...

Copy link
Collaborator Author

@neheb neheb Jan 4, 2023

Choose a reason for hiding this comment

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

Ah nvm. The issue here is that C++ is stricter when it comes to pointers. eg, you always need to cast malloc.

@neheb neheb merged commit a84df11 into Exiv2:main Jan 4, 2023
@neheb neheb deleted the 4 branch January 4, 2023 22:17
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.

2 participants