How about everblue?valerius wrote: Regarding BFE, I can try to compile it for XFree86/OS2 with GTK1. I have XFree86 installed, so, the BFE can be useful. But must we rely on optional features, like XFree86/OS2? I don't know. But XFree86 version may be useful.
As I saw in ReginaREXX sources, there was a rexxutil library for it, and, if I remember correctly, there was a mention of external libraries in Regina manual. (It can be downloaded from Regina page at SourceForge).osfadmin wrote:Hm.. I'll check this, but IBM Classic REXX allow to reuse external.Viking wrote: A question is: what languege to write it in? ReginaRexx seems to limited (it does not support reusable modules in Rexx, only external compiled code).
Wsh or Wish? Do you mean windowing shell for Tcl/Tk or something else? Please explain what means "common API but different languages".osfadmin wrote:I don't like idea to use not REXX language. I have idea to build something like WSH, but more usable. I mean common API but different languages. Such approach allow us not limit ourself in preffered language.Viking wrote: Maybe Python. I would prefer Perl, but maybe it's not suited for this (to big runtime, not easy to read source code). Anyone has any suggestions?
It may help, we can try it.osfadmin wrote:How about everblue?valerius wrote: Regarding BFE, I can try to compile it for XFree86/OS2 with GTK1. I have XFree86 installed, so, the BFE can be useful. But must we rely on optional features, like XFree86/OS2? I don't know. But XFree86 version may be useful.
There is also REXX/Tk, as I heard, it is similar to Tcl/Tk. But I didnt tried them both.osfadmin wrote: Ok. I propose following toolset for "installer" and "configurer" of build environment:
- REXX as portable code
- ReginaREXX on Windows
- ClassicRECC on OS/2
- ReginaREXX on Linux
- REXX/DW as GUI library. It is presented for all 3 platforms
Can you give a link to 2. and 3. ?osfadmin" wrote: 3. REXX/Trans for REXX interpreter interaction.
Why not Magpie - it seems to be commonly used with scons/Kenge/Iguana. You was considering to use these tools, didnt you? But again, we dont know the set of needed features yet.osfadmin wrote: 7. IDL4 as L4 IDL Compiler
I'm not about external libs with SAA interface. I'm about external modules (like in Perl, for example)valerius wrote:As I saw in ReginaREXX sources, there was a rexxutil library for it, and, if I remember correctly, there was a mention of external libraries in Regina manual. (It can be downloaded from Regina page at SourceForge).osfadmin wrote:Hm.. I'll check this, but IBM Classic REXX allow to reuse external.Viking wrote: A question is: what language to write it in? ReginaRexx seems to limited (it does not support reusable modules in Rexx, only external compiled code).
Windows Scripting Host. According API: I mean we can try to use REXX SAA API for use any scripting language not REXX only.valerius wrote:Wsh or Wish? Do you mean windowing shell for Tcl/Tk or something else? Please explain what means "common API but different languages".osfadmin wrote:I don't like idea to use not REXX language. I have idea to build something like WSH, but more usable. I mean common API but different languages. Such approach allow us not limit ourself in preffered language.Viking wrote: Maybe Python. I would prefer Perl, but maybe it's not suited for this (to big runtime, not easy to read source code). Anyone has any suggestions?
valerius wrote:There is also REXX/Tk, as I heard, it is similar to Tcl/Tk. But I didnt tried them both.osfadmin wrote: Ok. I propose following toolset for "installer" and "configurer" of build environment:
- REXX as portable code
- ReginaREXX on Windows
- ClassicRECC on OS/2
- ReginaREXX on Linux
- REXX/DW as GUI library. It is presented for all 3 platforms
If we have a plan to use Pistachio then we need IDL4 because other compilers not support X.2 API (or I'm wrong?)valerius wrote:Can you give a link to 2. and 3. ?osfadmin wrote: 3. REXX/Trans for REXX interpreter interaction.
Why not Magpie - it seems to be commonly used with scons/Kenge/Iguana. You was considering to use these tools, didnt you? But again, we dont know the set of needed features yet.osfadmin wrote: 7. IDL4 as L4 IDL Compiler
I don't know any other gui frontends for Bochs. But I have been trying to write a simple GTK porting layer (for BFE) for a gui toolkit, FLTK (it does not have a port for OS/2, though), mostly for fun. FLTK is a very small library.valerius wrote: But current OS/2 bochs versions are SDL (or DIVE?) ones. And XFree86/OS2 versions are too old... Unfortunately, there is no PM version of GTK, but there is a PM version of QT. Do you know of QT frontends for Bochs debugger?
Well, no. I was at the moment a bit lazyosfadmin wrote:Is it problem to set executible bit?Viking wrote: That sounds interesting. So, should I write the build instructions for Linux? It was a bit messy to get it working. I compiled Open Watcom in windows (the Linux version) and copied the executable files to the Linux partition (I could not run the compiler, because the files did not have (executable) "x" bit set). OW can be compiled with GCC, at least it said so in the documentation.
A better solution would have been to change the options in fstab which mounts the NTFS partition. So that every file is treated as having the executable bit set. And then just umount and remount it. At least I think so. It was a while I looked at the doc for mount.