fastLink | R package fastLink : Fast Probabilistic Record Linkage | Data Manipulation library

The missing symbol is part of the C runtime. Try adding vruntime.lib to your link line, or linking with the MSVC linker (link.exe) instead.

Assuming you have objects called pruebaA_df1, pruebaA_df2 .... pruebaA_df1000 in your environment, you can use Reduce as :

So I can't take credit for this. I'm only posting answer so we can close this question. But the issue was with the portaudio library itself The portinfo.def file was not exporting the method that I was trying to call - the method referenced in the example file.

the fix was to add the following line to the portinfo.def file:

Pa_GetVersionInfo @ 69

Now my client / console app compiles. I will submit a patch later today to portaudio repo for the community to consider. But thanks to @HansPassant and πάντα ῥεῖ

Calling external exe's/cmd's via PowerShell requires specific attention. It is a well-documented thing.

See these details from Microsoft and others: ---

PowerShell: Running Executables

1. The Call Operator &

It's partly correct. The actual requirements here are fair bit more complex and partly contradictory. For x86 targets, the calling convention used by the actual entry point code doesn't matter for executables, but needs to use the stdcall calling convention for DLLs. However, on x86 targets, the name passed with the /ENTRY option is automatically decorated as if it were a function following the cdecl calling convention, regardless whether an executable or DLL is being built.

On x64 and ARM targets there isn't actually a stdcall calling convention so there's no special requirements and no inconsistency. The entry point code should follow the standard cdecl convention for these targets, and the name passed with the /ENTRY option isn't decorated.

In the case of an executable, the entry point is called without arguments and so both the cdecl and stdcall calling convention are equivalent and so either can be used for the entry point code. In the case of a DLL, the entry point is called with three arguments, the same arguments passed to DllMain, and these arguments are passed using the stdcall calling convention. On x86 targets, a DLL's entry point code should pop these arguments using a ret 12 instruction when returning.

On x86 targets (and not x64 and ARM targets) the /ENTRY linker option automatically prefixes the the symbol passed with an underscore _, following the cdecl convention for symbol names. It doesn't add the stdcall @## suffix, even if you're building a DLL. It will then fuzzy match this symbol against the symbols in the code being linked. If you use /ENTRY:foo then it will first try to find a symbol named _foo, and if it doesn't find it, it will look for a symbol named foo or one starting with _foo@ or foo@.

Note, because you're using .MODEL flat, C in your example code MASM will automatically prefix the symbol main defined in your code with an underscore _, following the x86 cdecl calling convention. Conveniently, this matches the behaviour of /ENTRY as described above. However, it's not the best idea to name your entry point main as this would imply that it's supposed to be the C function of the same name. Since your entry entry point doesn't get passed arguments, but the C function main does it can be misleading to call your entry point main. I'd suggest naming it start instead.

Finally the .STACK directive does nothing useful when building 32-bit or 64-bit PECOFF programs. It's only useful when creating 16-bit programs.

I think I figure it out, I should write this in the if(IOS) statement range, so I write my CMakeLists like this, it goes well.