Skip to content
This repository has been archived by the owner on Sep 3, 2022. It is now read-only.

Is the inclusion of int vasprinf() ambiguous? #7

Open
scimad opened this issue Nov 7, 2019 · 1 comment
Open

Is the inclusion of int vasprinf() ambiguous? #7

scimad opened this issue Nov 7, 2019 · 1 comment

Comments

@scimad
Copy link

scimad commented Nov 7, 2019

In g2o/stuff/os_specific.c, the function int vasprintf() is defined within #ifdef WINDOWS, whereas the prototype definition at os_specific.h is within nested #ifdef WINDOWS and #ifndef _WINDOWS.

Is it an intended code?

Also, just to make sure,as documented in README.md, in step 5 of g2o, it says to add WINDOWS to prepossessor definitions. Is it WINDOWS and not _WINDOWS?
@Devilloong
Copy link

WINDOWS

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@scimad @Devilloong