Compile Opensees v1.7.4,error?

lish hit · Post by **lish hit** » Thu Aug 02, 2007 6:47 am

I download the code of version 1.7.4.

My system is windows. The error occurs with "tcl.lib". Does anyone successfully compile this version. Give me some suggestions?

Thanks!

Post by **fmk** » Thu Aug 02, 2007 9:56 am

you either have not installed tcl or you have installed it in the wrong location. search the message board or read the documentation for solution.

lish hit · Post by **lish hit** » Sat Aug 04, 2007 2:26 am

Thanks!

I did v1.7.3 well but fail when v1.7.4. So, I don't think that the tcl installed in the wrong location. The reason may be in the codes.

aarenas · Post by **aarenas** » Fri Nov 23, 2007 7:27 am

lish hit wrote:Thanks!

I did v1.7.3 well but fail when v1.7.4. So, I don't think that the tcl installed in the wrong location. The reason may be in the codes.

Hi,

Could you solve this problem?, I have the same problem. I have installed tcl in different directories including c:\program files or c:\tcl but nothing happend. Even I downloaded extras tcl libraries but I can't solve it. I did a search for this file and it is not present in my hard drive. When I installed Tcl/Tk, there is no option for adding extras stuff, like libraries, the installer just ask for the installation directory and it runs a default installation. Can anybody help us or send us the file. Thanks

koduru · Post by **koduru** » Fri Nov 23, 2007 10:29 am

Hello Juan,

I'm sorry that my suggestion did not work. If you have TCL installed to the correct directory already, the opensees visual c project may have the TCL directory incorrectly configured. Unfortunately, I'm not familiar with Visual C++ 6.0 so I cannot tell you exactly where the setting is, but I can give you an idea of what to look for. In Visual C++ 2005 express, I can right-click the OpenSees project under the solution explorer and select 'Properties'. I then go to 'Configuration Properties', 'C/C++', and then 'Command line'. You should see something like this at the top of the command line input:
/Od /I "..\..\..\src\system_of_eqn\linearSOE\diagonal" /I "c:\Program Files\tcl\include" /I

You should make sure that the path for TCL\include is the correct one for your system. I hope that helps.

-Robbie

The above answer is on one of the message threads in this board. This advice helped me (I use visual studio C++ 6.0). There was no "tcl\include" in the Command line. So, I added the line "c:\Program Files\tcl\include" (without quotes).
I could compile without errors for tcl after doing this.

Hope this helps

aarenas · Post by **aarenas** » Mon Nov 26, 2007 5:47 pm

Thanks for your help, but that is not going to work. I already check the path and they are right. The problem is that there is no such of library in my computer. I did search it and it is not in my hard drive.

Can somebody send me that library.

Thanks

koduru wrote:
Hello Juan,

I'm sorry that my suggestion did not work. If you have TCL installed to the correct directory already, the opensees visual c project may have the TCL directory incorrectly configured. Unfortunately, I'm not familiar with Visual C++ 6.0 so I cannot tell you exactly where the setting is, but I can give you an idea of what to look for. In Visual C++ 2005 express, I can right-click the OpenSees project under the solution explorer and select 'Properties'. I then go to 'Configuration Properties', 'C/C++', and then 'Command line'. You should see something like this at the top of the command line input:
/Od /I "..\..\..\src\system_of_eqn\linearSOE\diagonal" /I "c:\Program Files\tcl\include" /I

You should make sure that the path for TCL\include is the correct one for your system. I hope that helps.

-Robbie
The above answer is on one of the message threads in this board. This advice helped me (I use visual studio C++ 6.0). There was no "tcl\include" in the Command line. So, I added the line "c:\Program Files\tcl\include" (without quotes).
I could compile without errors for tcl after doing this.

Hope this helps

rjaeger · Post by **rjaeger** » Mon Nov 26, 2007 8:57 pm

Hello,

tcl.lib is what is being compiled when making the opensees executable. If tcl.lib isn't available, it means that the TCL project isn't successfully compiling and your problem is probably with your tcl installation. Check for errors in the output and see if that helps.

-Robbie

aarenas · Post by **aarenas** » Tue Nov 27, 2007 10:42 am

Hey Robbie,

When I load the Opensees solution, it loaded 24 projects, but there is no one called tcl. Maybe that is the problem?. Thanks

Alfredo

rjaeger wrote:Hello,

tcl.lib is what is being compiled when making the opensees executable. If tcl.lib isn't available, it means that the TCL project isn't successfully compiling and your problem is probably with your tcl installation. Check for errors in the output and see if that helps.

-Robbie

rjaeger · Post by **rjaeger** » Tue Nov 27, 2007 5:28 pm

Yes, I believe that is your problem. Maybe try reloading the solution file into Visual C++ to see if that helps any. If it doesn't, you can add the tcl project to your solution by right-clicking the solution (labeled Solution 'OpenSees' for me) in the solution explorer (on the left in VC++ 2005), select add, then choose existing project. When the dialog comes up, browse to your OpenSees source directory and you should be able to find the tcl.vcproj in Opensees/Win32/proj/tcl.

Hope that helps,
-Robbie

aarenas · Post by **aarenas** » Wed Nov 28, 2007 8:12 am

Robbie, how many project component do you have in your opensees soluction. I did your suggestion and that problem was solve but know instead of having 1 error I have over 12,000 !!, but is pretty much the same error "error LNK2001". I going to look info about it. Any other suggestion?

Thank you very much for your help

Alfredo

