Steema Central

I get this error when ever i try to load and compile example .cpp files. I am using CB2007/2009.

Thanks. NSM

Hi nile,

Are you trying to compile full demo project? It's Tee8New.bdsproj/Tee8New.bpr at C:\Program Files\Steema Software\TeeChart 8.04 for Delphi 2007\Examples\Features C++. I have the impression that you are trying to compile single units. The error message you get is because the units you are trying to compile don't find the base unit for demo examples.

Thanks. Found the project - not sure what i was thinking at the time!!

However, building the project yields the following error.

Link32 error Fatal: unable to open file TeeDesignOptions.obj

I did find a reference to this obj in the source code debug folder, and added a reference to it from the project options, but I get the same error when i do a re-build

nsm

Hi nile,

This is a known issue as you can see on this thread. It should alread be fixed in v8.04. Can you confirm the TeeChart version you are using?

Thanks in advance.

Narcis,

I am using v8.04. I also added the two .pas files as recommended by the topic link you supplied, specifically teexpform.pas, teedesignoptions.pas, but the compiler still complains with:

[BCC32 Error] Tee8New.cpp(526): E2303 Type name expected
Full parser context
Tee8New.cpp(427): parsing: int __stdcall WinMain(void *,void *,char *,int)

and the line

RegisterClass(__classid(TSurfaceSidesDemo));

The other issue is of course, this is to get your example source to compile in CB2007 - as part of the demo pack - but if you don't have access to the source code - then what?

cheers, nile.

Hi nile,

Can you please try using the demo here?

Thanks in advance.

Hi Narcis,

The compiler complained:

[ILINK32 Error] Fatal: Unable to open file 'TEEDESIGNOPTIONS.OBJ'

So we are on the same page, for now, all i have installed is a registered version of your trial, and as such no such file exits in the trial installed folders.

rgds nile.

Hi nile,

Have you tried adding TeeDesignOptions.pas from v8's sourcecode? We will try to fix this for the next maintenance release.