Dear Rony I am very happy that it was useful Looking at the status of variable for complex cmakelists ( and I wrote a couple of them ) Is usually the only way to debug cmakelists errors
The vdump module was the first one I wrote a long time ago To get a better knowledge of the cmake ways Using cmake -G should have caused different errors IIRC It tells to cmake which generator is being used, ( I usually go with cmake -G Ninja … … … ) So I do not see why it should meddle with the compiler options I will push an update to include the proper defaults for the c / c++ compilers ( obviously the msvc stuff will empty ) Just look at the README, I posted two different CMakeLists A minimal and a platinum , the minimal does al that is needed with no frills Cheers E > On 18 Feb 2019, at 17:07, Rony G. Flatscher <rony.flatsc...@wu.ac.at> wrote: > > Also, *very* interesting (but to an extend overwhelming) the generated > "vars_for_main_at_9999.txt" file in the build directory! > >
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