koduru · Post by **koduru** » Wed Nov 28, 2007 12:36 pm

I too have a linking errors for OpenSees and OpenSeesTk projets. All other errors are addressed and other projects complied successfully. The errors in both projects are similar to the following:

renderer.lib(OpenGlDevice.obj) : error LNK2019: unresolved external symbol __imp__DefWindowProcA@16 referenced in function "long __stdcall WndProc(struct HWND__ *,unsigned int,unsigned int,long)" (?WndProc@@YGJPAUHWND__@@IIJ@Z)

The other types of errors are:

winMain.obj : error LNK2019: unresolved external symbol __imp__SetMessageQueue@4 referenced in function _WinMain@16
winMain.obj : error LNK2019: unresolved external symbol __imp__MessageBoxA@16 referenced in function _Tcl_AppInit
renderer.lib(OpenGlDevice.obj) : error LNK2001: unresolved external symbol __imp__MessageBoxA@16
winMain.obj : error LNK2019: unresolved external symbol __imp__MessageBeep@4 referenced in function _Tcl_AppInit

Any help to fix these will be greatly appreciated!!
Thanks in advance,
Smitha

rjaeger · Post by **rjaeger** » Thu Nov 29, 2007 7:23 pm

aarenas wrote:Robbie, how many project component do you have in your opensees soluction. I did your suggestion and that problem was solve but know instead of having 1 error I have over 12,000 !!, but is pretty much the same error "error LNK2001". I going to look info about it. Any other suggestion?

Thank you very much for your help

Alfredo

Hi,

Can you give some examples of the errors? That may help us to find out where the problem is coming from.

-Robbie

rjaeger · Post by **rjaeger** » Thu Nov 29, 2007 7:27 pm

koduru wrote:I too have a linking errors for OpenSees and OpenSeesTk projets. All other errors are addressed and other projects complied successfully. The errors in both projects are similar to the following:

renderer.lib(OpenGlDevice.obj) : error LNK2019: unresolved external symbol __imp__DefWindowProcA@16 referenced in function "long __stdcall WndProc(struct HWND__ *,unsigned int,unsigned int,long)" (?WndProc@@YGJPAUHWND__@@IIJ@Z)

The other types of errors are:

winMain.obj : error LNK2019: unresolved external symbol __imp__SetMessageQueue@4 referenced in function _WinMain@16
winMain.obj : error LNK2019: unresolved external symbol __imp__MessageBoxA@16 referenced in function _Tcl_AppInit
renderer.lib(OpenGlDevice.obj) : error LNK2001: unresolved external symbol __imp__MessageBoxA@16
winMain.obj : error LNK2019: unresolved external symbol __imp__MessageBeep@4 referenced in function _Tcl_AppInit

Any help to fix these will be greatly appreciated!!
Thanks in advance,
Smitha

Hi Smitha,

Have a look at Alisa Neeman's page on Visual C++ problems http://www.soe.ucsc.edu/~aneeman/VCgotchas.html

You may need to delete the .dsp or .dsw file in your OpenSees/Win32/ directory and then try rebuilding the entire OpenSees project (clean and build or just rebuild).

-Robbie

aneeman · Post by **aneeman** » Sat Dec 01, 2007 9:21 am

It is the .ncb file you need to delete to get rid of cached errors..

cheers,

alisa

>>>>
Hi Smitha,

Have a look at Alisa Neeman's page on Visual C++ problems http://www.soe.ucsc.edu/~aneeman/VCgotchas.html

You may need to delete the .dsp or .dsw file in your OpenSees/Win32/ directory and then try rebuilding the entire OpenSees project (clean and build or just rebuild).

-Robbie
<<<

rjaeger · Post by **rjaeger** » Mon Dec 03, 2007 4:23 pm

Hi,

I was just having some external link issues and realized that I forgot to follow the MS Platform SDK installation procedures completely.

Make sure you have done each of these (from the MS website):

Using Visual C++ 2005 Express Edition with the Microsoft Platform SDK

By Brian Johnson,
Microsoft Corporation

You can use Visual C++ Express to build powerful .NET Framework applications immediately after installation. In order to use Visual C++ Express to build Win32 applications, you'll need to take just a few more steps. I'll list the steps necessary for building Win32 applications using Visual C++ Express.
Step 1: Install Visual C++ Express.

If you haven't done so already, install Visual C++ Express.

Step 2: Install the Microsoft Platform SDK.

Install the Platform SDK over the Web from the Download Center. Follow the instructions and install the SDK for the x86 platform.

Step 3: Update the Visual C++ directories in the Projects and Solutions section in the Options dialog box.

Add the paths to the appropriate subsection:

* Executable files: C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Bin
* Include files: C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include
* Library files: C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Lib

Note: Alternatively, you can update the Visual C++ Directories by modifying the VCProjectEngine.dll.express.config file located in the \vc\vcpackages subdirectory of the Visual C++ Express install location. Please make sure that you also delete the file "vccomponents.dat" located in the "%USERPROFILE%\Local Settings\Application Data\Microsoft\VCExpress\8.0" if it exists before restarting Visual C++ Express Edition.

Step 4: Update the corewin_express.vsprops file.

One more step is needed to make the Win32 template work in Visual C++ Express. You need to edit the corewin_express.vsprops file (found in C:\Program Files\Microsoft Visual Studio 8\VC\VCProjectDefaults) and

Change the string that reads:

AdditionalDependencies="kernel32.lib"

to

AdditionalDependencies="kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib"