> I'm using 6.2. Have you tried your 7.x clients with a 6.x > (or some other) > server? >
yes. the clients compiled with 7.x SDK bombs out on 6.x and other X. Hummingbird did a lot of changes in XDK headers and Dlls, I think that was causing EXPLOSIONS ;-) But my DX compiled with 6.2 XDK works fine on 7.x EXceed. Suhaib > Greg > > Suhaib Siddiqi <[EMAIL PROTECTED]>@opendx.watson.ibm.com on > 02/21/2001 09:06:50 PM > > Please respond to [email protected] > > Sent by: [EMAIL PROTECTED] > > > To: Gregory D Abram/Watson/[EMAIL PROTECTED], > "'[email protected] > '" <[email protected]> > cc: > Subject: RE: [opendx-dev] RE: Opendx MSVC > > > > > Greg, > > Are you using Exceed XDK 6.x or 7.x? If you are using XDK 7.0 then > obviously I am doing something very wrong. I thought dx.exe > was bombing > out > because it could not read XDk registry entries for XDK 7.0. > Well, that was > fixed after I downloaded new dx.c code. Now almost every > executable bombs > out with "memory references error message... memory cannot be read at > xxxxxxx" > > I went through XDk 7.0 documentation and noticed that calling > HCLXmInit(0 > and HCLXtInit etc are not needed any more. XDK 7.0 > documentation said, "Do > not call them, like you used to upto XDK 6.2, instead use > -DMOTIFAPP preprocessor". That was a minor problem. I edited all the > main.c > files and recompiled, still every executable bombs out with.. "memory > references error message... memory cannot be read at xxxxxxx" > > I guess we are looking for a lot of debugging to figure what > has changed > in Exceed 7.0 XDk which is causing all the executables to > bomb with memory > read/write errors. > > Suhaib > > -----Original Message----- > From: Gregory D Abram > To: [email protected] > Sent: 2/19/2001 8:37 PM > Subject: Re: [opendx-dev] RE: Opendx MSVC > > > internals.h is in src/exec/libdx > > I once gain successfully built OpenDX using my MSVC tools. > Sure enough, > ran > into a couple problems; here's what I did. > > First, I'm using a recent Cygwin download from Redhat. My > cygwin mounts > are: > > Device Directory Type Flags > c:\cygwin\bin /usr/bin user binmode > c:\cygwin\lib /usr/lib user binmode > \cygwin / user binmode > > I had trouble witn WinCVS making DOS-mode files, so I cvs co'ed on a > Unix > machine, tarred and copied to my cygwin machine. > > My exceed xdk is in (DOS) /cygwin/exceed or (cygwin) /exceed. > > I used this to set up my path: > > export PATH="/usr/local/src/dx/windows:/cygdrive/c/Program > Files/Microsoft > Visual Studio/VC98/Bin:/cygdrive/c/Program Files/Microsoft Visual > Studio/Common/MSDev98/Bin:/usr/local/bin:/usr/bin:/bin//cygdri > ve/c/jdk1. > 1.8/bin:/usr/X11R6/bin:." > > It seems cygwin's a bit odd about its path: it finds any .exe in the > path > before looking for shell files. I found that it was finding cygwin's > cpp > before the version in /usr/local/src/dx/windows, so I copied that to > /usr/local/src/dx/windows/dxcpp. > > I found a problem in the order of includes in > src/exec/libdx/message.c; > I > fixed it and checked in the fix. > > Then I used this shell file to configure my object directory: > > > if test "`cc 2>&1 | grep gcc`" != "" ; then > echo cc is gcc ... windows cc must precede gcc! > fi > > HERE="`pwd`" > export LIBPATH="/LIBPATH:C:/cygwin/exceed/xdk/lib" > export INCPATH="/INCPATH:C:/cygwin/exceed/xdk/include" > > ARCH=intelnt \ > AR=ar \ > RANLIB=ranlib \ > CC=cc \ > CPP=dxcpp \ > CXX=cxx \ > CXXCPP=cxxcpp \ > CFLAGS="-g" \ > CXXFLAGS="-g" \ > JAVAH=/cygdrive/c/jdk1.1.8/include \ > > JNIPATH=/cygdrive/c/jdk1.1.8/include:/cygdrive/c/jdk1.1.8/incl > ude/win32 > \ > JAVA40JAR=/cygdrive/c/Program\ > Files/Netscape/Navigator/Program/Java/Classes/java40.jar \ > bash ../../src/dx/configure > --x-includes=c:/cygwin/exceed/xdk/include \ > --x-libraries=c:/cygwin/exceed/xdk/lib \ > --prefix=/usr/local > > JAvaDX didn't configure for some reason; I'll look into that sometime, > but > the rest went fine. It then built, installed and ran fine. > > Greg > > > Suhaib Siddiqi <[EMAIL PROTECTED]>@opendx.watson.ibm.com on > 02/18/2001 08:15:51 PM > > Please respond to [email protected] > > Sent by: [EMAIL PROTECTED] > > > To: "'David Thompson '" <[EMAIL PROTECTED]> > cc: "'[email protected]'" <[email protected]> > Subject: [opendx-dev] RE: Opendx MSVC > > > > > In latest CVS code, in src/sexec/hwrender/opengl/hwPortOGL.c > the header internal.h is needed. It is not there? Where > this came from > > /* deal with DX/GL namespace collisions */ > #define Object dxObject > #define Matrix dxMatrix > #include "internals.h" <----- WHAT IS IT? Not in CVS? > > Suhaib > -----Original Message----- > From: David Thompson > To: Suhaib Siddiqi > Sent: 2/18/2001 7:59 PM > Subject: Re: Opendx MSVC > > Suhaib, > > Sorry I haven't gotten any further on this lately. We're just > finishing up our book and trying to get a license put together for > the eBook. Then I'm going to get back to the MSVC stuff. I was > actually trying to see if I could get Greg's stuff to work 2 weeks > ago--but was fighting it every step of the way. > > Once you get everything set up in the MSVC stuff, how do you update > the CVS tree? Do you have to do that by hand? If so, isn't there a > better way to work this out? > > David > > >David, > >Did you get MSVC compilation problems solved? > >I am working on latest CVS code and would be glad to give a MSVC > compiled > >binaries, with InstallShield Installer. I might create InstallShield > Web > >Installer, which will allow users to install directly from your URL > without > >downloading the zip files. Howeever if a user prefers to downlaod the > whole > >archive, he can still do so and install from local disk using > setup.exe. > > > >Suhaib > > -- > .............................................................. > .......... > ..... > David L. Thompson The University of Montana > mailto:[EMAIL PROTECTED] Computer Science Department > http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812 > Work Phone : (406)257-8530 > > > > >
