CompuServe Thread

can't get examples run

6 messages in this thread
#61678From: Dietmar RudolphOct 14, 1993 12:33 PM
Hi everybody, I just got my CDK for a review and cannot get the enclosed examples to compile and run. This is my environment: COMSPEC=C:\COMMAND.COM PCTOOLS=C:\PCTOOLS\DATA TEMP=d:\temp PROMPT=$p$g PATHX=C:\PCTOOLS;C:\;C:\DOS5;C:\UTILITY;C:\CORELDRV;C:\WORD5;E:\DBASE;C:\NWLITE PATH=C:\PCTOOLS;C:\;C:\DOS5;C:\UTILITY;C:\CORELDRV;C:\WORD5;E:\DBASE;C:\NWLITE; f:\highc\bin;f:\phar386\bin;f:\make MWLIB=F:\HIGHC\SMALL CYBER=f:\CDK PHAREXE=f:\PHAR386\BIN LINK=F:\PHAR386\BIN DISPLAY=CyADIdisp SENSOR1=CyADISensor PATHDXF=F:\CDK\DXFS RDPADI=F:\CDK\DRIVER\RC85XGA.EXP DGPADI=F:\CDK\DRIVER\DGPSUMI.EXP ADICFG=F:\CDK\DRIVER I tried different make utilities but keep getting make: don't know how to make main.obj with all the example programs. So there must be something else wrong. Any help welcome. Thanks Dietmar
#61870From: Tony BrandOct 15, 1993 3:12 PM
OK, well, I'll take a stab at helping. For a start off, the LINK environment var needs to be set to the link program itself, in your case, the line should read SET LINK=F:\PHAR386\BIN\386link.exe Then also for good measure, add SET LINKOPTS=-PRIV -BACKCOMPAT (See readme doc for why this is in there) OK, that's as much as I know, as I am not an AutoCAD user and so haven;t Dread and therefore don't knwo about ADI Drivers. I have found it easier to start off with a VESA compatible display, since it is easy to find VESA diroidrivers. Tony Brand Autodesk New Jersey Multimedia Division, and also a new CDK user
#62126From: Dietmar RudolphOct 18, 1993 2:47 AM
Thanks Tony, > Link must point to the executable itself. Fine, I haven't seen that in the docs. FWIW: Why isn't it possible to have a _consistent_ use of these variables? Unfortunately, I don't even come as far as linking. It seem that my MAKEs are quite unhappy with the supplied makefile. I changed the chain makefile to something like main.obj : main.cpp $(CC) main.cpp -c $(CFLAGS) $< This let's highC _try_ to compile main.cpp at least. Unfortunately it breaks with some syntax errors in one of the Autodesk supplied header files: unexpected symbol: 'try' in ../../head\event.hpp, L106/C30 I mailed the exact error messages to Jonas Ruikis [ADESK] who was so kind to answer via mail, but was of no help either (up to now). Still any help welcome. Next try: Have _you_ tried to get the examples compiled and run? Which MAKE did you use? If it's PD, could you mail me a copy? Dietmar Rudolph
#62185From: Tony BrandOct 18, 1993 1:39 PM
Well, I'm no expert, but the sample programs all compiled for me. I had similar trouble to you and was advised that MWMAKE was "shaky". Downloading new make files from the CDK library fixed the problem but I found it more effective to use a make program from the Microsoft compiler. That works really well! Makes are all pretty generic.
#62291From: Dietmar RudolphOct 19, 1993 3:14 AM
> Good luck Seem pretty needed 🙁 Here's what I learned up to now: – wrong compiler I have Metaware 3.11 (the current version), I need 3.04 or 3.1@25 (?) – wrong CDK I received 1.0 from Autodesk, current is 1.01 – wrong header files The supplied are buggy, corrected ones are on CIS. – wrong make files Newer are on CIS also. – wrong environment variables Never trust the documentation, get CyTechNotes #1 instead. – wrong drivers Don't believe Adesk would be able to support it's own specs. Current ADI is 4.2, CDK needs 4.1. And remember that I'm not a _user_ who wants to get real work done with this not yet finished Adesk product. I'm only an editor who wanted to write about 'how easy it is to create Cyberspace applications using CDK'.
#62482From: Dietmar RudolphOct 20, 1993 5:23 AM
Learn something new every day: > – wrong header files > The supplied are buggy, corrected ones are on CIS. The correct ones are _not_ on CIS, but in v1.01. > – wrong make files > Newer are on CIS also. These _are_ in Library 5. > – wrong environment variables > Never trust the documentation, get CyTechNotes #1 instead. CyTechNote #1 does _not_ talk on environment variables. There's a file in Lib 5 that does. > – wrong drivers > Don't believe Adesk would be able to support it's own specs. Current ADI > is 4.2, CDK needs 4.1. CDK _does_ support ADI 4.2.