Re: Marshalling issue on Windows with DevLong64

> On 2023-03-28, 15:17, "Benjamin Bertrand via omniORB-list" <[email protected] <mailto:[email protected]>> wrote:
>
>
> Anyway, instead of spending time debugging the cmake build system, I'm trying to use the original one with:
> - Visual Studio 2019
> - GNU tools from conda-forge instead of Cygwin
> - python from conda-forge
>
>
> I enabled platform = x86_win32_vs_16 and set PYTHON = /c/Users/beenj/mambaforge/envs/omniorb/python
>
>
> When compiling I get this error:
>
>
> link -out:omnicpp.exe -nologo -manifest -DEBUG -MACHINE:X64 -PDB:omnicpp.exe.pdb -libpath:..\..\..\..\..\lib\x86_win32 cexp.o cccp.o config.o alloca.o index.o
> + mt.exe '/outputresource:omnicpp.exe;#1' /manifest omnicpp.exe.manifest
> Microsoft (R) Manifest Tool
> Copyright (c) Microsoft Corporation.
> All rights reserved.
>
>
> mt.exe : command line error c1010007: Unexpected/Unknown option "C:/Users/beenj/mambaforge/envs/omniorb/Library/manifest". Use the /? option for help on usage and samples.
> dir.mk:55: recipe for target 'omnicpp.exe' failed
>
>
>
>
> C:/Users/beenj/mambaforge/envs/omniorb is the path of the conda environment where the tools are installed, but I don't understand where it's coming from in the manifest tool command.
> Any idea how to fix this?

To follow-up on that, I finally managed to fix the issue (thanks Reynald!):

I had to replace "/manifest" with "-manifest" and "DUMPBIN.EXE /SYMBOLS" with "DUMPBIN.EXE -SYMBOLS", otherwise the "/" is replaced by the conda env path (not sure why - might be because of the ROOT env variable set to that path?).

With that build, the marshalling issue is gone.