I tried again in Win 10 and LV 2020 and first went to Tools -> Advanced -> Clear Compiled Object Cache and then closed LV and cleaned the cache with the attached batch file (I changed the file extension to be able to attach it). The EXE built fine in LV 2020. Could you try it with LV 2020 please? My guess is the OS doesn't matter. I've attached the project saved in LV 2020 format.
It doesn't surprise me as the VIM isn't a friend of Lib 1
I think you meant Lib 2 (which has the Community Enum Type Def.)
Functionally, I wouldn't expect this to work at all. VIMs function like VIs with some trickery, but community scoping would break with any other subVI call that isn't a friend.
In Win 11 and LV 2022, I tried making the the Enum to Array of Enums.vim a friend of Lib 2 but it still won't build the EXE. Note: when I open the Add friend file explorer dialog it doesn't list VIMs, I have to allow the listing of all files. But if I save a copy of the VIM, change the file extension to .vi, keep the inlining, and manually swap the controls/indicators on the new VI for the Community Enum Type Def., then add this new VI as a friend of Lib 2, the EXE builds.
I can understand why LV implantation wise this might not be allowed: behind the scenes, the VIM gets replaced with a VI whose controls and indicators have their data types based on the input data types the VIM was called with. If I were to literally do that, I would expect it to NOT compile (in both debug mode or the EXE). However, VIMs are required to be inlined. My understanding of inlining is that at compile time the content of the inlined VI is dropped on the block diagram of the calling VI. If that is done literally, then the VI *where the code ends up is a friend of Lib 2*. Ok, I can see why an API designer might want to control if inlined VIs shouldn't be allowed to do this though.
I should be able to just make the VIM a friend of Lib 2 then right?
