Hi, with the latest version fesapi-2.12.2.1 I have made sure to set -DWITH_DOTNET_WRAPPING=ON in my configuration and also see that it is ON in the CMakeCache.txt but the build and install goes through and I get the FesapiCpp dll only but nothing for the FespaiCs. Any idea what am I doing wrong? Even when I launch the Fesapi VS solution I don’t see the option to build cs (it is not listed as one of the projects).
OK I think I might have got the answer to this. Is probably related to the SWIG_LINKED_TO_RELEASE variable since I was configuring/building debug C++ target so maybe it couldn’t find a release target and hence skipped. So guess I need to set that ON/OFF depending on whether I am building debug/release C++ target. Going to try that to confirm now.
Edit #1: So I tried the above and it didn’t work as I hoped. I still don’t see the C# target DLLs built for debug configuration. Not sure where I am going wrong or what else to try. Any ideas are appreciated. Going to try release now.
Edit #2: So I tried release as well and same, still don’t get the C# target DLL. Appreciate any help.
Edit #3: I loaded the *.csproj into a new VS instance and built it and seems to have generated the C# DLL, but not sure if thats the intended way. Anyway will plan to test it in due course.
Hi Sunil,
The FESAPI CS project is generated into fesapi/cs at master · F2I-Consulting/fesapi · GitHub as fesapiCs.csproj at build time.
The sources are generated in fesapi/cs/src at master · F2I-Consulting/fesapi · GitHub still at build time.
An example is provided to show how you could use this generated project into your own solution : fesapi/cs/example at master · F2I-Consulting/fesapi · GitHub
Finally, the CI also shows how to run it with command lines : fesapi/.github/workflows/github-actions.yml at 10514af2b4d544adc809883b484587b8fb902eee · F2I-Consulting/fesapi · GitHub
I always wanted to improve that, especially by delivering a nuget package, but I always lack time.
1 Like