8000 downstream visibility of -DZXING_EXPERIMENTAL_API · Issue #964 · zxing-cpp/zxing-cpp · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
downstream visibility of -DZXING_EXPERIMENTAL_API #964
Closed
@tonycoz

Description

@tonycoz

Hi,

I've been updating my perl wrapper for zxing-cpp and in general it works.

Unfortunately if I build zxing-cpp 2.3.0 with -DZXING_EXPERIMENTAL_API my barcode reader tests fail, either with a segmentation fault or a double free.

After a fair amount of debugging it seems like the types I see in my calling code are different to the types seen in the library presumably due to the class layout changes that ZXING_EXPERIMENTAL_API causes.

If I manually define ZXING_EXPERIMENTAL_API when building my code things work - but I don't see a way to detect that manually, the macro is defined neither in zxing.pc nor in Version.h.

Is there another way downstream users should be able to check whether the library was built with ZXING_EXPERIMENTAL_API?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0