builder,cgen: fix msvc build filename, remove temp files

[kbkpbot]

1. Partially fix issue Create .dll under Windows will result in strange filename. #23888 . If user specify a output name other than .exe or .dll, the output name will be appended with .exe or .dll;
2. Remove msvc generate temp files.

[huly-for-github]

Connected to Huly®: V_0.6-22293

[kbkpbot]

wait a moment, try fix issue #6983

[kbkpbot]

wait a moment, try fix issue #6983

As tcc doesn't has a method that change an export function's name, so my suggestion is not use the @[callconv: stdcall].

msvc can use a .def file change the export function's name, so it can use @[callconv: stdcall].

[spytheman]

Excellent work.

[Ekopalypse]

wait a moment, try fix issue #6983

As tcc doesn't has a method that change an export function's name, so my suggestion is not use the @[callconv: stdcall].

msvc can use a .def file change the export function's name, so it can use @[callconv: stdcall].

@kbkpbot
I don't understand what the calling convention has to do with the exported function names?
Regarding vlang of course.

[JalonSolov]

In V, names are usually exported as <module name>__<function name> for normal functions, <module name>__<struct name>_<receiver method name>, etc. This is very similar to the name mangling that C++ does for symbols.

So if you want a specific name for external things to call, you need to export said specific name, instead of others having to figure out the naming scheme.

[Ekopalypse]

So does this mean that there is no longer an export attribute?
Afaik, a calling convention does NOT only define what names should be, but above all how they are called and how parameters are passed or handled.