OBX IDE under OpenBSD 7.0

[alexshendi]

Hi,

thanks for writing the OBX IDE. I have built the IDE under OpenBSD 7.0 (amd64 and arm64 platforms). But I've only had partial success. I proceeded as follows:

• Download packages and populate build directory as per README.md.
• Install Qt5 and Mono packages "pkg_add -v mono qt5"
• Go to "Oberon" directory: Execute "qmake-qt5 OBXIDE2.pro"
• (arm64 platform only) edit Makefile to add "-fsigned-char" to C and C++ compiler flags
• Execute "gmake CC=clang CXX=clang++"

I can the start the IDE. Editing code works (I only tried a simple "hello, world" module. Attempting to compile or run results in a crash and a core dump. Exporting to IL and C works, with these caveats:

• I can compile the C code by following the instructions in build.txt and substituting gcc with clang and adding compiler flags.
• For IL, the build directory contains run.sh and build.sh. These contain references to "./ilasm" and "./mono". Replacing these by plain "ilasm" and "mono" makes these scripts work.

Again, many thanks!

[rochus-keller]

Thanks for the feedback. The use of Mono is actually an implementation detail of the IDE, that's why a mono executable and the mscorlib.dll are included with the binary deployments, i.e. present in a subdirectory relative to the ObxIDE executable called "mono". I will add some more instructions to the readme. I usually take the mono-sgen executable from the mono build and rename it to "mono", and the biggest mscorlib.dll file the build generates (~5 MB). I tested it with Mono 5. Here are the precompiled x86_64 files just in case: http://software.rochus-keller.ch/mono_5.20.1.34_linux_x86_64.tar.gz. But you can of course also create links to these files in the "mono" subdirectory. If done so, you can run (CTRL+R) the Oberon+ program directly from within the IDE and also run the debugger. Note that if you execute the Compile menu command (CTRL+SHIFT+T) the IDE directly creates the CIL assemblies - with debug information if enabled - without separately running ILASM.

Do you really get a crash of the whole OpenBSD system when you run the assembly, or is just the mono executable crashing and reporting the issue to the IDE output pane?

[alexshendi]

Hi,

thank you for your fast response.

Just to clarify: OpenBSD doesn't crash, just the IDE.

I now did the following:

• cd ~/bin
• mkdir mono; cd mono
• ln -s /usr/local/bin/mono ./mono
• ln -s /usr/local/lib/mono/4.8-api/mscorlib.dll ./mscorlib.dll

(I had previously copied ObxIDE to ~/bin)

Now it works as advertised. Thanks, again!

Best Regards,

Alexander

Am 21. Dezember 2021 11:24:22 MEZ schrieb Rochus Keller @.***>:

Thanks for the feedback. The use of Mono is actually an implementation detail of the IDE, that's why a mono executable and the mscorlib.dll are included with the binary deployments, i.e. present in a subdirectory relative to the ObxIDE executable called "mono". I will add some more instructions to the readme. I usually take the mono-sgen executable from the mono build and rename it to "mono", and the biggest mscorlib.dll file the build generates (~5 MB). I tested it with Mono 5. Here are the precompiled x86_64 files just in case: http://software.rochus-keller.ch/mono_5.20.1.34_linux_x86_64.tar.gz. But you can of course also create links to these files in the "mono" subdirectory. If done so, you can run (CTRL+R) the Oberon+ program directly from within the IDE and also run the debugger. Note that if you execute the Compile menu command (CTRL+SHIFT+T) the IDE directly creates the CIL assemblies - with debug information if enabled - without separately running ILASM.

Do you really get a crash of the whole OpenBSD system when you run the assembly, or is just the mono executable crashing and reporting the issue to the IDE output pane?

-- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.