x86 ? about armago_x64 HOT 25 CLOSED

Hi FairyTale5571,

Why do you still use a 32bit system ? I thought no one anymore use this.

For better understanding, how do you use also inidbi with appveyor ? :)

from armago_x64.

that sounds silly, but, u cant upload only x64 dll without x86 dll into the workshop) I tried build dll with appveyor, but he corrupted, idk why, just ask u, maybe u know how its correct work

from armago_x64.

and ye, i too not use x86 anymore )) workshop requires it from me

from armago_x64.

do you set on arma3 launcher the 64bits platforme support as default in parameters ?

from armago_x64.

No, u dont understood, i cant upload only x64 dll into my mod in steam workshop.
https://i.imgur.com/kdWgywE.png

from armago_x64.

i just added the 32bits version. Hope it will fix your problem

from armago_x64.

added where? )) Im not see )

from armago_x64.

Sorry, i thought you talked about another repository :(

for 32 bits version, you have to use a 32 bit compilator and another entrie point

Replace :
RVEXTENSION by _RVExtension@12

and do the same for other with thoses entries point:
_RVExtensionArgs@20
_RVExtensionVersion@8

from armago_x64.

It must bo replaced in go file?

from armago_x64.

i just check. In fact, normaly it should be something like this:

//export _RVExtension@12
func _RVExtension@12

Excepted that GO doesn't accept function name with "@" caracter and export command seems to not accept to translate the entry point like this:

//export RVExtension@12
func RVExtension

so i dont think there is simply solution for this perhaps you should ask to goland community. It seems to be a very old compatibility problem relative to arma convention name and c.

from armago_x64.

Got it. Close thread

from armago_x64.

how did you do ?

from armago_x64.

in no way, I will write to stack overflow, the meaning is to continue this issues if there is no solution at the moment.

from armago_x64.

ok then , i asked to gonuts:

https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/golang-nuts/RnGw1sx3vug/6zVj_q4JCAAJ

from armago_x64.

Maybe it help..
https://i.imgur.com/puZ1ZvC.png

from armago_x64.

it seems you can remove the @Number but i don't have a 32 bits compiler to test :(

from armago_x64.

I have, just drop me example )

from armago_x64.

try to rename the functions names like that

//export _RVExtension
func _RVExtension(output *C.char, outputsize C.size_t, input *C.char) {

from my part, it doesn't work. The entry point is not recognized

from armago_x64.

Nope, doesnt work

from armago_x64.

I am not very optimistic about this subject

from armago_x64.

yep, me now too

from armago_x64.

Hm, look this https://stackoverflow.com/questions/6125683/call-go-functions-from-c/6147097#6147097
or this https://play.golang.org/p/ajb4mD3ZrYG

from armago_x64.

there was the answer on gonuts concerning this problem:
https://docs.microsoft.com/en-us/cpp/build/reference/decorated-names?view=vs-2019

so Golang doesn't support the C decorated names that are required to use those kind of entry point.

Përhaps your last link could lead to something, but currently it doesn't compile
https://play.golang.org/p/ajb4mD3ZrYG

but i m not enough familiar with thoses concept, i don't understant if the dllexport macro permits to declare the decorated names that we have to specify or if it resolves itself the name.
https://docs.microsoft.com/en-us/cpp/cpp/dllexport-dllimport?view=vs-2019

if we have to declare ourself the decorated name with dllexport macri, the character are unsupport by golang.

from armago_x64.

Hello,

Isegal from Golang helped me to solve the problem.

You can find the 32 bits version on the 32bits branch :)
https://github.com/code34/armago_x64/tree/32bits

More information here, on how it was solved:
golang/go#32851

from armago_x64.

omg, its really work!

from armago_x64.