compile-file

[g2sv]

Can anybody give me compiled files of attached lisp files. it would be greate help is sombody explains me that procedure too or can give some Refrence documentation.

Regards,
Gav.

[Thom Ivancso]

Hello Gav,

Attached are the two files compiled into dll's for your use.

The procedure I used is the same one explained in the Intergration kit help under OSDM install dir\help\Common\documentation\integration_kit\reference\lispcompilation.html

I open up a session of OSDM and make sure my current folder is the one containing the lisp files I want to compile.

Then from the OSDM user input line I type (compile-file "abc.lsp") Once the hour glass disappears the dll file is created.

I am using Microsoft's Visual Studio 6.0 Professional which includes Visual C++ 6.0 to do the compiling of the lisp files.

Note: Borland C++ does not work for the Windows platform.

To load the dll file into OSDM I use this command syntax.

(load (format nil "path/file.lsp"))

The two files loaded into OSDM without any problems for me.

Hope this helps,
Cheers
Thom

[andrea]

I have tried to compile the filee abc.lsp but they give the following error to me... what I can make??

[Thom Ivancso]

Hello Andrea,

Are you using Microsoft's Visual Studio C++ 6.0 to compile this file?


Cheers
Thom

[andrea]

I have launch the command ("compile-file "c:/abc.lsp") give to Solidesigner .......

It goes well? or what I must make?

[clausb]

You either did not install a C++ compiler (VC++ 6.0) on the system, or for some reason the compiler executables (cl.exe, link.exe) are not in your PATH.

First, check whether Visual C++ is installed on your system.

If so, open a DOS shell window, then type "cl.exe". If the response is "cl.exe is not recognized as an internal or external command, operable program or batch file", then you know that the directory containing cl.exe is not in the PATH environment variable. Fix the PATH environment variable, then try compiling again.

Claus

PS: You might have to fix the INCLUDE and LIB environment variables as well.

[andrea]

The variable ones I must setting in :

Windows
SET INCLUDE=C:\Programmi\Microsoft Visual Studio .NET 2003\Vc7\bin
and
SET LIB=C:\Programmi\Microsoft Visual Studio .NET 2003\Vc7\bin


or OSD start

????????????

[clausb]

See also my reply in the other read on encrypting LISP files.

Setting the environment variable in the shell using the SET command will NOT be sufficient to fix your problem. You need to set them in the System Control Panel.

The INCLUDE environment variable only contains references to C/C++ header file directories, NOT to binary directories. The LIB environment variable refers to library file directories, NOT to binary directories either.

If you do not know what header files, libraries and binary files are, maybe you should rather re-run the Visual C++ setup program and have it set the environment variables for you.

Claus

[andrea]

I do not succeed just...
repeated installation of
"Visual Studio .NET 2003"
I have verified and as variable of system
I have:
LIB=C:\Programmi\Microsoft Visual Studio .NET 2003\SDK\v1.1\Lib\
INCLUDE=C:\Programmi\Microsoft Visual Studio .NET 2003\SDK\v1.1\include\

from solid I see this variable pear tree if launch......
gives always the usual error to me...

Like from the forum http://www.cocreateusers.org/forum/showthread.php?s=&threadid=5151

if launch the command cl.exe from one shell of dos gives error to me...

WHERE MISTAKE? WHERE MISTAKE? WHERE MISTAKE?

[Thom Ivancso]

Hello andrea,

Originally posted by andrea
I do not succeed just...
repeated installation of
"Visual Studio .NET 2003"

Visual Studio .NET 2003 will not work to compile the Lisp code for OneSpace Designer, you need to have Visual Studio 6.0 installed to be able to compile the Lisp code.

Cheers
Thom

[Andy Poulsen]

Hello Andrea,

We also tried compiling using Visual Studio .NET, and were unable to get it to work.

When I checked with CoCreate on this issue they said that ONLY Visual c++ 6.0 would work -- the later versions are NOT SUPPORTED.

I'm not sure what the differences are, but we got a copy of 6.0 just for the purpose of compiling OSD code. It's now old enough software that it's not too difficult or expensive to get a copy.

We were going to try to find a workaround for this issue, but since CoCreate said that we would most likely have problems doing that, and since it was so inexpensive just to get a copy, that's what we did.

Perhaps CoCreate has made some changes in the newer versions of OSD Modeling to support Visual Studio .NET or .Net 2003 -- if so, I'm sure Claus or another helpful person will let us know!

Good luck! I hope this helps!

andy

[clausb]

Andy: OSDM 2005 will indeed support VS.NET 2003 for LISP compilation.

Andrea: If you get an error when trying to run cl.exe from the DOS shell, it means that the directory which contains cl.exe is not in your PATH yet.

Claus

[andrea]

The rows cl.exe are in the folder...
C:\Programmi\Microsoft Visual Studio .NET 2003\Vc7\bin
various from those of the variable ones LIB and INCLUDE

A remedy or not? Or I must install Visual Study 6.0

THANKS

[clausb]

We do not support VS.NET 2003 with any of the released versions of OSDM, so yes, you will have to install VC++ 6 if you want to compile your LISP code. Alternatively, wait for the OSDM 2005 release which supports VS.NET 2003.

The name of the directory which contains cl.exe must be added to the PATH environment variable. INCLUDE is for header file directories only.

Claus

[andrea]

I have installed Visual Study 6, I have setting variable the total LIB and INCLUDES, and as for magic all it works

INFINITELY THANKS To ALL....