build about c-for-go HOT 5 OPEN

.\zycore.go:1577:2: could not determine kind of name for C.hello

it looks like tt/library.h is not part of the includes for #cgo directives in the generated package. Make sure to include headers under generator. Includes config path, it lists headers to include after generating files. Also, generator.FlagGroups allows you to set CFLAGS that specify include dirs as well.

See proper example https://github.com/xlab/portmidi/blob/a2cf51204affa3600b0e6e15c7174cd5cbde463b/pm.yml#L6-L8

If you set that as part of the generator config, it will be used in all generated files and sometimes that's not desired behavior. An alternative might be to manually create a file that includes all proper headers, example

from c-for-go.

Plus check out the official docs on cgo

https://go.dev/blog/cgo
https://pkg.go.dev/cmd/cgo

While generator does boilerplate, some things require to get hands dirty and that requires some knowledge.

from c-for-go.

Plus check out the official docs on cgo

https://go.dev/blog/cgo
https://pkg.go.dev/cmd/cgo

While generator does boilerplate, some things require to get hands dirty and that requires some knowledge.

Hello, I copied the header file to the go file output directory according to your prompt, and then imported the header file, and the result was still the same. Finally, I deleted the functions other than the hello function and ran successfully, but it was not safe and could not bind those libraries in batches. So can you generate yaml files for the libraries I mentioned above to be bound? I can check from your yam file whether there is any problem with the configuration I generated, and it would be better to export the function. If possible, xed zydis can choose any one. Thank you. Reame doesn't seem to have more examples to explain the usage of each rule, except that each warehouse has a yaml file. As long as one of the libraries is successfully bound, I believe I can complete the binding of other libraries with your help. I need your help. Thank you, teacher.

from c-for-go.

I get it, so, you need to just create file manually including other lib's header files.

from c-for-go.

i found the reason is cgo not supported msvc

from c-for-go.