comp.os.os2.programmer.porting (Usenet) Saturday, 09-Oct-1999 to Friday, 15-Oct-1999 +----------------------------------------------------------------------------+ From: nkonll@eggman-network.hypermart.net 14-Oct-99 02:01:07 To: All 14-Oct-99 03:59:08 Subj: Stop others from using your computer!!! 622 From: nkonll@eggman-network.hypermart.net That's right....stop others from using your computer now! Desktop Blocker will password protect your Windows system so that nobody except for you will be able to access your desktop. Keep that co-worker off your computer, keep the babysitter off the Internet, and keep the wife from discovering your "collection"(you shouldn't be looking at that stuff anyway). Desktop Blocker is a FREE download at: http://www.eggman.net/desktopblocker Take a couple seconds to view our SCREENSHOT: http://www.eggman.net/software/dbss.htm Lock-up your desktop today!!! -EggMan Network trpirgbyddbfdfyiddoudbclyouwbmwhelhhrkcgzizozndperxk --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: @Home Network (1:109/42) +----------------------------------------------------------------------------+ From: nospam_ktk@netlabs.org 14-Oct-99 20:43:26 To: All 14-Oct-99 20:03:13 Subj: Compiling St6arOffice with EGCS From: "Adrian Gschwend" I talked to some people from StarOffice at Warpstock Europe and they told me, that they have a serious problem with the OS/2 port of it. Until now they used to compile the code with VAcpp 3.65 on OS/2 but now they use "namespaces" in the code and because VAcpp 4.0 does not support commandline compiling, they can't compile it on OS/2 anymore (the project is simply too big for the VAcpp 4.0 workframe). On Linux they use the Pentium optimized version of the GNU compiler and they tried the same on OS/2. But unfortunately there is a problem in the OS/2 port: (Taken from http://www.goof.com/pcg/os2/#Bugs) Known bugs: emxomf now traps (sometimes?) when compiling with -g (debug) switch. This is due to new format of debugging info (DWARF2). I do not know how to fix this. Use A.OUT format (no -Zomf) for debugging and pmgdb. Solution: This happens because pgcc uses new stabs format (-gstabs+) while emxomf understands only the standard stabs debugging info. I've partialy fixed this by adding a tiny command-line preprocessor to gcc. It scans argv[] and looks for both -Zomf and -g# where # is a number. If it finds one, it replaces -g# by -gstabs#. This doesn't always help, however. --- As you can see this is a limitation in EMX, we now have to find people who are able to fix this (which will not be an easy task I think). We are already in contact with Eberhard Mattes but we need more support. If you think you are able to fix this, please get in contact with Oliver Braun . Please JUST reply if you really think you can help StarDivision. A StarOffice without debug informations can not be tested and if noone can fix this limitation, Sun can not provide a new version for OS/2 ! So you see this is important for the future of StarOffice on OS/2. Thanks for your support Adrian Gschwend @ OS/2 Netlabs http://www.netlabs.org --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: OS/2 Netlabs (1:109/42) +----------------------------------------------------------------------------+ From: robmv@ibm.net 14-Oct-99 16:19:21 To: All 14-Oct-99 20:03:13 Subj: Re: Compiling St6arOffice with EGCS From: Robert Marcano Este es un mensaje de varias partes en formato MIME. --------------9B0739FDDDD473E461397F2C Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit What???VisualAge 4.0 include on an extra CD command line compilers dor OS/2 and for Windows, (3.6 level) with all VisualAge 4.0 support (namespaces, etc....) Adrian Gschwend escribi¢: > I talked to some people from StarOffice at Warpstock Europe and they told me, > that they have a serious problem with the OS/2 port of it. Until now they > used to compile the code with VAcpp 3.65 on OS/2 but now they use > "namespaces" in the code and because VAcpp 4.0 does not support commandline > compiling, they can't compile it on OS/2 anymore (the project is simply too > big for the VAcpp 4.0 workframe). On Linux they use the Pentium optimized > version of the GNU compiler and they tried the same on OS/2. But > unfortunately there is a problem in the OS/2 port: > > (Taken from http://www.goof.com/pcg/os2/#Bugs) > > Known bugs: > > emxomf now traps (sometimes?) when compiling with -g (debug) switch. This is > due to new format of debugging info (DWARF2). I do not know how to fix this. > Use A.OUT format (no -Zomf) for debugging and pmgdb. > > Solution: This happens because pgcc uses new stabs format (-gstabs+) while > emxomf understands only the standard stabs debugging info. I've partialy > fixed this by adding a tiny command-line preprocessor to gcc. It scans argv[] > and looks for both -Zomf and -g# where # is a number. If it finds one, it > replaces -g# by -gstabs#. This doesn't always help, however. > --- > > As you can see this is a limitation in EMX, we now have to find people who > are able to fix this (which will not be an easy task I think). We are already > in contact with Eberhard Mattes but we need more support. If you think you > are able to fix this, please get in contact with Oliver Braun > . Please JUST reply if you really think you can help > StarDivision. > > A StarOffice without debug informations can not be tested and if noone can > fix this limitation, Sun can not provide a new version for OS/2 ! So you see > this is important for the future of StarOffice on OS/2. > > Thanks for your support > > Adrian Gschwend > @ OS/2 Netlabs > http://www.netlabs.org --------------9B0739FDDDD473E461397F2C Content-Type: text/x-vcard; charset=us-ascii; name="robmv.vcf" Content-Transfer-Encoding: 7bit Content-Description: Tarjeta para Robert Marcano Content-Disposition: attachment; filename="robmv.vcf" begin:vcard n:Marcano Varela;Robert Jes£s x-mozilla-html:TRUE org:Programaci¢n Mecanizada C.A. (PROMCA) adr:;;CCCT, 1ra Etapa, piso 2, oficina 205, Chuao;Caracas;Miranda;1060;Venezuela version:2.1 email;internet:robmv@ibm.net title:System Architect tel;fax:(+582) 9591729 tel;home:(+5816) 6218891 tel;work:(+582)9 591665 note;quoted-printable:Certified VisualAge for Smalltalk Associate Developer=0D=0ACertified VisualAge for C++ Associate Developer=0D=0ACertified OS/2 Warp Engineer x-mozilla-cpt:;0 fn:Robert Jes£s Marcano Varela end:vcard --------------9B0739FDDDD473E461397F2C-- --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: =?iso-8859-1?Q?Programaci=F3n?= Mecanizada C.A. ( (1:109/42) +----------------------------------------------------------------------------+ From: nospam_ktk@netlabs.org 14-Oct-99 23:04:18 To: All 14-Oct-99 20:03:13 Subj: Re: Compiling St6arOffice with EGCS From: "Adrian Gschwend" On Thu, 14 Oct 1999 16:19:43 -0600, Robert Marcano wrote: >What???VisualAge 4.0 include on an extra CD command line compilers dor OS/2 and >for Windows, (3.6 level) with all VisualAge 4.0 support (namespaces, etc....) so this would be cool, StarDiv told me that there are no commandline tools, I have to ask them. Thanks for your info cu Adrian --- Adrian Gschwend @ OS/2 Netlabs ICQ: 22419590 ktk@netlabs.org ------- The OS/2 OpenSource Project: http://www.netlabs.org --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: OS/2 Netlabs (1:109/42) +----------------------------------------------------------------------------+ From: paul_floyd@see.sig 15-Oct-99 10:26:15 To: All 15-Oct-99 10:27:10 Subj: Re: Compiling St6arOffice with EGCS From: Paul FLOYD Robert Marcano wrote: > > What???VisualAge 4.0 include on an extra CD command line compilers dor OS/2 and > for Windows, (3.6 level) with all VisualAge 4.0 support (namespaces, etc....) > This is not correct, to my knowledge. The VisualAge C++ 4.0 Professional for OS/2 and Windows NT (or whatever the catchy name for it is) contains 4 CDs. 2 are for NT, which I'll ignore, and the other 2 are for OS/2. The first is VAC++ 4.0, which claims ISO C++ compliance. This is intended for use with the IDE. It is possible to build from the command line, but not using traditional style makefiles, you have to use the projects created with the IDE. This product cannot debug C source or DLLs either. The second disk has VAC++ 3.6.5. This is a traditional command line compiler (icc?), and can work with traditional make files (nmake?). It has a separate debugger (icat? ipmd?) which can debug DLLs and C code. However, the level of C++ compliance is back at the 1992 level, with a few bits added. I can't remember exactly what though, you'd either have to look in the IBM web pages or search the IBM VAC++ newsgroups. [snip] Regards Paul -- Paul Floyd Focal Ingenierie Sud Mail: paul underscore floyd at focal dot fr Sig tagline under contemplation. --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: Focal Ingenierie Sud (1:109/42) +----------------------------------------------------------------------------+ From: cwr@cts.com 15-Oct-99 09:32:28 To: All 15-Oct-99 10:27:10 Subj: Re: Compiling St6arOffice with EGCS From: Will Rose In comp.os.os2.programmer.tools Adrian Gschwend wrote: : On Thu, 14 Oct 1999 16:19:43 -0600, Robert Marcano wrote: :>What???VisualAge 4.0 include on an extra CD command line compilers dor OS/2 and :>for Windows, (3.6 level) with all VisualAge 4.0 support (namespaces, etc....) : so this would be cool, StarDiv told me that there are no commandline tools, I : have to ask them. AFAIK the command line compiler in 4.0 (3.6), and isn't to the current C++ standard. (I don't know if it includes namespaces). The 4.0 compiler is current. Will cwr@crash.cts.com --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: CTS Network Services (1:109/42) +----------------------------------------------------------------------------+ From: obr@stardivision.de 15-Oct-99 11:18:14 To: All 15-Oct-99 10:27:11 Subj: Re: Compiling StarOffice with EGCS From: Oliver Braun > What???VisualAge 4.0 include on an extra CD command line compilers > dor OS/2 and for Windows, (3.6 level) with all VisualAge 4.0 > support (namespaces, etc....) That`s simply not true. The IBM documentation ?Choosing the Right C++ CD? of the Visual Age 4.0 Package states in the section ?C++ Standard Compliance? for Version 4.0 ANSI/ISO 1998 C++ Standard and for the 3.6 ANSI 1992 Draft. If you try to compile a source file with namespaces in it, the 3.6 compile simply states: namespace is not a type name. If there is any undocumented compiler switch to make namespaces work with the 3.6 compiler, any report of it will be appreciated. Oliver Braun StarOffice Software Entwicklungs GmbH --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: Star Division GmbH, Hamburg, Germany (1:109/42) +----------------------------------------------------------------------------+ From: shikojo@hotmail.com 15-Oct-99 14:04:20 To: All 15-Oct-99 14:34:17 Subj: Your New StartPage ! From: shikojo@hotmail.com (Shikojo) I found the best ever site on the net !!! Here you could find best Computers, Internet, Games, Entertainment and other links ! http://goldcity.hello.to/ -- http://hey.to/netmoney The Revolution In Internet Begins ! Get Paid By The Net ! Make Money Surfing The Web ! --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: Get Paid By The Net (1:109/42) +----------------------------------------------------------------------------+ From: mamodeo@stny.rr.com 15-Oct-99 10:24:04 To: All 15-Oct-99 14:34:17 Subj: Re: Compiling St6arOffice with EGCS From: Marty Adrian Gschwend wrote: > > I talked to some people from StarOffice at Warpstock Europe and they told me, > that they have a serious problem with the OS/2 port of it. Until now they > used to compile the code with VAcpp 3.65 on OS/2 but now they use > "namespaces" in the code and because VAcpp 4.0 does not support commandline > compiling, they can't compile it on OS/2 anymore (the project is simply too > big for the VAcpp 4.0 workframe). On Linux they use the Pentium optimized > version of the GNU compiler and they tried the same on OS/2. But > unfortunately there is a problem in the OS/2 port: > > (Taken from http://www.goof.com/pcg/os2/#Bugs) > > Known bugs: > > emxomf now traps (sometimes?) when compiling with -g (debug) switch. This is > due to new format of debugging info (DWARF2). I do not know how to fix this. > Use A.OUT format (no -Zomf) for debugging and pmgdb. Is there any reason they wouldn't want to use the A.OUT format? I've got full debug info in MAME (producing a 41MB executable) and it works great. All I had to do is leave everything in A.OUT form and use EMXBIND as the last step in the build process. All this does is add a reliance on the EMX runtime DLLs, but who doesn't have them nowadays? - Marty --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: IBM Global Services North -- Burlington, Vermont, (1:109/42) +----------------------------------------------------------------------------+ From: robmv@ibm.net 15-Oct-99 11:43:12 To: All 15-Oct-99 14:34:17 Subj: Re: Compiling St6arOffice with EGCS From: Robert Marcano Este es un mensaje de varias partes en formato MIME. --------------F34DCDF940D3EA154CA45FD9 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sorry for the mistake, I use the IDE, and I erroneously interpreted the problem. Thanks for the info. post this question to the newsgroups in news.software.ibm.com too Will Rose escribi¢: > In comp.os.os2.programmer.tools Adrian Gschwend wrote: > : On Thu, 14 Oct 1999 16:19:43 -0600, Robert Marcano wrote: > > :>What???VisualAge 4.0 include on an extra CD command line compilers dor OS/2 and > :>for Windows, (3.6 level) with all VisualAge 4.0 support (namespaces, etc....) > > : so this would be cool, StarDiv told me that there are no commandline tools, I > : have to ask them. > > AFAIK the command line compiler in 4.0 (3.6), and isn't to the > current C++ standard. (I don't know if it includes namespaces). > The 4.0 compiler is current. > > Will > cwr@crash.cts.com --------------F34DCDF940D3EA154CA45FD9 Content-Type: text/x-vcard; charset=us-ascii; name="robmv.vcf" Content-Transfer-Encoding: 7bit Content-Description: Tarjeta para Robert Marcano Content-Disposition: attachment; filename="robmv.vcf" begin:vcard n:Marcano Varela;Robert Jes£s x-mozilla-html:TRUE org:Programaci¢n Mecanizada C.A. (PROMCA) adr:;;CCCT, 1ra Etapa, piso 2, oficina 205, Chuao;Caracas;Miranda;1060;Venezuela version:2.1 email;internet:robmv@ibm.net title:System Architect tel;fax:(+582) 9591729 tel;home:(+5816) 6218891 tel;work:(+582)9 591665 note;quoted-printable:Certified VisualAge for Smalltalk Associate Developer=0D=0ACertified VisualAge for C++ Associate Developer=0D=0ACertified OS/2 Warp Engineer x-mozilla-cpt:;0 fn:Robert Jes£s Marcano Varela end:vcard --------------F34DCDF940D3EA154CA45FD9-- --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: =?iso-8859-1?Q?Programaci=F3n?= Mecanizada C.A. ( (1:109/42) +----------------------------------------------------------------------------+ From: ilya@math.ohio-state.edu 15-Oct-99 16:39:12 To: All 15-Oct-99 21:58:14 Subj: Re: Compiling St6arOffice with EGCS From: ilya@math.ohio-state.edu (Ilya Zakharevich) [A complimentary Cc of this posting was sent to Marty ], who wrote in article <38073908.303BE79C@stny.rr.com>: > Is there any reason they wouldn't want to use the A.OUT format? > > I've got full debug info in MAME (producing a 41MB executable) and it > works great. All I had to do is leave everything in A.OUT form and use > EMXBIND as the last step in the build process. > > All this does is add a reliance on the EMX runtime DLLs, but who doesn't > have them nowadays? What the heck? Debug in a.out, and make a production copy in omf. Ilya --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: Department of Mathematics, The Ohio State Univers (1:109/42) +----------------------------------------------------------------------------+ From: dannospammo@us.ibm.com 15-Oct-99 15:57:12 To: All 15-Oct-99 21:58:14 Subj: Re: Compiling St6arOffice with EGCS From: "Dan Nimick" On Thu, 14 Oct 1999 20:43:52 +0200 (CDT), Adrian Gschwend wrote: >VAcpp 4.0 does not support commandline compiling To compile VAge 4.0 from the command line starting from a traditional MAKE file: Run the MAKE2CFG utility (ex. make2cfg -f makefile) This will give you a pretty good version of a ICC file that can be used with: vacbld xxx.icc where xxx.icc is the file created by make2cfg. Now, I've only done this once, and it was a small project (one EXE, no DLL), but it worked like a champ once I got my MAKE file useable by the make2cfg utility. The file had a bunch of junk the utility didn't understand. I ended up using VAge to create a make file in its format as a template. Then I put all my stuff in that template, then ran make2cfg and viola!! Luck... Dan Nimick --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: Global Network Services - Remote Access Mail & Ne (1:109/42) +----------------------------------------------------------------------------+ From: bschwand@dvart.com 15-Oct-99 13:47:08 To: All 15-Oct-99 21:58:15 Subj: Re: Print to graphic [was Re: METAFILE CONVERTION] From: bruno schwander the best in my opinion is to print to a postscript file using a postscript printer driver. then use ghostscript to create an EPS file from it. I love postscript, if anything goes wrong, you can always look at the source code :-) bruno Mat Kramer wrote: > A more general question: is there a printer driver that will allow > output to be saved as a file and then imported into Word 97 as a > graphic? Word will import HPGL -- which driver should I use for that? > > bv wrote: > > You could get the Windows metafile into an OS/2 metafile format simply by > > printing it under WinOS/2 and intercepting the spoolfile. The spoolfile is an > > OS/2 metafile, but it is probably not in a format your application will be able > > to handle. > > > > I think the best way is to convert them to a format like EPS, and exchange > > that. This should work for some types of metafiles. > > -- > Mat Kramer [MekTek] mek@compuserve.com > VyperHelp: http://ourworld.compuserve.com/homepages/mek/vyper.htm --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: Posted via Supernews, http://www.supernews.com (1:109/42) +----------------------------------------------------------------------------+ +============================================================================+