jmalak
commented
8 months ago Old discussion
crazii commented on Dec 26, 2023 • BTW I choose 16bit DOS only on setup, and there's no lh includes folder, only h But the owsetenv.sh script uses lh, and I changed it to h, I don't know whether it is relevant.
winspool commented 6 hours ago BTW I choose 16bit DOS only on setup, and there's no lh includes folder, only h But the owsetenv.sh script uses lh, and I > > changed it to h, I don't know whether it is relevant. The DOS folders are not enough for linux. I suggest to install everything.
jmalak commented 2 hours ago • You mix target and host setup. If you want DOS development on Linux host then you must install Linux host and target (tools and libraries and headers) and DOS target (libraries and header files). You can add any additional target by installer later. OW is installed always in default native configuration, that you should always install default (native host and target - installer default) and add other target which you will use. Probably I will need to change installer to not omit default host and > target to prevent such situation or warn user that do something non-standard. For cross-compilation you need always setup INCLUDE environment variable manualy or in make file. By example CMake requires default configuration to work with OW cross-compile stuff properly
Installer enable user to remove default host and default target installation. It is correct function, but for users without OW knowledge it causes problems later because thay don't change OW setup for such non-standard installation. it was reported in issue #1187 and I created this issue from original one because this problem is unrelated to the original issue.
Best solution looks like to do check for this situation and warn user that request something non-standard and it will require manual configuration.