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.

Sign up for GitHub

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

Jump to bottom

Builder fails to parse declaration const char* const A("s"); #179

Closed
jpsacha opened this issue May 6, 2017 · 6 comments
Closed

Builder fails to parse declaration const char* const A("s"); #179

jpsacha opened this issue May 6, 2017 · 6 comments
Labels
bug

Comments

@jpsacha
Copy link
Member

jpsacha commented May 6, 2017

Basler Pylon library 5.0.5 is using declaration

const char* const ManufacturerInfoKey("ManufacturerInfo");

JavaCPP Builder fails while parsing header file with that line. Complete header file is attached. The actual error message:

Failed to execute goal org.bytedeco:javacpp:1.3.3-SNAPSHOT:build (javacpp.parser) on project pylon: 
Failed to execute JavaCPP Builder: C:\Program Files\Basler\pylon 5\Development\include\pylon\DeviceInfo.h:50: 
Could not parse declaration at '='

DeviceInfo.h.zip
@saudet saudet added the bug label May 12, 2017
saudet added a commit that referenced this issue May 14, 2017
@saudet
Fix bugs in Parser
b5378cf 
 * Fix `Parser` incorrectly recognizing values as pointers when `const` is placed after type (issue #173)
 * Add `Parser` support for C++11 `using` declarations that act as `typedef` (issue #169)
 * Let `Parser` accept variables initialized with parentheses (issue #179)
 * Fix `Parser` confusion between attributes and namespace-less templates (issue #181)
@saudet
Copy link
Member

saudet commented May 17, 2017

This should be fixed with the commit above. Let me know if you still have issues! Thanks

@jpsacha
Copy link
Member Author

jpsacha commented May 18, 2017

Unfortunately I am still getting the same error with latest (5/14) javacpp.

@saudet
Copy link
Member

saudet commented May 18, 2017

Might be because of PYLONBASE_API. Is it properly "ignored"?

@jpsacha
Copy link
Member Author

jpsacha commented May 20, 2017

It is ignored with

new Info("PYLONBASE_API").cppTypes().annotations().cppText("")

Current version of presets on branch wip/pylon

saudet added a commit that referenced this issue May 28, 2017
@saudet
* Fix Parser error on member variables with initializers plus `Inf…
c6760df 
…o.skip()` (issue #179)
@saudet
Copy link
Member

saudet commented May 28, 2017

Thanks, it's fixed now! The issue was only happening with Info.skip().

@saudet
Copy link
Member

saudet commented Jul 27, 2017

Fix released in version 1.3.3. Thanks for reporting!

@saudet saudet closed this as completed Jul 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jpsacha @saudet