From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Wed, 24 Jul 2002 04:33:20 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 282 ************************************************** Tuesday 23 July 2002 Number 282 ************************************************** Subjects for today 1 Re: Using YACC when building FLEX : Thomas Dickey 2 Re: Using YACC when building FLEX : Thomas Dickey 3 Re: Building FLEX requires flex.exe : Thomas Dickey 4 Re: Perl Building : Edwin =?iso-8859-1?Q?G=FCnthner?= 5 wxWindows : Dave Webster 6 RE: wxWindows : Dave Webster 7 Re: Saving parameter to listfile : John Poltorak 8 Using YACC when building FLEX : John Poltorak 9 RE: wxWindows : Dave Webster 10 Re: Using YACC when building FLEX : John Poltorak 11 regex.c : John Poltorak 12 Re: wxWindows : Henry Sobotka 13 Re: wxWindows : tstevic at attglobal.net 14 RE: wxWindows : Dave Webster 15 RE: wxWindows : Dave Webster 16 Building FLEX requires flex.exe : John Poltorak 17 Re: Saving parameter to listfile : Yuri Prokushev" 18 RE: wxWindows : Hakan" 19 Building emacs : John Poltorak 20 Re: Perl Building : John Poltorak 21 RE: wxWindows : Hakan" 22 RE: wxWindows : Dave Webster 23 Re: Building FLEX requires flex.exe : Holger Veit 24 Re: Building FLEX requires flex.exe : John Poltorak 25 Re: Building FLEX requires flex.exe : John Poltorak 26 Re: wxWindows : John Poltorak 27 RE: wxWindows : Dave Webster 28 RE: wxWindows : Hakan" 29 RE: wxWindows : Dave Webster 30 RE: wxWindows : Dave Webster 31 Re: wxWindows : John Poltorak 32 Re: Building FLEX requires flex.exe : Holger Veit 33 Re: Building FLEX requires flex.exe : Holger Veit 34 Re: Building FLEX requires flex.exe : John Poltorak 35 RE: wxWindows : Hakan" 36 Re: ux2_bootstrap.cmd - wanna try this? : lamikr 37 Re: Building emacs : Christian Hennecke" 38 Re: wxWindows : John Poltorak 39 Re: Using YACC when building FLEX : Csaba" 40 RE: wxWindows : Csaba" 41 Re: Using YACC when building FLEX : John Poltorak 42 Trying to configure autoconf : xyzyx" 43 Clearing the environment? : xyzyx" **= Email 1 ==========================** Date: Wed, 24 Jul 2002 05:40:21 -0400 From: Thomas Dickey Subject: Re: Using YACC when building FLEX On Wed, Jul 24, 2002 at 10:15:56AM +0100, John Poltorak wrote: > > FLEX comes with a Makefile.os2 which defines YACC as bison. I tried > changing this to yacc to see if it worked, but it didn't. I got:- > > ... > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c nfa.c > yacc -d -o parse.c parse.y > usage: yacc [-dlrtv] [-b file_prefix] [-p symbol_prefix] filename > make[1]: *** [parse.c] Error 1 > > > Can anyone suggest what I'm doing wrong here? ...using bison. The -o option isn't recognized by yacc or byacc. It's not really necessary (saves a line in the makefile). There are some technical differences between bison and yacc/byacc where the latter won't work (but I haven't seen any uses where the author couldn't have coded against either). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 2 ==========================** Date: Wed, 24 Jul 2002 06:36:27 -0400 From: Thomas Dickey Subject: Re: Using YACC when building FLEX On Wed, Jul 24, 2002 at 11:06:38AM +0100, John Poltorak wrote: > On Wed, Jul 24, 2002 at 05:40:21AM -0400, Thomas Dickey wrote: > > On Wed, Jul 24, 2002 at 10:15:56AM +0100, John Poltorak wrote: > > > > > > FLEX comes with a Makefile.os2 which defines YACC as bison. I tried > > > changing this to yacc to see if it worked, but it didn't. I got:- > > > > > > ... > > > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c nfa.c > > > yacc -d -o parse.c parse.y > > > usage: yacc [-dlrtv] [-b file_prefix] [-p symbol_prefix] filename > > > make[1]: *** [parse.c] Error 1 > > > > > > > > > Can anyone suggest what I'm doing wrong here? > > ...using bison. > > > > The -o option isn't recognized by yacc or byacc. > > I removed -o from the Makefile but it didn't help. I must be missing > something here... > > > It's not really necessary > > (saves a line in the makefile). > > Which line? The line that renames the output of yacc to whatever is wanted other than the standard y.tab.c (also y.tab.h). byacc's -b option allows one to rename the "y" part of the name, while bison's -o option allows one to name the file explicitly. Minor stuff like that is not sufficient reason to use bison in preference to byacc. See cproto, for example, which can use any of those ftp://invisible-island.net/cproto -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 3 ==========================** Date: Wed, 24 Jul 2002 08:03:09 -0400 From: Thomas Dickey Subject: Re: Building FLEX requires flex.exe On Wed, Jul 24, 2002 at 12:23:23PM +0100, John Poltorak wrote: > > I get an error msg while building flex saying flex is not a recognised > command. > > Do I really need to have flex installed before I can build flex? no - your makefile is probably not expanding some token on that line (for instance, if INSTALL_PROGRAM isn't expanded). Do a "make -n" to see what it's trying to do. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 4 ==========================** Date: Wed, 24 Jul 2002 08:11:45 -0400 From: Edwin =?iso-8859-1?Q?G=FCnthner?= Subject: Re: Perl Building Hi there, > I have learned[1] for certain that between [perl] build attempts, the > source tree MUST be deleted and replaced before the next build. This is > kind of unfortunate with perl because so much of it is +R. Since this You could try: unzip the files, get rid of the +R and zip it again. From now on you have a source tree that is easier to delete ;-) **= Email 5 ==========================** Date: Wed, 24 Jul 2002 09:01:36 -0500 From: Dave Webster Subject: wxWindows If you have not read the latest OS/2 eZine issue, I put an article on there concerning wxWindows. I am closing in on getting this product finished (about 3-6 months of work left). Without rehashing all that was in the article, wxWindows the worlds foremost Open Source cross platform GUI toolkit available today. I encompasses just about every known GUI widget ever conceived, a complete template-like container class set, 100% full Unicode support, sockets, threads, semaphores, mutexes, etc.... And the OS/2 port is nearing a first cut completion. The wxWindows group is planning a formal release of wxOS2, as a very rough beta, with the next release, 2.3.3, some time in August. Currently wxOS2 is available only via CVS check-out from wxWindows.org, but after release it will be downloadable from the www.wxWindows.org site as a .zip. With that said, it is pretty usable already, but still very rough around the edges. My last major hole to fill is a fully functioning tree control (and it's subset a list control) with full direct manipulation capability for file drag and drop complete with an attached splitter window ala Window's File Explorer. An OS/2 container control in tree view won't cut it. I also have several other minor holes to fill that are not nearly so daunting. So if anyone would like to assist feel free to let me know. But you will need to be proficient in C++, be able and willing to use CVS, and be willing to spend some time with the library to understand its plumbing before trying to code anything for it. It often requires that things be done in a very non-OS/2 like fashion from what you are probably used to. And yes, once done, I feel it will be, by far and wide, the most all-encompassing Unix to OS/2 cross platform toolkit available. (OS/2 to MAC, OS2 to FreeBSD, OS/2 to Gtk, and OS/2 to Windows as well). **= Email 6 ==========================** Date: Wed, 24 Jul 2002 09:23:33 -0500 From: Dave Webster Subject: RE: wxWindows Most of the development with wxWindows today is in vertical market software and not in the mass market area at all. Companies like using wx to build cross platform (and just single platform as it is a wonderful toolkit on any platform) apps with very narrowly focused purpose. There have been some recent announcements that have yet to make the wxWindows web site of some fairly significant Windows based software companies switching to wxWindows from MFC. IBM currently uses it. If wxWindows ever makes a serious splash in the Window's world and wxOS2 can get to reasonably solid state, I can see it pretty much ending the OPEN32/Odin effort as cross-compiling wxMSW source to wxOS2 is trivial to converting a WIN32 app today using those. (remember wxWindows does not typically rely on resource files at all so there is not a .rc file migration ever needed). -----Original Message----- From: John Poltorak [mailto:jp at eyup.org] Sent: Wednesday, July 24, 2002 8:49 AM To: os2-unix at eyup.org Subject: Re: wxWindows On Wed, Jul 17, 2002 at 02:36:04PM +0200, Adrian Gschwend wrote: > On Wed, 17 Jul 2002 13:26:56 +0100, John Poltorak wrote: > > >Are there any well known apps which use wxWindows? If I could use it > >today, what could I hope to build with it? > > I and my friend are writing the diploma work with wxWindows. We mainly > use it for GUI stuff but also for cross-platform threading support. > > There are some articles about wxWindows at ibm.com (check wxWindows > homepage for URL), they use it to port MFC applications to Linux. > > IMHO GTK and Qt get too much hype nowadays, wxWindows is a very nice > class library to work with, the only drawback IMHO is the quite bad > documentation they have. Sometime it's not clear at all how something > should be used. Is there any already available source which uses wxWindows? I'm not likely to start developing anything with it myself, not yet anyway, but I wondered if I could build a pre-existing app. Do any Linux apps use wxWindows? I'd like to dip my toes in the water just to get a feel of what is possible. > cu > > Adrian > > > > -- > Adrian Gschwend > at OS/2 Netlabs > > ICQ: 22419590 > ktk at netlabs.org > ------- > The OS/2 OpenSource Project: > http://www.netlabs.org > -- John **= Email 7 ==========================** Date: Wed, 24 Jul 2002 09:58:05 +0100 From: John Poltorak Subject: Re: Saving parameter to listfile On Tue, Jul 23, 2002 at 04:17:54PM -0700, Steve Wendt wrote: > On Tue, 23 Jul 2002, John Poltorak wrote: > > > eg if running foo p1 p2 p3 p4 p5 p6, I want to create a listfile containing:- > > > > p1 > > p2 > > p3 > > p4 > > p5 > > p6 > > > > Is there a simple way to do this? > > Holger gave you some C code, but here's a batch file off the top of my > head... > > at echo off > del listfile > :loop > if %1!==! goto end > echo %1 >> listfile > shift > goto loop > :end Ahhh... the forgotten art of batch file programming :-)... -- John **= Email 8 ==========================** Date: Wed, 24 Jul 2002 10:15:56 +0100 From: John Poltorak Subject: Using YACC when building FLEX FLEX comes with a Makefile.os2 which defines YACC as bison. I tried changing this to yacc to see if it worked, but it didn't. I got:- ... gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c nfa.c yacc -d -o parse.c parse.y usage: yacc [-dlrtv] [-b file_prefix] [-p symbol_prefix] filename make[1]: *** [parse.c] Error 1 Can anyone suggest what I'm doing wrong here? Does YACC require some configuration files which I haven't installed? Or should I just stick to using BISON? -- John **= Email 9 ==========================** Date: Wed, 24 Jul 2002 10:51:30 -0500 From: Dave Webster Subject: RE: wxWindows I've heard that there is a reasonable chance Open Office very well might. As for Mozilla, there are supposedly competing products underway using wxWindows that may make that moot. WxWindows has been around for 10 years, but only in the last year or so is library beginning to get a big following. One of the reasons is that some of the principals have moved out of the world of Academia and into the European business community and are really preaching the wx gospel to a much wider audience now, and folks are finally starting to listen. The thing is, it is important to get wxOS2 out there in a reasonably useful state to take advantage of the potential explosion of wxWindows based mass market apps that should start appearing in the next two years. Wx also needs a replacement for SciTech. SciTech was slated to be a corporate support wrapper around wxWindows in much the same fashion that IBM and HP are corporate support wrappers around Linux. Large, commercial shops and Fortune 1000 type companies are simply not comfortable with any Open Source software unless there is this corporate wrapper around it. SciTech folks apparently had some major falling out with the principals over how the wx product is managed and pretty much abandoned their wxMGL effort as a result. Too bad. It really needs a significant corporate sponsor so if you or anyone knows of one, that would be a great boon to the wxWindows effort. -----Original Message----- From: John Poltorak [mailto:jp at eyup.org] Sent: Wednesday, July 24, 2002 10:18 AM To: os2-unix at eyup.org Subject: Re: wxWindows On Wed, Jul 24, 2002 at 09:23:33AM -0500, Dave Webster wrote: > Most of the development with wxWindows today is in vertical market software > and not in the mass market area at all. Companies like using wx to build > cross platform (and just single platform as it is a wonderful toolkit on any > platform) apps with very narrowly focused purpose. There have been some > recent announcements that have yet to make the wxWindows web site of some > fairly significant Windows based software companies switching to wxWindows > from MFC. IBM currently uses it. > > If wxWindows ever makes a serious splash in the Window's world and wxOS2 can > get to reasonably solid state, I can see it pretty much ending the > OPEN32/Odin effort as cross-compiling wxMSW source to wxOS2 is trivial to > converting a WIN32 app today using those. (remember wxWindows does not > typically rely on resource files at all so there is not a .rc file migration > ever needed). Is there any chance of Open Office being converted to use wxWindows? Maybe Mozilla too... What compilers can be used with it? -- John **= Email 10 ==========================** Date: Wed, 24 Jul 2002 11:06:38 +0100 From: John Poltorak Subject: Re: Using YACC when building FLEX On Wed, Jul 24, 2002 at 05:40:21AM -0400, Thomas Dickey wrote: > On Wed, Jul 24, 2002 at 10:15:56AM +0100, John Poltorak wrote: > > > > FLEX comes with a Makefile.os2 which defines YACC as bison. I tried > > changing this to yacc to see if it worked, but it didn't. I got:- > > > > ... > > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c nfa.c > > yacc -d -o parse.c parse.y > > usage: yacc [-dlrtv] [-b file_prefix] [-p symbol_prefix] filename > > make[1]: *** [parse.c] Error 1 > > > > > > Can anyone suggest what I'm doing wrong here? > ...using bison. > > The -o option isn't recognized by yacc or byacc. I removed -o from the Makefile but it didn't help. I must be missing something here... > It's not really necessary > (saves a line in the makefile). Which line? > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net -- John **= Email 11 ==========================** Date: Wed, 24 Jul 2002 11:20:28 +0100 From: John Poltorak Subject: regex.c Is there a definitive version of regex.c anywhere? -- John **= Email 12 ==========================** Date: Wed, 24 Jul 2002 11:51:44 -0400 From: Henry Sobotka Subject: Re: wxWindows John Poltorak wrote: > > Is there any chance of Open Office being converted to use wxWindows? Maybe > Mozilla too... I don't think it would make much sense for Mozilla because its crossplatform XUL/Javascript etc. GUI already is a sort of wxWindows, i.e. a fairly complete set of widgets that can be used to build other apps (in fact, the Mozilla source is intended to be a development toolkit and the browser/editor/mailnews suite can be considered a demo of what can be done with it). Sandwiching a layer of wxWindows C++ classes between the Mozilla GUI and the OS/2 API would also very likely result in a substantial performance hit. h~ **= Email 13 ==========================** Date: Wed, 24 Jul 2002 11:56:45 -0400 From: tstevic at attglobal.net Subject: Re: wxWindows On Wed, Jul 24, 2002 at 09:23:33AM -0500, Dave Webster wrote: > Most of the development with wxWindows today is in vertical market software > and not in the mass market area at all. Companies like using wx to build >cross platform (and just single platform as it is a wonderful toolkit on >any platform) apps with very narrowly focused purpose. There have been >some recent announcements that have yet to make the wxWindows web site >of some fairly significant Windows based software companies switching >to wxWindows from MFC. IBM currently uses it. > > If wxWindows ever makes a serious splash in the Window's world and wxOS2 can > get to reasonably solid state, I can see it pretty much ending the > OPEN32/Odin effort as cross-compiling wxMSW source to wxOS2 is trivial to > converting a WIN32 app today using those. (remember wxWindows does not > typically rely on resource files at all so there is not a .rc file migration > ever needed). But......getting someone or some company to cross-compile to OS/2 is quite a different matter. How many programmers who think it's a windows only world would take the time ( no matter how trivial ) to even look into doing so? -------------------------------------------- tstevic at attglobal.net V.O.I.C.E. RexxLA TeamOS/2 ' I'm just to lazy to use windows.................... ' **= Email 14 ==========================** Date: Wed, 24 Jul 2002 11:58:00 -0500 From: Dave Webster Subject: RE: wxWindows Plenty if there was a business case for doing it. Take an application for use in the financial services or telco sector where OS/2 still enjoys a sizeable market share. Having one box with an OS/2 partition on it takes a few minutes to build the OS/2 binary then put it on the CD or zip/tar it up along with its Windows and Linux binaries and create a link to the download and that's it. Top Dog Software, www.topdogsoftware.biz, is an example of a sizeable commercial Windows software company moving to wxWindows that will be more than happy to cross compile to anything wx supports. The biggest impact, early on, though is within the Open Source community. Things like open source office suites and CAD/CAM apps will demonstrate the feasibility and ease of cross compiling wxWindows apps to OS/2 or MAC or whatever and then for-profit efforts will follow. The resources for cross compile are miniscule, but obviously those for full testing are not so as always, the business has to be there. -----Original Message----- From: tstevic at attglobal.net [mailto:tstevic at attglobal.net] Sent: Wednesday, July 24, 2002 10:57 AM To: os2-unix at eyup.org Subject: Re: wxWindows On Wed, Jul 24, 2002 at 09:23:33AM -0500, Dave Webster wrote: > Most of the development with wxWindows today is in vertical market software > and not in the mass market area at all. Companies like using wx to build >cross platform (and just single platform as it is a wonderful toolkit on >any platform) apps with very narrowly focused purpose. There have been >some recent announcements that have yet to make the wxWindows web site >of some fairly significant Windows based software companies switching >to wxWindows from MFC. IBM currently uses it. > > If wxWindows ever makes a serious splash in the Window's world and wxOS2 can > get to reasonably solid state, I can see it pretty much ending the > OPEN32/Odin effort as cross-compiling wxMSW source to wxOS2 is trivial to > converting a WIN32 app today using those. (remember wxWindows does not > typically rely on resource files at all so there is not a .rc file migration > ever needed). But......getting someone or some company to cross-compile to OS/2 is quite a different matter. How many programmers who think it's a windows only world would take the time ( no matter how trivial ) to even look into doing so? -------------------------------------------- tstevic at attglobal.net V.O.I.C.E. RexxLA TeamOS/2 ' I'm just to lazy to use windows.................... ' **= Email 15 ==========================** Date: Wed, 24 Jul 2002 12:06:07 -0500 From: Dave Webster Subject: RE: wxWindows There are no shipping apps for OS/2 as wxOS2 is not a released port. Most of the wxWindows samples work, tough. For examples of current wxWindows apps go to www.wxWindows.org. There are an ever growing number of them readily available, but most are vertical market apps and apps developed for internal use at this point. And that will likely be where the bulk of wxWindows development happens, inside corporations for internal use, especially for those needing cross-platform capabilities. However, there is no reason why something like wxDesigner could not simply be compiled under VisualAge C++ V3.0 FP 8 and shipped as an OS/2 product. Prior to the release I hope to at least put up some screen shots on the wx web site. -----Original Message----- From: Hakan [mailto:agents at meddatainc.com] Sent: Wednesday, July 24, 2002 11:32 AM To: os2-unix at eyup.org Subject: RE: wxWindows Dave, Can you give us examples of applications using vxWindows (preferably OS/2 applications although I do understand that the OS/2 port is not complete)? Hakan On Wed, 24 Jul 2002 10:51:30 -0500, Dave Webster wrote: >I've heard that there is a reasonable chance Open Office very well might. >As for Mozilla, there are supposedly competing products underway using >wxWindows that may make that moot. WxWindows has been around for 10 years, >but only in the last year or so is library beginning to get a big following. >One of the reasons is that some of the principals have moved out of the >world of Academia and into the European business community and are really >preaching the wx gospel to a much wider audience now, and folks are finally >starting to listen. > >The thing is, it is important to get wxOS2 out there in a reasonably useful >state to take advantage of the potential explosion of wxWindows based mass >market apps that should start appearing in the next two years. Wx also >needs a replacement for SciTech. SciTech was slated to be a corporate >support wrapper around wxWindows in much the same fashion that IBM and HP >are corporate support wrappers around Linux. Large, commercial shops and >Fortune 1000 type companies are simply not comfortable with any Open Source >software unless there is this corporate wrapper around it. SciTech folks >apparently had some major falling out with the principals over how the wx >product is managed and pretty much abandoned their wxMGL effort as a result. >Too bad. It really needs a significant corporate sponsor so if you or >anyone knows of one, that would be a great boon to the wxWindows effort. > >-----Original Message----- >From: John Poltorak [mailto:jp at eyup.org] >Sent: Wednesday, July 24, 2002 10:18 AM >To: os2-unix at eyup.org >Subject: Re: wxWindows > > >On Wed, Jul 24, 2002 at 09:23:33AM -0500, Dave Webster wrote: >> Most of the development with wxWindows today is in vertical market >software >> and not in the mass market area at all. Companies like using wx to build >> cross platform (and just single platform as it is a wonderful toolkit on >any >> platform) apps with very narrowly focused purpose. There have been some >> recent announcements that have yet to make the wxWindows web site of some >> fairly significant Windows based software companies switching to wxWindows >> from MFC. IBM currently uses it. >> >> If wxWindows ever makes a serious splash in the Window's world and wxOS2 >can >> get to reasonably solid state, I can see it pretty much ending the >> OPEN32/Odin effort as cross-compiling wxMSW source to wxOS2 is trivial to >> converting a WIN32 app today using those. (remember wxWindows does not >> typically rely on resource files at all so there is not a .rc file >migration >> ever needed). > > >Is there any chance of Open Office being converted to use wxWindows? Maybe >Mozilla too... > > >What compilers can be used with it? > >-- >John > > > **= Email 16 ==========================** Date: Wed, 24 Jul 2002 12:23:23 +0100 From: John Poltorak Subject: Building FLEX requires flex.exe I get an error msg while building flex saying flex is not a recognised command. Do I really need to have flex installed before I can build flex? -- John **= Email 17 ==========================** Date: Wed, 24 Jul 2002 12:29:39 -0400 (EDT) From: "Yuri Prokushev" Subject: Re: Saving parameter to listfile On Tue, 23 Jul 2002 16:17:54 -0700 (PDT), Steve Wendt wrote: >On Tue, 23 Jul 2002, John Poltorak wrote: > >> eg if running foo p1 p2 p3 p4 p5 p6, I want to create a listfile containing:- >> >> p1 >> p2 >> p3 >> p4 >> p5 >> p6 >> >> Is there a simple way to do this? > >Holger gave you some C code, but here's a batch file off the top of my >head... at echo off if exist listfile del listfile :loop if %1!==! goto end echo %1 >> listfile shift goto loop :end Small fix **= Email 18 ==========================** Date: Wed, 24 Jul 2002 12:32:21 -0400 (EDT) From: "Hakan" Subject: RE: wxWindows Dave, Can you give us examples of applications using vxWindows (preferably OS/2 applications although I do understand that the OS/2 port is not complete)? Hakan On Wed, 24 Jul 2002 10:51:30 -0500, Dave Webster wrote: >I've heard that there is a reasonable chance Open Office very well might. >As for Mozilla, there are supposedly competing products underway using >wxWindows that may make that moot. WxWindows has been around for 10 years, >but only in the last year or so is library beginning to get a big following. >One of the reasons is that some of the principals have moved out of the >world of Academia and into the European business community and are really >preaching the wx gospel to a much wider audience now, and folks are finally >starting to listen. > >The thing is, it is important to get wxOS2 out there in a reasonably useful >state to take advantage of the potential explosion of wxWindows based mass >market apps that should start appearing in the next two years. Wx also >needs a replacement for SciTech. SciTech was slated to be a corporate >support wrapper around wxWindows in much the same fashion that IBM and HP >are corporate support wrappers around Linux. Large, commercial shops and >Fortune 1000 type companies are simply not comfortable with any Open Source >software unless there is this corporate wrapper around it. SciTech folks >apparently had some major falling out with the principals over how the wx >product is managed and pretty much abandoned their wxMGL effort as a result. >Too bad. It really needs a significant corporate sponsor so if you or >anyone knows of one, that would be a great boon to the wxWindows effort. > >-----Original Message----- >From: John Poltorak [mailto:jp at eyup.org] >Sent: Wednesday, July 24, 2002 10:18 AM >To: os2-unix at eyup.org >Subject: Re: wxWindows > > >On Wed, Jul 24, 2002 at 09:23:33AM -0500, Dave Webster wrote: >> Most of the development with wxWindows today is in vertical market >software >> and not in the mass market area at all. Companies like using wx to build >> cross platform (and just single platform as it is a wonderful toolkit on >any >> platform) apps with very narrowly focused purpose. There have been some >> recent announcements that have yet to make the wxWindows web site of some >> fairly significant Windows based software companies switching to wxWindows >> from MFC. IBM currently uses it. >> >> If wxWindows ever makes a serious splash in the Window's world and wxOS2 >can >> get to reasonably solid state, I can see it pretty much ending the >> OPEN32/Odin effort as cross-compiling wxMSW source to wxOS2 is trivial to >> converting a WIN32 app today using those. (remember wxWindows does not >> typically rely on resource files at all so there is not a .rc file >migration >> ever needed). > > >Is there any chance of Open Office being converted to use wxWindows? Maybe >Mozilla too... > > >What compilers can be used with it? > >-- >John > > > **= Email 19 ==========================** Date: Wed, 24 Jul 2002 13:09:25 +0100 From: John Poltorak Subject: Building emacs I managed to build emacs v20.7 recently with some considerable help from Masaru Nomiya, but it did involve a bit of manual intervention. What I would like to do is come up with a build script which was fully automated. If anyone has succeeded in building emacs, can you come up with a script of some sort? -- John **= Email 20 ==========================** Date: Wed, 24 Jul 2002 13:21:06 +0100 From: John Poltorak Subject: Re: Perl Building On Wed, Jul 24, 2002 at 08:11:45AM -0400, Edwin Günthner wrote: > Hi there, > > > > I have learned[1] for certain that between [perl] build attempts, the > > source tree MUST be deleted and replaced before the next build. This is > > kind of unfortunate with perl because so much of it is +R. Since this > > You could try: unzip the files, get rid of the +R and zip it again. > From now on you have a source tree that is easier to delete ;-) What's wrong with using? :- rm -rf perl-5.8.0 -- John **= Email 21 ==========================** Date: Wed, 24 Jul 2002 13:44:18 -0400 (EDT) From: "Hakan" Subject: RE: wxWindows Well, I am curious because, as already pointed out, the business case as to why a software developer should use vxWindows in order to reach the OS/2 market is very weak. The Linux market may offer a stronger case. Compiliing an application is just part of the equation. Furthermore, cross-platform libraries tend to be written to the lowest common denominator, thereby excluding features exclusive to OS/2 (or other operating systems), e.g., the WPS. What about demos of vxWindows compiled for OS/2? Surely there must be some? Hakan On Wed, 24 Jul 2002 12:06:07 -0500, Dave Webster wrote: >There are no shipping apps for OS/2 as wxOS2 is not a released port. Most >of the wxWindows samples work, tough. For examples of current wxWindows >apps go to www.wxWindows.org. There are an ever growing number of them >readily available, but most are vertical market apps and apps developed for >internal use at this point. And that will likely be where the bulk of >wxWindows development happens, inside corporations for internal use, >especially for those needing cross-platform capabilities. However, there is >no reason why something like wxDesigner could not simply be compiled under >VisualAge C++ V3.0 FP 8 and shipped as an OS/2 product. > >Prior to the release I hope to at least put up some screen shots on the wx >web site. > >-----Original Message----- >From: Hakan [mailto:agents at meddatainc.com] >Sent: Wednesday, July 24, 2002 11:32 AM >To: os2-unix at eyup.org >Subject: RE: wxWindows > > >Dave, > >Can you give us examples of applications using vxWindows (preferably >OS/2 applications although I do understand that the OS/2 port is not >complete)? > >Hakan > >On Wed, 24 Jul 2002 10:51:30 -0500, Dave Webster wrote: > >>I've heard that there is a reasonable chance Open Office very well might. >>As for Mozilla, there are supposedly competing products underway using >>wxWindows that may make that moot. WxWindows has been around for 10 years, >>but only in the last year or so is library beginning to get a big >following. >>One of the reasons is that some of the principals have moved out of the >>world of Academia and into the European business community and are really >>preaching the wx gospel to a much wider audience now, and folks are finally >>starting to listen. >> >>The thing is, it is important to get wxOS2 out there in a reasonably useful >>state to take advantage of the potential explosion of wxWindows based mass >>market apps that should start appearing in the next two years. Wx also >>needs a replacement for SciTech. SciTech was slated to be a corporate >>support wrapper around wxWindows in much the same fashion that IBM and HP >>are corporate support wrappers around Linux. Large, commercial shops and >>Fortune 1000 type companies are simply not comfortable with any Open Source >>software unless there is this corporate wrapper around it. SciTech folks >>apparently had some major falling out with the principals over how the wx >>product is managed and pretty much abandoned their wxMGL effort as a >result. >>Too bad. It really needs a significant corporate sponsor so if you or >>anyone knows of one, that would be a great boon to the wxWindows effort. >> >>-----Original Message----- >>From: John Poltorak [mailto:jp at eyup.org] >>Sent: Wednesday, July 24, 2002 10:18 AM >>To: os2-unix at eyup.org >>Subject: Re: wxWindows >> >> >>On Wed, Jul 24, 2002 at 09:23:33AM -0500, Dave Webster wrote: >>> Most of the development with wxWindows today is in vertical market >>software >>> and not in the mass market area at all. Companies like using wx to build >>> cross platform (and just single platform as it is a wonderful toolkit on >>any >>> platform) apps with very narrowly focused purpose. There have been some >>> recent announcements that have yet to make the wxWindows web site of some >>> fairly significant Windows based software companies switching to >wxWindows >>> from MFC. IBM currently uses it. >>> >>> If wxWindows ever makes a serious splash in the Window's world and wxOS2 >>can >>> get to reasonably solid state, I can see it pretty much ending the >>> OPEN32/Odin effort as cross-compiling wxMSW source to wxOS2 is trivial to >>> converting a WIN32 app today using those. (remember wxWindows does not >>> typically rely on resource files at all so there is not a .rc file >>migration >>> ever needed). >> >> >>Is there any chance of Open Office being converted to use wxWindows? Maybe >>Mozilla too... >> >> >>What compilers can be used with it? >> >>-- >>John >> >> >> > > > > **= Email 22 ==========================** Date: Wed, 24 Jul 2002 13:53:37 -0500 From: Dave Webster Subject: RE: wxWindows Yes, there are plenty of demos via the wxWindows samples, some of which are pretty exotic. As for the lowest common denominator as it pertains to features, I can attest, after over 3 years of working on the project OS/2 is by far and wide the most primitive GUI wxWindows supports (at least until they hit the embedded OS's) and I actually have to add a great deal of capability to OS/2 from scratch (areas such as guages, progress bars, statusbars, toolbars, tooltips, over a dozen dialogs common to most GUI's at the API level not in OS/2 PM and so on). However, things unique to a particular OS, if that feature is truly unique to a particular OS, are justifiable ignored as that defeats the purpose of a cross-platform toolkit in the first place. Philosophically speaking, we live in a Windows-centric universe now. The realities of cross platform development, especially in a commercial sense, are that the Windows product ships first. If successful, other ports may happen. The easier the porting effort the better the chance a major app will make it to other platforms. With wxWindows, that effort is nearly trivial, and that is why it was originally developed over 10 years ago....the desire to create something in Windows, prove its viability on the dominant OS, and then, if a hit, port it to Linux Gtk, Motif and the MAC (and now OS/2) and execute it using native widgets (unlike Java and most other cross-platform GUI toolkits). The dominant OS dictates the GUI feature set. The reality is that OS/2 is long in the tooth as GUI's go and really quite primitive. WPS is about the only thing it has going for it that most others do not. I have looked at almost every cross platform GUI toolkit out there, including IOCL, V, Fox, and at least two dozen others. Nothing is nearly as complete and all encompassing as wxWindows, not even close (auto grids, auto sizers, auto layout controls, wizard controls and such as well as fully implemented Unicode support). But therein lies wxWindows biggest weakness, it is like trying to take a drink from a fire hydrant. -----Original Message----- From: Hakan [mailto:agents at meddatainc.com] Sent: Wednesday, July 24, 2002 12:44 PM To: os2-unix at eyup.org Subject: RE: wxWindows Well, I am curious because, as already pointed out, the business case as to why a software developer should use vxWindows in order to reach the OS/2 market is very weak. The Linux market may offer a stronger case. Compiliing an application is just part of the equation. Furthermore, cross-platform libraries tend to be written to the lowest common denominator, thereby excluding features exclusive to OS/2 (or other operating systems), e.g., the WPS. What about demos of vxWindows compiled for OS/2? Surely there must be some? Hakan On Wed, 24 Jul 2002 12:06:07 -0500, Dave Webster wrote: >There are no shipping apps for OS/2 as wxOS2 is not a released port. Most >of the wxWindows samples work, tough. For examples of current wxWindows >apps go to www.wxWindows.org. There are an ever growing number of them >readily available, but most are vertical market apps and apps developed for >internal use at this point. And that will likely be where the bulk of >wxWindows development happens, inside corporations for internal use, >especially for those needing cross-platform capabilities. However, there is >no reason why something like wxDesigner could not simply be compiled under >VisualAge C++ V3.0 FP 8 and shipped as an OS/2 product. > >Prior to the release I hope to at least put up some screen shots on the wx >web site. > >-----Original Message----- >From: Hakan [mailto:agents at meddatainc.com] >Sent: Wednesday, July 24, 2002 11:32 AM >To: os2-unix at eyup.org >Subject: RE: wxWindows > > >Dave, > >Can you give us examples of applications using vxWindows (preferably >OS/2 applications although I do understand that the OS/2 port is not >complete)? > >Hakan > >On Wed, 24 Jul 2002 10:51:30 -0500, Dave Webster wrote: > >>I've heard that there is a reasonable chance Open Office very well might. >>As for Mozilla, there are supposedly competing products underway using >>wxWindows that may make that moot. WxWindows has been around for 10 years, >>but only in the last year or so is library beginning to get a big >following. >>One of the reasons is that some of the principals have moved out of the >>world of Academia and into the European business community and are really >>preaching the wx gospel to a much wider audience now, and folks are finally >>starting to listen. >> >>The thing is, it is important to get wxOS2 out there in a reasonably useful >>state to take advantage of the potential explosion of wxWindows based mass >>market apps that should start appearing in the next two years. Wx also >>needs a replacement for SciTech. SciTech was slated to be a corporate >>support wrapper around wxWindows in much the same fashion that IBM and HP >>are corporate support wrappers around Linux. Large, commercial shops and >>Fortune 1000 type companies are simply not comfortable with any Open Source >>software unless there is this corporate wrapper around it. SciTech folks >>apparently had some major falling out with the principals over how the wx >>product is managed and pretty much abandoned their wxMGL effort as a >result. >>Too bad. It really needs a significant corporate sponsor so if you or >>anyone knows of one, that would be a great boon to the wxWindows effort. >> >>-----Original Message----- >>From: John Poltorak [mailto:jp at eyup.org] >>Sent: Wednesday, July 24, 2002 10:18 AM >>To: os2-unix at eyup.org >>Subject: Re: wxWindows >> >> >>On Wed, Jul 24, 2002 at 09:23:33AM -0500, Dave Webster wrote: >>> Most of the development with wxWindows today is in vertical market >>software >>> and not in the mass market area at all. Companies like using wx to build >>> cross platform (and just single platform as it is a wonderful toolkit on >>any >>> platform) apps with very narrowly focused purpose. There have been some >>> recent announcements that have yet to make the wxWindows web site of some >>> fairly significant Windows based software companies switching to >wxWindows >>> from MFC. IBM currently uses it. >>> >>> If wxWindows ever makes a serious splash in the Window's world and wxOS2 >>can >>> get to reasonably solid state, I can see it pretty much ending the >>> OPEN32/Odin effort as cross-compiling wxMSW source to wxOS2 is trivial to >>> converting a WIN32 app today using those. (remember wxWindows does not >>> typically rely on resource files at all so there is not a .rc file >>migration >>> ever needed). >> >> >>Is there any chance of Open Office being converted to use wxWindows? Maybe >>Mozilla too... >> >> >>What compilers can be used with it? >> >>-- >>John >> >> >> > > > > **= Email 23 ==========================** Date: Wed, 24 Jul 2002 13:57:49 +0200 From: Holger Veit Subject: Re: Building FLEX requires flex.exe On Wed, Jul 24, 2002 at 12:23:23PM +0100, John Poltorak wrote: > > I get an error msg while building flex saying flex is not a recognised > command. > > Do I really need to have flex installed before I can build flex? You probably have a PATH problem. IIRC (please correct me, it was long ago I compiled that) flex is first bootstrapped with a default file, and then the built initial flex version translates itself again to build the final version. I guess what you see is happening in the second phase, which means that the built flex is not in your PATH (maybe the dot directory is missing). Holger -- Please update your tables to my new e-mail address: holger.veit$ais.fhg.de (replace the '$' with ' at ' -- spam-protection) **= Email 24 ==========================** Date: Wed, 24 Jul 2002 14:03:54 +0100 From: John Poltorak Subject: Re: Building FLEX requires flex.exe On Wed, Jul 24, 2002 at 08:03:09AM -0400, Thomas Dickey wrote: > On Wed, Jul 24, 2002 at 12:23:23PM +0100, John Poltorak wrote: > > > > I get an error msg while building flex saying flex is not a recognised > > command. > > > > Do I really need to have flex installed before I can build flex? > > no - your makefile is probably not expanding some token on that line > (for instance, if INSTALL_PROGRAM isn't expanded). Do a "make -n" > to see what it's trying to do. Here's what I get:- [C:\unixos2\workdir\flex-2.5.4]make -n -f makefile.os2 release make -f Makefile.os2 flex.exe \ CC="gcc -Zomf -O" O=".obj" A=".lib" AR="emxomfar" \ LDFLAGS="-s -Zcrtdll -Zstack 512" make[1]: Entering directory `/unixos2/workdir/flex-2.5.4' gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c ccl.c gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c dfa.c gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c ecs.c gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c gen.c gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c main.c gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c misc.c gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c nfa.c bison -d -o parse.c parse.y gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c parse.c flex -ist scan.l >scan.c bison -d -o parse.c parse.y gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c scan.c gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c skel.c gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c sym.c gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c tblcmp.c gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c yylex.c gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c libmain.c gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c libyywrap.c emxomfar cru fl.lib libmain.obj libyywrap.obj emxomfar s fl.lib gcc -Zomf -O -s -Zcrtdll -Zstack 512 -o flex.exe ccl.obj dfa.obj ecs.obj gen.obj main.obj misc.obj nfa.obj parse.obj scan.obj skel.obj sym.obj tblcmp.obj yylex.obj fl.lib make[1]: Leaving directory `/unixos2/workdir/flex-2.5.4' This is using the Makefile.os2 included with flex-2.5.4a without any changes. If I drop the '-n' from make, I get:- ... gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c nfa.c bison -d -o parse.c parse.y gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c parse.c flex -ist scan.l >scan.c SYS1041: The name flex is not recognized as an internal or external command, operable program or batch file. make[1]: *** [scan.c] Error 1041 make[1]: Leaving directory `/unixos2/workdir/flex-2.5.4' make: *** [release] Error 2 > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net -- John **= Email 25 ==========================** Date: Wed, 24 Jul 2002 14:13:33 +0100 From: John Poltorak Subject: Re: Building FLEX requires flex.exe On Wed, Jul 24, 2002 at 01:57:49PM +0200, Holger Veit wrote: > On Wed, Jul 24, 2002 at 12:23:23PM +0100, John Poltorak wrote: > > > > I get an error msg while building flex saying flex is not a recognised > > command. > > > > Do I really need to have flex installed before I can build flex? > > You probably have a PATH problem. IIRC (please correct me, it was > long ago I compiled that) flex is first bootstrapped with a default > file, and then the built initial flex version translates itself again > to build the final version. I guess what you see is happening in the > second phase, which means that the built flex is not in your PATH (maybe > the dot directory is missing). I'm only using the supplied Makefile.os2 which is included with flex-2.5.4a. No flex.exe gets built so I can't see how it could be a path problem. > Holger > > -- > Please update your tables to my new e-mail address: > holger.veit$ais.fhg.de (replace the '$' with ' at ' -- spam-protection) > -- John **= Email 26 ==========================** Date: Wed, 24 Jul 2002 14:49:08 +0100 From: John Poltorak Subject: Re: wxWindows On Wed, Jul 17, 2002 at 02:36:04PM +0200, Adrian Gschwend wrote: > On Wed, 17 Jul 2002 13:26:56 +0100, John Poltorak wrote: > > >Are there any well known apps which use wxWindows? If I could use it > >today, what could I hope to build with it? > > I and my friend are writing the diploma work with wxWindows. We mainly > use it for GUI stuff but also for cross-platform threading support. > > There are some articles about wxWindows at ibm.com (check wxWindows > homepage for URL), they use it to port MFC applications to Linux. > > IMHO GTK and Qt get too much hype nowadays, wxWindows is a very nice > class library to work with, the only drawback IMHO is the quite bad > documentation they have. Sometime it's not clear at all how something > should be used. Is there any already available source which uses wxWindows? I'm not likely to start developing anything with it myself, not yet anyway, but I wondered if I could build a pre-existing app. Do any Linux apps use wxWindows? I'd like to dip my toes in the water just to get a feel of what is possible. > cu > > Adrian > > > > -- > Adrian Gschwend > at OS/2 Netlabs > > ICQ: 22419590 > ktk at netlabs.org > ------- > The OS/2 OpenSource Project: > http://www.netlabs.org > -- John **= Email 27 ==========================** Date: Wed, 24 Jul 2002 15:40:06 -0500 From: Dave Webster Subject: RE: wxWindows Wow! One thing at a time. I'm no expert, by any means, on Python. Python is a 4GL development kit. In order to use it, you have to "bind" it to underlying C++ objects. But getting technical on just how that works is beyond my expertise. I'll let the Python experts handle that one. While you could use the wx.lib or wx.dll with programs written in languages whose build mechanisms allow mixed language bindings and inter-language procedure calls, you cannot use it directly. The interface is strictly C++. As far as what needs doing: 1) I am currently working on finishing the standard dialogs that wxWindows provides. These include things like color selection, font selection, file dialogs, printer selection, text prompt selection, numeric selection, single and multi-choice selection, search and replace selection, message box, and so on. I have almost all of them completed. 2) A full featured notebook/property page control. Got bits and pieces of that done. 3) A list control (probably nothing more than a tree view Container control). 4) A tree control. This is a biggy. This is a control that basically looks like Window's file explorer. It is a list control but with a splitter window that shows the contents of the currently selected folder object. And it must support full drag-and-drop file manipulation. I have neither the tree control, the drag-drop, nor the splitter implemented. 5) An MDI frame window as well as wx's doc/view class. This is partially complete but untested 6) The joystick manipulation class 7) The wave class and a few other Multi-media classes. 8) Finish all the font encoding and OS/2 support for Unicode/Locale facilities -- something I am completely unable to do or test. 9) Metafile support class. 10) Printing is basically a black hole, especially Postscript, although most of it piggyback's on the wxDC class which works pretty well. 11) The OpenGL interface class. 12) Some of the more exotic graphics drawing in the wxDC class like rounded text. That's about as complete a list as I have. Aside from those items, a lot of what is implemented is a bit rough and could stand some cleaning up or a rehash as some things are a downright kludge, particularly items for which there are no native PM implementations. Would like for folks to take a look at socket, thread, mutex and semaphore implementations to ensure they are OK. -----Original Message----- From: John Poltorak [mailto:jp at eyup.org] Sent: Wednesday, July 24, 2002 2:27 PM To: os2-unix at eyup.org Subject: Re: wxWindows On Wed, Jul 24, 2002 at 09:01:36AM -0500, Dave Webster wrote: > If you have not read the latest OS/2 eZine issue, I put an article on there > concerning wxWindows. I am closing in on getting this product finished > (about 3-6 months of work left). Without rehashing all that was in the > article, wxWindows the worlds foremost Open Source cross platform GUI > toolkit available today. In the article you mentioned that you could do with some help getting it finished. What sort of things do you want people to do? You also mentioned something about Python support, but that there was no OS/2 binding yet. What does that actually mean? What work is involved? What other languages are supported? For instance could you use wxWindows with Pascal or even ADA? In case anyone hasn't read the article it's available here:- http://www.os2ezine.com/20020716/page_6.html -- John **= Email 28 ==========================** Date: Wed, 24 Jul 2002 15:41:15 -0400 (EDT) From: "Hakan" Subject: RE: wxWindows I was hoping you would point me to some demos of vxWindows for OS/2... Alas, no. Can you point me to some demo programs running under OS/2? Thank you. Hakan On Wed, 24 Jul 2002 13:53:37 -0500, Dave Webster wrote: >Yes, there are plenty of demos via the wxWindows samples, some of which are >pretty exotic. > >As for the lowest common denominator as it pertains to features, I can >attest, after over 3 years of working on the project OS/2 is by far and wide >the most primitive GUI wxWindows supports (at least until they hit the >embedded OS's) and I actually have to add a great deal of capability to OS/2 >from scratch (areas such as guages, progress bars, statusbars, toolbars, >tooltips, over a dozen dialogs common to most GUI's at the API level not in >OS/2 PM and so on). However, things unique to a particular OS, if that >feature is truly unique to a particular OS, are justifiable ignored as that >defeats the purpose of a cross-platform toolkit in the first place. > >Philosophically speaking, we live in a Windows-centric universe now. The >realities of cross platform development, especially in a commercial sense, >are that the Windows product ships first. If successful, other ports may >happen. The easier the porting effort the better the chance a major app >will make it to other platforms. With wxWindows, that effort is nearly >trivial, and that is why it was originally developed over 10 years >ago....the desire to create something in Windows, prove its viability on the >dominant OS, and then, if a hit, port it to Linux Gtk, Motif and the MAC >(and now OS/2) and execute it using native widgets (unlike Java and most >other cross-platform GUI toolkits). The dominant OS dictates the GUI >feature set. The reality is that OS/2 is long in the tooth as GUI's go and >really quite primitive. WPS is about the only thing it has going for it >that most others do not. > >I have looked at almost every cross platform GUI toolkit out there, >including IOCL, V, Fox, and at least two dozen others. Nothing is nearly as >complete and all encompassing as wxWindows, not even close (auto grids, auto >sizers, auto layout controls, wizard controls and such as well as fully >implemented Unicode support). But therein lies wxWindows biggest weakness, >it is like trying to take a drink from a fire hydrant. > >-----Original Message----- >From: Hakan [mailto:agents at meddatainc.com] >Sent: Wednesday, July 24, 2002 12:44 PM >To: os2-unix at eyup.org >Subject: RE: wxWindows > > >Well, I am curious because, as already pointed out, the business case >as to why a software developer should use vxWindows in order to reach >the OS/2 market is very weak. The Linux market may offer a stronger >case. Compiliing an application is just part of the equation. > >Furthermore, cross-platform libraries tend to be written to the lowest >common denominator, thereby excluding features exclusive to OS/2 (or >other operating systems), e.g., the WPS. > >What about demos of vxWindows compiled for OS/2? Surely there must be >some? > >Hakan > >On Wed, 24 Jul 2002 12:06:07 -0500, Dave Webster wrote: > >>There are no shipping apps for OS/2 as wxOS2 is not a released port. Most >>of the wxWindows samples work, tough. For examples of current wxWindows >>apps go to www.wxWindows.org. There are an ever growing number of them >>readily available, but most are vertical market apps and apps developed for >>internal use at this point. And that will likely be where the bulk of >>wxWindows development happens, inside corporations for internal use, >>especially for those needing cross-platform capabilities. However, there >is >>no reason why something like wxDesigner could not simply be compiled under >>VisualAge C++ V3.0 FP 8 and shipped as an OS/2 product. >> >>Prior to the release I hope to at least put up some screen shots on the wx >>web site. >> >>-----Original Message----- >>From: Hakan [mailto:agents at meddatainc.com] >>Sent: Wednesday, July 24, 2002 11:32 AM >>To: os2-unix at eyup.org >>Subject: RE: wxWindows >> >> >>Dave, >> >>Can you give us examples of applications using vxWindows (preferably >>OS/2 applications although I do understand that the OS/2 port is not >>complete)? >> >>Hakan >> >>On Wed, 24 Jul 2002 10:51:30 -0500, Dave Webster wrote: >> >>>I've heard that there is a reasonable chance Open Office very well might. >>>As for Mozilla, there are supposedly competing products underway using >>>wxWindows that may make that moot. WxWindows has been around for 10 >years, >>>but only in the last year or so is library beginning to get a big >>following. >>>One of the reasons is that some of the principals have moved out of the >>>world of Academia and into the European business community and are really >>>preaching the wx gospel to a much wider audience now, and folks are >finally >>>starting to listen. >>> >>>The thing is, it is important to get wxOS2 out there in a reasonably >useful >>>state to take advantage of the potential explosion of wxWindows based mass >>>market apps that should start appearing in the next two years. Wx also >>>needs a replacement for SciTech. SciTech was slated to be a corporate >>>support wrapper around wxWindows in much the same fashion that IBM and HP >>>are corporate support wrappers around Linux. Large, commercial shops and >>>Fortune 1000 type companies are simply not comfortable with any Open >Source >>>software unless there is this corporate wrapper around it. SciTech folks >>>apparently had some major falling out with the principals over how the wx >>>product is managed and pretty much abandoned their wxMGL effort as a >>result. >>>Too bad. It really needs a significant corporate sponsor so if you or >>>anyone knows of one, that would be a great boon to the wxWindows effort. >>> >>>-----Original Message----- >>>From: John Poltorak [mailto:jp at eyup.org] >>>Sent: Wednesday, July 24, 2002 10:18 AM >>>To: os2-unix at eyup.org >>>Subject: Re: wxWindows >>> >>> >>>On Wed, Jul 24, 2002 at 09:23:33AM -0500, Dave Webster wrote: >>>> Most of the development with wxWindows today is in vertical market >>>software >>>> and not in the mass market area at all. Companies like using wx to >build >>>> cross platform (and just single platform as it is a wonderful toolkit on >>>any >>>> platform) apps with very narrowly focused purpose. There have been some >>>> recent announcements that have yet to make the wxWindows web site of >some >>>> fairly significant Windows based software companies switching to >>wxWindows >>>> from MFC. IBM currently uses it. >>>> >>>> If wxWindows ever makes a serious splash in the Window's world and wxOS2 >>>can >>>> get to reasonably solid state, I can see it pretty much ending the >>>> OPEN32/Odin effort as cross-compiling wxMSW source to wxOS2 is trivial >to >>>> converting a WIN32 app today using those. (remember wxWindows does not >>>> typically rely on resource files at all so there is not a .rc file >>>migration >>>> ever needed). >>> >>> >>>Is there any chance of Open Office being converted to use wxWindows? Maybe > >>>Mozilla too... >>> >>> >>>What compilers can be used with it? >>> >>>-- >>>John >>> >>> >>> >> >> >> >> > > > > **= Email 29 ==========================** Date: Wed, 24 Jul 2002 15:54:10 -0500 From: Dave Webster Subject: RE: wxWindows wxOS2 is available only via CVS from wxWindows.org. To even get to a demo, you'd have to check out the distribution from the CVS tree via anonymous, read-only access, build the library, then go to a particular sample, and build/link it, then run it. The dll and static lib are both over 50MB in size and many of the statically linked samples exceed 20MB so giving them to you as an e-mail attachment is impossible. Hopefully by late August, the next formal release of wxWindows will be available, and for the first time, wxOS2 with it. But even then, you'd have to download it from the site or buy the CD, install it, build the library, and link the demos yourself to get them. Understand the state of the project. It has never been released in any form and is still incomplete. To get any kind of wxWindows app or demo you have to download the source, and build it. That is how they do it over there. The don't even put executable binaries on the CD. There are a few apps that are available for wxWindows in executable form, like wxDesigner, but you have to pay for them. Typically all wxWindows Open Source projects use the Linux/Unix model of distribution where you untar/zip the tarball and then "make" it. Some of us are trying hard to get them to adopt a more Windows/MAC/OS2 method of allowing users to download a setup that simply installs the exe and any needed dlls, but that is very slow to catch on. They are a bit slow to realize that typical Windows/OS2 users do not have any ability to "make" anything. But the core group is dominated nowadays by a very Linux oriented crowd so get used to the tarball/make routine if you want to use this library for any development, or even a lot of apps developed under it. -----Original Message----- From: Hakan [mailto:agents at meddatainc.com] Sent: Wednesday, July 24, 2002 2:41 PM To: os2-unix at eyup.org Subject: RE: wxWindows I was hoping you would point me to some demos of vxWindows for OS/2... Alas, no. Can you point me to some demo programs running under OS/2? Thank you. Hakan On Wed, 24 Jul 2002 13:53:37 -0500, Dave Webster wrote: >Yes, there are plenty of demos via the wxWindows samples, some of which are >pretty exotic. > >As for the lowest common denominator as it pertains to features, I can >attest, after over 3 years of working on the project OS/2 is by far and wide >the most primitive GUI wxWindows supports (at least until they hit the >embedded OS's) and I actually have to add a great deal of capability to OS/2 >from scratch (areas such as guages, progress bars, statusbars, toolbars, >tooltips, over a dozen dialogs common to most GUI's at the API level not in >OS/2 PM and so on). However, things unique to a particular OS, if that >feature is truly unique to a particular OS, are justifiable ignored as that >defeats the purpose of a cross-platform toolkit in the first place. > >Philosophically speaking, we live in a Windows-centric universe now. The >realities of cross platform development, especially in a commercial sense, >are that the Windows product ships first. If successful, other ports may >happen. The easier the porting effort the better the chance a major app >will make it to other platforms. With wxWindows, that effort is nearly >trivial, and that is why it was originally developed over 10 years >ago....the desire to create something in Windows, prove its viability on the >dominant OS, and then, if a hit, port it to Linux Gtk, Motif and the MAC >(and now OS/2) and execute it using native widgets (unlike Java and most >other cross-platform GUI toolkits). The dominant OS dictates the GUI >feature set. The reality is that OS/2 is long in the tooth as GUI's go and >really quite primitive. WPS is about the only thing it has going for it >that most others do not. > >I have looked at almost every cross platform GUI toolkit out there, >including IOCL, V, Fox, and at least two dozen others. Nothing is nearly as >complete and all encompassing as wxWindows, not even close (auto grids, auto >sizers, auto layout controls, wizard controls and such as well as fully >implemented Unicode support). But therein lies wxWindows biggest weakness, >it is like trying to take a drink from a fire hydrant. > >-----Original Message----- >From: Hakan [mailto:agents at meddatainc.com] >Sent: Wednesday, July 24, 2002 12:44 PM >To: os2-unix at eyup.org >Subject: RE: wxWindows > > >Well, I am curious because, as already pointed out, the business case >as to why a software developer should use vxWindows in order to reach >the OS/2 market is very weak. The Linux market may offer a stronger >case. Compiliing an application is just part of the equation. > >Furthermore, cross-platform libraries tend to be written to the lowest >common denominator, thereby excluding features exclusive to OS/2 (or >other operating systems), e.g., the WPS. > >What about demos of vxWindows compiled for OS/2? Surely there must be >some? > >Hakan > >On Wed, 24 Jul 2002 12:06:07 -0500, Dave Webster wrote: > >>There are no shipping apps for OS/2 as wxOS2 is not a released port. Most >>of the wxWindows samples work, tough. For examples of current wxWindows >>apps go to www.wxWindows.org. There are an ever growing number of them >>readily available, but most are vertical market apps and apps developed for >>internal use at this point. And that will likely be where the bulk of >>wxWindows development happens, inside corporations for internal use, >>especially for those needing cross-platform capabilities. However, there >is >>no reason why something like wxDesigner could not simply be compiled under >>VisualAge C++ V3.0 FP 8 and shipped as an OS/2 product. >> >>Prior to the release I hope to at least put up some screen shots on the wx >>web site. >> >>-----Original Message----- >>From: Hakan [mailto:agents at meddatainc.com] >>Sent: Wednesday, July 24, 2002 11:32 AM >>To: os2-unix at eyup.org >>Subject: RE: wxWindows >> >> >>Dave, >> >>Can you give us examples of applications using vxWindows (preferably >>OS/2 applications although I do understand that the OS/2 port is not >>complete)? >> >>Hakan >> >>On Wed, 24 Jul 2002 10:51:30 -0500, Dave Webster wrote: >> >>>I've heard that there is a reasonable chance Open Office very well might. >>>As for Mozilla, there are supposedly competing products underway using >>>wxWindows that may make that moot. WxWindows has been around for 10 >years, >>>but only in the last year or so is library beginning to get a big >>following. >>>One of the reasons is that some of the principals have moved out of the >>>world of Academia and into the European business community and are really >>>preaching the wx gospel to a much wider audience now, and folks are >finally >>>starting to listen. >>> >>>The thing is, it is important to get wxOS2 out there in a reasonably >useful >>>state to take advantage of the potential explosion of wxWindows based mass >>>market apps that should start appearing in the next two years. Wx also >>>needs a replacement for SciTech. SciTech was slated to be a corporate >>>support wrapper around wxWindows in much the same fashion that IBM and HP >>>are corporate support wrappers around Linux. Large, commercial shops and >>>Fortune 1000 type companies are simply not comfortable with any Open >Source >>>software unless there is this corporate wrapper around it. SciTech folks >>>apparently had some major falling out with the principals over how the wx >>>product is managed and pretty much abandoned their wxMGL effort as a >>result. >>>Too bad. It really needs a significant corporate sponsor so if you or >>>anyone knows of one, that would be a great boon to the wxWindows effort. >>> >>>-----Original Message----- >>>From: John Poltorak [mailto:jp at eyup.org] >>>Sent: Wednesday, July 24, 2002 10:18 AM >>>To: os2-unix at eyup.org >>>Subject: Re: wxWindows >>> >>> >>>On Wed, Jul 24, 2002 at 09:23:33AM -0500, Dave Webster wrote: >>>> Most of the development with wxWindows today is in vertical market >>>software >>>> and not in the mass market area at all. Companies like using wx to >build >>>> cross platform (and just single platform as it is a wonderful toolkit on >>>any >>>> platform) apps with very narrowly focused purpose. There have been some >>>> recent announcements that have yet to make the wxWindows web site of >some >>>> fairly significant Windows based software companies switching to >>wxWindows >>>> from MFC. IBM currently uses it. >>>> >>>> If wxWindows ever makes a serious splash in the Window's world and wxOS2 >>>can >>>> get to reasonably solid state, I can see it pretty much ending the >>>> OPEN32/Odin effort as cross-compiling wxMSW source to wxOS2 is trivial >to >>>> converting a WIN32 app today using those. (remember wxWindows does not >>>> typically rely on resource files at all so there is not a .rc file >>>migration >>>> ever needed). >>> >>> >>>Is there any chance of Open Office being converted to use wxWindows? Maybe > >>>Mozilla too... >>> >>> >>>What compilers can be used with it? >>> >>>-- >>>John >>> >>> >>> >> >> >> >> > > > > **= Email 30 ==========================** Date: Wed, 24 Jul 2002 15:56:24 -0500 From: Dave Webster Subject: RE: wxWindows There are a number of wx developers that are working for software firms looking to either "port" Open Office or Star Office or develop their own Office suite using wxWindows and do the same for CAD/CAM. -----Original Message----- From: Csaba [mailto:adwx88 at uk.uumail.com] Sent: Wednesday, July 24, 2002 2:58 PM To: os2-unix at eyup.org Subject: RE: wxWindows On 24 Jul 2002, at 10:51, Dave Webster wrote: >> -----Original Message----- >> From: John Poltorak [mailto:jp at eyup.org] [snip] >> Is there any chance of Open Office being converted to use >>wxWindows? Maybe Mozilla too... > I've heard that there is a reasonable chance Open Office very well might. I sincerely doubt it, considering the sheer size of OpenOffice > As for Mozilla, [snip] Mozilla is heavily componentized. There are plenty of browsers out there already using Gecko, the Mozilla engine: Konqueror, Galeon, etc. Writing a wxWindows framework around the Gecko renderer is (drumroll) left as an exercise, apparently solved here: http://wxmozilla.sourceforge.net/ Ceci n'est pas un .signature **= Email 31 ==========================** Date: Wed, 24 Jul 2002 16:18:24 +0100 From: John Poltorak Subject: Re: wxWindows On Wed, Jul 24, 2002 at 09:23:33AM -0500, Dave Webster wrote: > Most of the development with wxWindows today is in vertical market software > and not in the mass market area at all. Companies like using wx to build > cross platform (and just single platform as it is a wonderful toolkit on any > platform) apps with very narrowly focused purpose. There have been some > recent announcements that have yet to make the wxWindows web site of some > fairly significant Windows based software companies switching to wxWindows > from MFC. IBM currently uses it. > > If wxWindows ever makes a serious splash in the Window's world and wxOS2 can > get to reasonably solid state, I can see it pretty much ending the > OPEN32/Odin effort as cross-compiling wxMSW source to wxOS2 is trivial to > converting a WIN32 app today using those. (remember wxWindows does not > typically rely on resource files at all so there is not a .rc file migration > ever needed). Is there any chance of Open Office being converted to use wxWindows? Maybe Mozilla too... What compilers can be used with it? -- John **= Email 32 ==========================** Date: Wed, 24 Jul 2002 16:25:29 +0200 From: Holger Veit Subject: Re: Building FLEX requires flex.exe On Wed, Jul 24, 2002 at 02:03:54PM +0100, John Poltorak wrote: > On Wed, Jul 24, 2002 at 08:03:09AM -0400, Thomas Dickey wrote: > > On Wed, Jul 24, 2002 at 12:23:23PM +0100, John Poltorak wrote: > > > > > > I get an error msg while building flex saying flex is not a recognised > > > command. > > > > > > Do I really need to have flex installed before I can build flex? > > > > no - your makefile is probably not expanding some token on that line > > (for instance, if INSTALL_PROGRAM isn't expanded). Do a "make -n" > > to see what it's trying to do. > > Here's what I get:- > > > [C:\unixos2\workdir\flex-2.5.4]make -n -f makefile.os2 release > make -f Makefile.os2 flex.exe \ > CC="gcc -Zomf -O" O=".obj" A=".lib" AR="emxomfar" \ > LDFLAGS="-s -Zcrtdll -Zstack 512" > make[1]: Entering directory `/unixos2/workdir/flex-2.5.4' > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c ccl.c > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c dfa.c > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c ecs.c > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c gen.c > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c main.c > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c misc.c > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c nfa.c > bison -d -o parse.c parse.y > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c parse.c > flex -ist scan.l >scan.c > bison -d -o parse.c parse.y > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c scan.c > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c skel.c > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c sym.c > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c tblcmp.c > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c yylex.c > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c libmain.c > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c libyywrap.c > emxomfar cru fl.lib libmain.obj libyywrap.obj > emxomfar s fl.lib > gcc -Zomf -O -s -Zcrtdll -Zstack 512 -o flex.exe ccl.obj dfa.obj ecs.obj > gen.obj main.obj misc.obj nfa.obj parse.obj scan.obj skel.obj sym.obj > tblcmp.obj yylex.obj fl.lib > make[1]: Leaving directory `/unixos2/workdir/flex-2.5.4' > > > This is using the Makefile.os2 included with flex-2.5.4a without any > changes. If I drop the '-n' from make, I get:- > > ... > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c nfa.c > bison -d -o parse.c parse.y > gcc -Zomf -O -DOS2 -DSHORT_FILE_NAMES -c parse.c > flex -ist scan.l >scan.c > SYS1041: The name flex is not recognized as an > internal or external command, operable program or batch file. > make[1]: *** [scan.c] Error 1041 > make[1]: Leaving directory `/unixos2/workdir/flex-2.5.4' > make: *** [release] Error 2 Okay, then, it is not a PATH problem but rather a timestamp problem. There is a rule which will make a scan.c out of the scan.l if scan.l is newer than scan.c. This uses flex, of course. The stock flex distribution should come with a scan.l that has an *older* timestamp than scan.c. The scan.c has been precompiled as initscan.c. Do a 'make .bootstrap' first to avoid the problem, seems it isn't run for some reason. Holger -- Please update your tables to my new e-mail address: holger.veit$ais.fhg.de (replace the '$' with ' at ' -- spam-protection) **= Email 33 ==========================** Date: Wed, 24 Jul 2002 16:28:44 +0200 From: Holger Veit Subject: Re: Building FLEX requires flex.exe On Wed, Jul 24, 2002 at 02:13:33PM +0100, John Poltorak wrote: > On Wed, Jul 24, 2002 at 01:57:49PM +0200, Holger Veit wrote: > > On Wed, Jul 24, 2002 at 12:23:23PM +0100, John Poltorak wrote: > > > > > > I get an error msg while building flex saying flex is not a recognised > > > command. > > > > > > Do I really need to have flex installed before I can build flex? > > > > You probably have a PATH problem. IIRC (please correct me, it was > > long ago I compiled that) flex is first bootstrapped with a default > > file, and then the built initial flex version translates itself again > > to build the final version. I guess what you see is happening in the > > second phase, which means that the built flex is not in your PATH (maybe > > the dot directory is missing). > > I'm only using the supplied Makefile.os2 which is included with > flex-2.5.4a. No flex.exe gets built so I can't see how it could be a path > problem. Argggghhhh! In correction to my last reply, don't run 'make .bootstrap', but 'make -f Makefile.os2 first_flex'. This will copy the initscan.c accordingly[1] Holger -- Please update your tables to my new e-mail address: holger.veit$ais.fhg.de (replace the '$' with ' at ' -- spam-protection) **= Email 34 ==========================** Date: Wed, 24 Jul 2002 16:48:50 +0100 From: John Poltorak Subject: Re: Building FLEX requires flex.exe On Wed, Jul 24, 2002 at 04:28:44PM +0200, Holger Veit wrote: > On Wed, Jul 24, 2002 at 02:13:33PM +0100, John Poltorak wrote: > > On Wed, Jul 24, 2002 at 01:57:49PM +0200, Holger Veit wrote: > > > On Wed, Jul 24, 2002 at 12:23:23PM +0100, John Poltorak wrote: > > > > > > > > I get an error msg while building flex saying flex is not a recognised > > > > command. > > > > > > > > Do I really need to have flex installed before I can build flex? > > > > > > You probably have a PATH problem. IIRC (please correct me, it was > > > long ago I compiled that) flex is first bootstrapped with a default > > > file, and then the built initial flex version translates itself again > > > to build the final version. I guess what you see is happening in the > > > second phase, which means that the built flex is not in your PATH (maybe > > > the dot directory is missing). > > > > I'm only using the supplied Makefile.os2 which is included with > > flex-2.5.4a. No flex.exe gets built so I can't see how it could be a path > > problem. > > Argggghhhh! In correction to my last reply, don't run 'make .bootstrap', There isn't a .bootstrap target in Makefile.os2 anyway... > but > 'make -f Makefile.os2 first_flex'. This will copy the initscan.c accordingly[1] OK, I tried:- [C:\unixos2\workdir\flex-2.5.4]make -f makefile.os2 first_flex cp initscan.c scan.c make flex make[1]: Entering directory `C:/unixos2/workdir/flex-2.5.4' make[1]: *** No rule to make target `flex'. Stop. make[1]: Leaving directory `C:/unixos2/workdir/flex-2.5.4' make: *** [first_flex] Error 2 I wonder if this ever worked for anyone... Maybe my combination of Make or SHELL is having an adverse effect on getting this built. I would have though it should be very straightforward... > Holger > > -- > Please update your tables to my new e-mail address: > holger.veit$ais.fhg.de (replace the '$' with ' at ' -- spam-protection) > -- John **= Email 35 ==========================** Date: Wed, 24 Jul 2002 17:16:32 -0400 (EDT) From: "Hakan" Subject: RE: wxWindows I do not want to be too discouraging, however, in my opinion, this project will not have any impact on OS/2 application development. Hakan On Wed, 24 Jul 2002 15:54:10 -0500, Dave Webster wrote: >wxOS2 is available only via CVS from wxWindows.org. To even get to a demo, >you'd have to check out the distribution from the CVS tree via anonymous, >read-only access, build the library, then go to a particular sample, and >build/link it, then run it. The dll and static lib are both over 50MB in >size and many of the statically linked samples exceed 20MB so giving them to >you as an e-mail attachment is impossible. > >Hopefully by late August, the next formal release of wxWindows will be >available, and for the first time, wxOS2 with it. But even then, you'd have >to download it from the site or buy the CD, install it, build the library, >and link the demos yourself to get them. > >Understand the state of the project. It has never been released in any form >and is still incomplete. To get any kind of wxWindows app or demo you have >to download the source, and build it. That is how they do it over there. >The don't even put executable binaries on the CD. There are a few apps that >are available for wxWindows in executable form, like wxDesigner, but you >have to pay for them. Typically all wxWindows Open Source projects use the >Linux/Unix model of distribution where you untar/zip the tarball and then >"make" it. Some of us are trying hard to get them to adopt a more >Windows/MAC/OS2 method of allowing users to download a setup that simply >installs the exe and any needed dlls, but that is very slow to catch on. >They are a bit slow to realize that typical Windows/OS2 users do not have >any ability to "make" anything. But the core group is dominated nowadays by >a very Linux oriented crowd so get used to the tarball/make routine if you >want to use this library for any development, or even a lot of apps >developed under it. > > >-----Original Message----- >From: Hakan [mailto:agents at meddatainc.com] >Sent: Wednesday, July 24, 2002 2:41 PM >To: os2-unix at eyup.org >Subject: RE: wxWindows > > >I was hoping you would point me to some demos of vxWindows for OS/2... >Alas, no. Can you point me to some demo programs running under OS/2? > >Thank you. > >Hakan > >On Wed, 24 Jul 2002 13:53:37 -0500, Dave Webster wrote: > >>Yes, there are plenty of demos via the wxWindows samples, some of which are >>pretty exotic. >> >>As for the lowest common denominator as it pertains to features, I can >>attest, after over 3 years of working on the project OS/2 is by far and >wide >>the most primitive GUI wxWindows supports (at least until they hit the >>embedded OS's) and I actually have to add a great deal of capability to >OS/2 >>from scratch (areas such as guages, progress bars, statusbars, toolbars, >>tooltips, over a dozen dialogs common to most GUI's at the API level not in >>OS/2 PM and so on). However, things unique to a particular OS, if that >>feature is truly unique to a particular OS, are justifiable ignored as that >>defeats the purpose of a cross-platform toolkit in the first place. >> >>Philosophically speaking, we live in a Windows-centric universe now. The >>realities of cross platform development, especially in a commercial sense, >>are that the Windows product ships first. If successful, other ports may >>happen. The easier the porting effort the better the chance a major app >>will make it to other platforms. With wxWindows, that effort is nearly >>trivial, and that is why it was originally developed over 10 years >>ago....the desire to create something in Windows, prove its viability on >the >>dominant OS, and then, if a hit, port it to Linux Gtk, Motif and the MAC >>(and now OS/2) and execute it using native widgets (unlike Java and most >>other cross-platform GUI toolkits). The dominant OS dictates the GUI >>feature set. The reality is that OS/2 is long in the tooth as GUI's go and >>really quite primitive. WPS is about the only thing it has going for it >>that most others do not. >> >>I have looked at almost every cross platform GUI toolkit out there, >>including IOCL, V, Fox, and at least two dozen others. Nothing is nearly >as >>complete and all encompassing as wxWindows, not even close (auto grids, >auto >>sizers, auto layout controls, wizard controls and such as well as fully >>implemented Unicode support). But therein lies wxWindows biggest weakness, >>it is like trying to take a drink from a fire hydrant. >> >>-----Original Message----- >>From: Hakan [mailto:agents at meddatainc.com] >>Sent: Wednesday, July 24, 2002 12:44 PM >>To: os2-unix at eyup.org >>Subject: RE: wxWindows >> >> >>Well, I am curious because, as already pointed out, the business case >>as to why a software developer should use vxWindows in order to reach >>the OS/2 market is very weak. The Linux market may offer a stronger >>case. Compiliing an application is just part of the equation. >> >>Furthermore, cross-platform libraries tend to be written to the lowest >>common denominator, thereby excluding features exclusive to OS/2 (or >>other operating systems), e.g., the WPS. >> >>What about demos of vxWindows compiled for OS/2? Surely there must be >>some? >> >>Hakan >> >>On Wed, 24 Jul 2002 12:06:07 -0500, Dave Webster wrote: >> >>>There are no shipping apps for OS/2 as wxOS2 is not a released port. Most >>>of the wxWindows samples work, tough. For examples of current wxWindows >>>apps go to www.wxWindows.org. There are an ever growing number of them >>>readily available, but most are vertical market apps and apps developed >for >>>internal use at this point. And that will likely be where the bulk of >>>wxWindows development happens, inside corporations for internal use, >>>especially for those needing cross-platform capabilities. However, there >>is >>>no reason why something like wxDesigner could not simply be compiled under >>>VisualAge C++ V3.0 FP 8 and shipped as an OS/2 product. >>> >>>Prior to the release I hope to at least put up some screen shots on the wx >>>web site. >>> >>>-----Original Message----- >>>From: Hakan [mailto:agents at meddatainc.com] >>>Sent: Wednesday, July 24, 2002 11:32 AM >>>To: os2-unix at eyup.org >>>Subject: RE: wxWindows >>> >>> >>>Dave, >>> >>>Can you give us examples of applications using vxWindows (preferably >>>OS/2 applications although I do understand that the OS/2 port is not >>>complete)? >>> >>>Hakan >>> >>>On Wed, 24 Jul 2002 10:51:30 -0500, Dave Webster wrote: >>> >>>>I've heard that there is a reasonable chance Open Office very well might. >>>>As for Mozilla, there are supposedly competing products underway using >>>>wxWindows that may make that moot. WxWindows has been around for 10 >>years, >>>>but only in the last year or so is library beginning to get a big >>>following. >>>>One of the reasons is that some of the principals have moved out of the >>>>world of Academia and into the European business community and are really >>>>preaching the wx gospel to a much wider audience now, and folks are >>finally >>>>starting to listen. >>>> >>>>The thing is, it is important to get wxOS2 out there in a reasonably >>useful >>>>state to take advantage of the potential explosion of wxWindows based >mass >>>>market apps that should start appearing in the next two years. Wx also >>>>needs a replacement for SciTech. SciTech was slated to be a corporate >>>>support wrapper around wxWindows in much the same fashion that IBM and HP >>>>are corporate support wrappers around Linux. Large, commercial shops and >>>>Fortune 1000 type companies are simply not comfortable with any Open >>Source >>>>software unless there is this corporate wrapper around it. SciTech folks >>>>apparently had some major falling out with the principals over how the wx >>>>product is managed and pretty much abandoned their wxMGL effort as a >>>result. >>>>Too bad. It really needs a significant corporate sponsor so if you or >>>>anyone knows of one, that would be a great boon to the wxWindows effort. >>>> >>>>-----Original Message----- >>>>From: John Poltorak [mailto:jp at eyup.org] >>>>Sent: Wednesday, July 24, 2002 10:18 AM >>>>To: os2-unix at eyup.org >>>>Subject: Re: wxWindows >>>> >>>> >>>>On Wed, Jul 24, 2002 at 09:23:33AM -0500, Dave Webster wrote: >>>>> Most of the development with wxWindows today is in vertical market >>>>software >>>>> and not in the mass market area at all. Companies like using wx to >>build >>>>> cross platform (and just single platform as it is a wonderful toolkit >on >>>>any >>>>> platform) apps with very narrowly focused purpose. There have been >some >>>>> recent announcements that have yet to make the wxWindows web site of >>some >>>>> fairly significant Windows based software companies switching to >>>wxWindows >>>>> from MFC. IBM currently uses it. >>>>> >>>>> If wxWindows ever makes a serious splash in the Window's world and >wxOS2 >>>>can >>>>> get to reasonably solid state, I can see it pretty much ending the >>>>> OPEN32/Odin effort as cross-compiling wxMSW source to wxOS2 is trivial >>to >>>>> converting a WIN32 app today using those. (remember wxWindows does not >>>>> typically rely on resource files at all so there is not a .rc file >>>>migration >>>>> ever needed). >>>> >>>> >>>>Is there any chance of Open Office being converted to use wxWindows? >Maybe >> >>>>Mozilla too... >>>> >>>> >>>>What compilers can be used with it? >>>> >>>>-- >>>>John >>>> >>>> >>>> >>> >>> >>> >>> >> >> >> >> > > > > **= Email 36 ==========================** Date: Wed, 24 Jul 2002 18:00:28 +0100 From: lamikr Subject: Re: ux2_bootstrap.cmd - wanna try this? For some reason the current version could not even build perl for me. Everything before that worked well. (downloading files, patching and building emx, etc...) I tried this with fresh install where I first deleted everything, downloaded ux2_bootstrap.cmd and executed it. This is my ux2_bootstrap.cmd: rem rem rem set bldrt=x: set uxrt=x: set osrt=e: pause set bld_home=unixos2 wget -Ncr -nH --cut-dirs=3 -t 1 -P %bldrt%/%bld_home% ftp://unixos2: at 213.152.37.92/pub/unixos2/build_system/ %bldrt% cd \%bld_home%\lib ux2_inst %1 %2 %3 %4 %5 %6 %7 %8 %9 And here is my perl.log ARCHIVE CFLAGS LDFLAGS PARMS MAKEPARM SRC perl-5.8.0 . ARCHIVE perl-5.8.0 CFLAGS LDFLAGS PARMS MAKEPARM . SRC /unixos2/workdir /unixos2/workdir/perl-5.8.0 using perl specific Build script [X:\unixos2\workdir\perl-5.8.0]sh Configure -des -D prefix=x:/usr/lib/perl (I see you are using the Korn shell. Some ksh's blow up on Configure, mainly on older exotic systems. If yours does, try the Bourne shell instead.) First let's make sure your kit is complete. Checking... Locating common programs... Checking compatibility between x:/usr/bin/echo.exe and builtin echo (if any)... Symbolic links are NOT supported. No symbolic links, so not testing for their testing... Good, your tr supports [:lower:] and [:upper:] to convert case. Using [:upper:] and [:lower:] to convert case. 3b1 dynix isc_2 opus super-ux aix dynixptx linux os2 svr4 altos486 epix lynxos os390 svr5 amigaos esix4 machten posix-bc ti1500 apollo fps machten_2 powerux titanos atheos freebsd mint qnx ultrix_4 aux_3 genix mips rhapsody umips beos gnu mpc sco unicos bsdos greenhills mpeix sco_2_3_0 unicosmk convexos hpux ncr_tower sco_2_3_1 unisysdynix cxux i386 netbsd sco_2_3_2 utekv cygwin irix_4 newsos4 sco_2_3_3 uts darwin irix_5 next_3 sco_2_3_4 uwin dcosx irix_6 next_3_0 solaris_2 vmesa dec_osf irix_6_0 next_4 stellar vos dgux irix_6_1 nonstopux sunos_4_0 dos_djgpp isc openbsd sunos_4_1 Which of these apply, if any? [os2] !!! Apparently there is no need to patch Configure. cp: cannot create regular file `t/lib/os2_base.t': Permission denied Operating system name? [os2] Process terminated by SIGSEGV Operating system version? [2] Build Perl for SOCKS? [n] Use the PerlIO abstraction layer? [y] Build a threading Perl? [n] Build Perl for multiplicity? [n] Use which C compiler? [gcc] Checking for GNU cc in disguise and/or its version number... Process terminated by SIGSEGV Process terminated by SIGSEGV Now, how can we feed standard input to your C preprocessor... Directories to use for library searches? [x:/usr/lib x:/usr/lib/mt] What is the file extension used for shared libraries? [dll] Checking for optional libraries... Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV What libraries to use? [-lsocket -lm -lbsd] What optimizer/debugger flag should be used? [-O2 -fomit-frame-pointer -malign-loops=2 -malign-jumps=2 -malign-functions=2 -s] Any additional cc flags? [-Zomf -Zmt -DDOSISH -DOS2=2 -DEMBED -I. -D_EMX_CRT_REV_=64] Let me guess what the preprocessor flags are... Any additional ld flags (NOT including libraries)? [-Zexe -Zomf -Zmt -Zcrtdll -Zstack 32000 -Zlinker /e:2] Checking your choice of C compiler and flags for coherency... Checking to see how big your integers are... Checking to see if you have long long... Checking to see how big your long longs are... Computing filename position in cpp output for #include directives... NOT found. Checking to see if you have int64_t... Checking which 64-bit integer type we could use... We could use 'long long' for 64-bit integers. Try to use 64-bit integers, if available? [n] Try to use maximal 64-bit support, if available? [n] Checking for GNU C Library... Shall I use x:/emx/bin/nm to extract C symbols from the libraries? [y] Process terminated by SIGSEGV Process terminated by SIGSEGV Process terminated by SIGSEGV Where is your C library? [x:/usr/lib/mt/c_import.lib] Extracting names from the following files for later perusal: Process terminated by SIGSEGV This may take a while... Process terminated by SIGSEGV **= Email 37 ==========================** Date: Wed, 24 Jul 2002 19:35:59 +0200 (CEST) From: "Christian Hennecke" Subject: Re: Building emacs On Wed, 24 Jul 2002 13:09:25 +0100, John Poltorak wrote: >I managed to build emacs v20.7 recently with some considerable help from >Masaru Nomiya, but it did involve a bit of manual intervention. John, could you assemble a binary distribution? I guess there are quite some people who would like to use the latest Emacs, but are not capable of building it themselves. Christian Hennecke **= Email 38 ==========================** Date: Wed, 24 Jul 2002 20:27:14 +0100 From: John Poltorak Subject: Re: wxWindows On Wed, Jul 24, 2002 at 09:01:36AM -0500, Dave Webster wrote: > If you have not read the latest OS/2 eZine issue, I put an article on there > concerning wxWindows. I am closing in on getting this product finished > (about 3-6 months of work left). Without rehashing all that was in the > article, wxWindows the worlds foremost Open Source cross platform GUI > toolkit available today. In the article you mentioned that you could do with some help getting it finished. What sort of things do you want people to do? You also mentioned something about Python support, but that there was no OS/2 binding yet. What does that actually mean? What work is involved? What other languages are supported? For instance could you use wxWindows with Pascal or even ADA? In case anyone hasn't read the article it's available here:- http://www.os2ezine.com/20020716/page_6.html -- John **= Email 39 ==========================** Date: Wed, 24 Jul 2002 20:58:11 +0100 From: "Csaba" Subject: Re: Using YACC when building FLEX On 24 Jul 2002, at 11:06, John Poltorak wrote: > On Wed, Jul 24, 2002 at 05:40:21AM -0400, Thomas Dickey wrote: [snip] > > The -o option isn't recognized by yacc or byacc. > > It's not really necessary > > (saves a line in the makefile). > > Which line? > IIRC, yacc produces a file called yy.tab.c So, for a dependency of foo.c on foo.y you'd have to write: foo.c : foo.y yacc $< move yy.tab.c $ at With -o foo.c : foo.y yacc -o $ at $< A .sig ! A .sig! My kingdom for a .sig! **= Email 40 ==========================** Date: Wed, 24 Jul 2002 20:58:11 +0100 From: "Csaba" Subject: RE: wxWindows On 24 Jul 2002, at 10:51, Dave Webster wrote: >> -----Original Message----- >> From: John Poltorak [mailto:jp at eyup.org] [snip] >> Is there any chance of Open Office being converted to use >>wxWindows? Maybe Mozilla too... > I've heard that there is a reasonable chance Open Office very well might. I sincerely doubt it, considering the sheer size of OpenOffice > As for Mozilla, [snip] Mozilla is heavily componentized. There are plenty of browsers out there already using Gecko, the Mozilla engine: Konqueror, Galeon, etc. Writing a wxWindows framework around the Gecko renderer is (drumroll) left as an exercise, apparently solved here: http://wxmozilla.sourceforge.net/ Ceci n'est pas un .signature **= Email 41 ==========================** Date: Wed, 24 Jul 2002 21:24:35 +0100 From: John Poltorak Subject: Re: Using YACC when building FLEX On Wed, Jul 24, 2002 at 08:58:11PM +0100, Csaba wrote: > On 24 Jul 2002, at 11:06, John Poltorak wrote: > > > On Wed, Jul 24, 2002 at 05:40:21AM -0400, Thomas Dickey wrote: > [snip] > > > The -o option isn't recognized by yacc or byacc. > > > It's not really necessary > > > (saves a line in the makefile). > > > > Which line? > > > > IIRC, yacc produces a file called yy.tab.c > So, for a dependency of foo.c on foo.y you'd have to write: > > foo.c : foo.y > yacc $< > move yy.tab.c $ at > > With -o > > foo.c : foo.y > yacc -o $ at $< So how would I incorporate that into this Makefile if I wanted to use yacc instead of bison? :- # make file for "flex" tool, emx+gcc release: $(MAKE) -f Makefile.os2 flex.exe \ CC="gcc -Zomf -O" O=".obj" A=".lib" AR="emxomfar" \ LDFLAGS="-s -Zcrtdll -Zstack 512" debug: $(MAKE) -f Makefile.os2 flex.exe \ CC="gcc -g" O=".o" A=".a" AR="ar" CFLAGS = -DOS2 -DSHORT_FILE_NAMES YACC = bison FLEX = flex FLEX_FLAGS = -ist .SUFFIXES: .c $O .c$O: $(CC) $(CFLAGS) -c $< FLEXLIB = fl$A FLEXOBJS = ccl$O dfa$O ecs$O gen$O main$O misc$O nfa$O parse$O \ scan$O skel$O sym$O tblcmp$O yylex$O LIBOBJS = libmain$O libyywrap$O flex.exe : $(FLEXOBJS) $(FLEXLIB) $(CC) $(LDFLAGS) -o $ at $(FLEXOBJS) $(FLEXLIB) first_flex: cp initscan.c scan.c $(MAKE) $(MFLAGS) flex $(FLEXLIB): $(LIBOBJS) $(AR) cru $(FLEXLIB) $(LIBOBJS) $(AR) s $(FLEXLIB) parse.h parse.c: parse.y $(YACC) -d -o parse.c parse.y scan.c : scan.l $(FLEX) $(FLEX_FLAGS) $(COMPRESSION) scan.l >scan.c scan$O : scan.c parse.h flexdef.h main$O : main.c flexdef.h ccl$O : ccl.c flexdef.h dfa$O : dfa.c flexdef.h ecs$O : ecs.c flexdef.h gen$O : gen.c flexdef.h misc$O : misc.c flexdef.h nfa$O : nfa.c flexdef.h parse$O : parse.c flexdef.h sym$O : sym.c flexdef.h tblcmp$O : tblcmp.c flexdef.h yylex$O : yylex.c flexdef.h skel.c: flex.skl mkskel.sh $(SHELL) mkskel.sh flex.skl >skel.c Maybe I should give up on this Makefile and try making one correctly with configure... -- John **= Email 42 ==========================** Date: Wed, 24 Jul 2002 22:17:00 -0500 (CDT) From: "xyzyx" Subject: Trying to configure autoconf Trying to configure, goes a little bit and then has this problem: config.status: creating config/Makefile sed: Couldn't open file d:tmp/cs27144-4943/subs-1.sed sed: Couldn't open file d:tmp/cs27144-4943/subs-2.sed config.status: creating tests/Makefile sed: Couldn't open file d:tmp/cs27144-4943/subs-1.sed sed: Couldn't open file d:tmp/cs27144-4943/subs-2.sed (continues on for each file it's trying to create) I see in my ux2 environment that I now have a TMPDIR=d:\tmp -- perhaps this is the cause? Well, let's find out... set TMPDIR=/tmp sh configure Then, it works. regards, Paul **= Email 43 ==========================** Date: Wed, 24 Jul 2002 22:18:39 -0500 (CDT) From: "xyzyx" Subject: Clearing the environment? Does anyone have a script to clear out the environment variables? I've got a ton of settings from my "normal" EMX setup which I'm pretty sure are interfering with UnixOS2. thanks, paul