From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Tue, 18 Nov 2003 14:15:46 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 244 ************************************************** Monday 17 November 2003 Number 244 ************************************************** Subjects for today 1 RE: wxWindows : Dave Webster 2 wxWindows : John Poltorak 3 Re: std::min? : Dave and Natalie" 4 Re: wxWindows : Stefan Neis 5 Re: wxWindows : Stefan Neis 6 RE: wxWindows : Stefan Neis 7 Re: wxWindows : John Poltorak 8 Re: creating intl/Makefile : Dave and Natalie" 9 Re: wxWindows : Stefan Neis 10 Re: wxWindows : John Poltorak 11 Re: wxWindows : John Poltorak 12 GNU Info keymapping : John Poltorak **= Email 1 ==========================** Date: Tue, 18 Nov 2003 09:02:17 -0600 From: Dave Webster Subject: RE: wxWindows It is available via the wxWindows web site or you can get daily snapshots from CVS. Stefan has been making some modifications, but most development halted some time ago. It is available on OS/2, natively, using emx or VisualAge (may be Watcom as well, I'm not sure), or you can use the wxGtk(gcc) which is VERY robust if you are doing the Linux shell thingy under OS/2. 2.4 is still latest "stable" release, but there have been several 2.5.x "releases". See wxWindows.org for details. -----Original Message----- From: John Poltorak [mailto:jp at warpix.org] Sent: Tuesday, November 18, 2003 8:26 AM To: os2-unix at warpix.org Subject: wxWindows What is the current status of wxWindows and what should I do if I wanted to use it with gcc? -- John **= Email 2 ==========================** Date: Tue, 18 Nov 2003 14:25:58 +0000 From: John Poltorak Subject: wxWindows What is the current status of wxWindows and what should I do if I wanted to use it with gcc? -- John **= Email 3 ==========================** Date: Tue, 18 Nov 2003 15:00:18 -0800 From: "Dave and Natalie" Subject: Re: std::min? On Mon, 17 Nov 2003 11:21:26 EST, Andrea Venturoli wrote: >** Reply to note from "Dave and Natalie" Sun, 16 Nov 2003 09:58:10 -0800 > >> Shouldn't std::min be defined in -lgcc or somesuch? > >No, it should be a template and as such instantiated and compiled when/where you use it. > > > >> I am getting around this with a macro but it doesn't seem like an elegant solution > >It's not elegant at all and you'll get into problems sooner or later. > > > >> Menu.cc:355: no matching function for call to `min (unsigned int &, size_t)' > > ^^^ ^^^ > >Here is the problem. The definition should be something like: > >template std::min(const T&a,const T&b) {...} > >and you can see that both a and b must be of the same type. >In your example, however one is "unsigned int", the other is "size_t", so this template doesn't apply and you have no >other available. >Cast one of the two; e.g. change > >std::min(a,b) > >into something like (*) > >std::min(static_cast(a),b) Ok, this worked > >or > >std::min(a,static_cast(b)) > > > >(*) It's not guaranteed to work as I wrote it, the exact expression depends on your code (it might be "const size_t", >"size_t&", ...) > Actually its not my code but the code for Blackbox, a window manager and the code does compile on most *nixes. I wonder if size_t is different on *nix? Perhaps just a subset of integer? Anyways many thanx, I'll pas this upstream Dave **= Email 4 ==========================** Date: Tue, 18 Nov 2003 16:17:07 +0100 (CET) From: Stefan Neis Subject: Re: wxWindows On Tue, 18 Nov 2003, John Poltorak wrote: > What is the current status of wxWindows and what should I do if I wanted > to use it with gcc? wxWindows-2.4.2 has been released, if you download wxOS2, I _hope_ that the OS/2 specific configure files are already in place, if you download wxAll (or one of the X11 based ports), the OS/2 specific configure files are in docs/os2/os2-specific.zip. Unzip that and replace the Unix-specific configure scripts by the OS/2 aware ones. Read docs/os2/*.txt and set the environment variables as needed (MAKE_SHELL or MAKESHELL, depending on your make version and maybe INSTALL, depending on your path), then run "configure" and "make" and that's all - if you want just the lib. Running make in the samples directory should generate some/most of the samples, running make in an individual sample's directory generates just that sample. Warning: When you try to compile and run any samples, you'll notice that there are some problems with refresh of the application's windows (I fixed some minor problems but some major ones still remain). Secondly, File handling is rather heavily broken (Saving textfiles back to disk won't work and drive letter support is buggy...), I'm planning/hoping to fix it during the next weekend. Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 5 ==========================** Date: Tue, 18 Nov 2003 16:17:07 +0100 (CET) From: Stefan Neis Subject: Re: wxWindows On Tue, 18 Nov 2003, John Poltorak wrote: > What is the current status of wxWindows and what should I do if I wanted > to use it with gcc? wxWindows-2.4.2 has been released, if you download wxOS2, I _hope_ that the OS/2 specific configure files are already in place, if you download wxAll (or one of the X11 based ports), the OS/2 specific configure files are in docs/os2/os2-specific.zip. Unzip that and replace the Unix-specific configure scripts by the OS/2 aware ones. Read docs/os2/*.txt and set the environment variables as needed (MAKE_SHELL or MAKESHELL, depending on your make version and maybe INSTALL, depending on your path), then run "configure" and "make" and that's all - if you want just the lib. Running make in the samples directory should generate some/most of the samples, running make in an individual sample's directory generates just that sample. Warning: When you try to compile and run any samples, you'll notice that there are some problems with refresh of the application's windows (I fixed some minor problems but some major ones still remain). Secondly, File handling is rather heavily broken (Saving textfiles back to disk won't work and drive letter support is buggy...), I'm planning/hoping to fix it during the next weekend. Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 6 ==========================** Date: Tue, 18 Nov 2003 16:20:12 +0100 (CET) From: Stefan Neis Subject: RE: wxWindows On Tue, 18 Nov 2003, Dave Webster wrote: > under OS/2. 2.4 is still latest "stable" release, but there have been > several 2.5.x "releases". See wxWindows.org for details. IIRC, there was only an "unofficial" 2.5.0 release with 2.5.1 not yet released. BTW, I'm adding drive letter support to wxGTK/Motif/X11 on OS/2 for the next 2.5.x release. Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 7 ==========================** Date: Tue, 18 Nov 2003 16:27:29 +0000 From: John Poltorak Subject: Re: wxWindows On Tue, Nov 18, 2003 at 04:17:07PM +0100, Stefan Neis wrote: > On Tue, 18 Nov 2003, John Poltorak wrote: > > > What is the current status of wxWindows and what should I do if I wanted > > to use it with gcc? > > wxWindows-2.4.2 has been released, if you download wxOS2, I _hope_ that > the OS/2 specific configure files are already in place, if you download > wxAll (or one of the X11 based ports), the OS/2 specific configure files > are in docs/os2/os2-specific.zip. Unzip that and replace the Unix-specific > configure scripts by the OS/2 aware ones. I was wondering whether I could incorporate wxWindows into UX2BS as part of the basic toolset... > Regards, > Stefan > -- > Micro$oft is not an answer. It is a question. The answer is 'no'. > -- John **= Email 8 ==========================** Date: Tue, 18 Nov 2003 16:40:45 -0800 From: "Dave and Natalie" Subject: Re: creating intl/Makefile On Mon, 17 Nov 2003 14:57:16 +0000, John Poltorak wrote: > >If the option --without-included-gettext is specified for configure, >should intl/Makefile be created? I'd think so, if only because the main makefile will call intl/Makefile. It just shouldn't do anything. Try running make all in intl Dave **= Email 9 ==========================** Date: Tue, 18 Nov 2003 17:34:29 +0100 (CET) From: Stefan Neis Subject: Re: wxWindows On Tue, 18 Nov 2003, John Poltorak wrote: > I was wondering whether I could incorporate wxWindows into UX2BS as part > of the basic toolset... It's not that basic, IMHO. BTW, I'm currently running configure script on a different box with a rather incomplete toolset installed and get > # ../../configure --disable-gui > > Abnormal program termination > > Abnormal program termination > configure: WARNING: ac_executable_extensions not set, assuming .exe > configure: creating cache /dev/null > checking build system type... i386-pc-os2-emx (snipp) > checking for gcc... gcc > checking for C compiler default output... > Abnormal program termination > conftest.exe > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > Abnormal program termination > > checking for suffix of object files... > Abnormal program termination > > checking whether we are using the GNU C compiler... no > checking whether gcc accepts -g... no > checking for gcc option to accept ANSI C... none needed and as a result of the configure run, I get complete nonsense. Any idea which tool is missing to make configure happy? I'm lost... Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 10 ==========================** Date: Tue, 18 Nov 2003 18:45:12 +0000 From: John Poltorak Subject: Re: wxWindows On Tue, Nov 18, 2003 at 05:34:29PM +0100, Stefan Neis wrote: > On Tue, 18 Nov 2003, John Poltorak wrote: > > > I was wondering whether I could incorporate wxWindows into UX2BS as part > > of the basic toolset... > > It's not that basic, IMHO. > BTW, I'm currently running configure script on a different box with a > rather incomplete toolset installed and get > > # ../../configure --disable-gui > > > > Abnormal program termination > > > > Abnormal program termination > > configure: WARNING: ac_executable_extensions not set, assuming .exe > > configure: creating cache /dev/null > > checking build system type... i386-pc-os2-emx > (snipp) > > checking for gcc... gcc > > checking for C compiler default output... > > Abnormal program termination > > conftest.exe > > checking whether the C compiler works... yes > > checking whether we are cross compiling... no > > checking for suffix of executables... > > Abnormal program termination > > > > checking for suffix of object files... > > Abnormal program termination > > > > checking whether we are using the GNU C compiler... no > > checking whether gcc accepts -g... no > > checking for gcc option to accept ANSI C... none needed > > and as a result of the configure run, I get complete nonsense. > Any idea which tool is missing to make configure happy? I'm lost... Which version of autoconf produced configure? Are you using an existing configure script or one which you generated? > Regards, > Stefan > -- > Micro$oft is not an answer. It is a question. The answer is 'no'. > -- John **= Email 11 ==========================** Date: Tue, 18 Nov 2003 19:28:46 +0000 From: John Poltorak Subject: Re: wxWindows On Tue, Nov 18, 2003 at 04:17:07PM +0100, Stefan Neis wrote: > On Tue, 18 Nov 2003, John Poltorak wrote: > > > What is the current status of wxWindows and what should I do if I wanted > > to use it with gcc? > > wxWindows-2.4.2 has been released, if you download wxOS2, I _hope_ that > the OS/2 specific configure files are already in place, if you download > wxAll (or one of the X11 based ports), the OS/2 specific configure files > are in docs/os2/os2-specific.zip. Unzip that and replace the Unix-specific > configure scripts by the OS/2 aware ones. I have just downloaded wxBase-2.4.2 and wxOS2-2.4.2 for comparison and wonder whether I would be able to use the former to build wxWindows... They have the same configure.in and Makefile.in. > Regards, > Stefan > -- > Micro$oft is not an answer. It is a question. The answer is 'no'. -- John **= Email 12 ==========================** Date: Tue, 18 Nov 2003 23:16:50 +0000 From: John Poltorak Subject: GNU Info keymapping I asked about keyboard mapping with GNU Info a few weeks back, but no one seemed to know how it was done. Now looking through the app again, it looks like the utility INFOKEY can be used to set things up the way I want. If only I knew how to use it... Does anyone have a ~/.infokey that I can have a look at? -- John