-
Notifications
You must be signed in to change notification settings - Fork 561
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
Unable to parse 3GPP TS 25.433 #119
Comments
Hi @velichkov Thanks for your response. How to resolve this issue? |
Try the version from pull request 99
My suggestion is to try first the pull request as described above. Also have a look at https://github.com/osmocom/osmo-iuh.git and http://www.moiji-mobile.com/2016/04/27/hnbap-and-ranap-support-in-osmocomorg/ |
Hi @velichkov Thanks. I cloned the source. Here I can't see some files for compile.
How to generate these files? |
Hi @velichkov I cloned by following. git clone https://github.com/vlm/asn1c.git Then entered to "asn1c" directory. Here, I run full request. git fetch origin pull/99/head:pr99 But I can't see some files as following.
How to generate these files? |
Hi @velichkov I fatched pr99 branch. After fatched, I compiled the source but I got other errors. Please check asn files, and compile error files. |
Hi @JohannesBakker, To generate the configure and Makefile files which meet your environment, please see INSTALL.md :
|
Hi @brchiu Thanks. Now I try to get C/C++ source file from asn1 file by using ASN1C that compiled with this source. Please check work_file.asn1.txt, compile-log.txt files. |
hi, @JohannesBakker In repository's commit 94f0b64 , your NBAP asn.1 can be parsed and C code generated. You can have a trial. Unfortunately, it broke up in newest repository acdca41 and I submitted #185 to track it. We might need to wait @vlm's available time to fix it. |
ASN.1 grammar parse error near line 1591 (token "id-C-ID"): syntax error, unexpected TOK_identifier, expecting '}'
Cannot parse "asn_work.asn1"
asn_work.asn1.txt
work.asn1"
The text was updated successfully, but these errors were encountered: