problems related to CVS and debug vs. release configurations

For developers writing C++, Fortran, Java, code who have questions or comments to make.

Moderators: silvia, selimgunay, Moderators

Post Reply
GunAndRose
Posts: 44
Joined: Wed Oct 26, 2005 2:23 pm
Location: San Francisco, CA

problems related to CVS and debug vs. release configurations

Post by GunAndRose » Mon Feb 05, 2007 8:54 am

I did the follwing for the source code before compiling in VC++2005:

1. check out the Source code from PEER
2. initiate a local repository in C: drive
3. import the checked out source code into the local repository
4. check out a working copy from the local Repository

However, I got two problems:

1. the lib files checked out from LocRepository are different with those in the PEER codes, So I had to copy the PEER lib files into the working copy,

Btw: I used
cvs –d :local:c:/ localRepository import OpenSees PEER WDIFF173
for importing the PEER codes into LocRepository
and
cvs –d :local:c:/localRepository checkout opensees
for checking out the working copy.


2. this problem has two folds:

2.1 while compiling the working copy in the DEBUG config, everything is OK and an executive file of OpenSees.exe was generated in folder ..\win32\bin. This exe file works correctly for current tcl files I coded. But this should be happen since it was compiled under DEBUG config. So is that a VC++2005 problem or I missed something while compiling the working copy.

2.2 while compiling the working copy in the RELEASE config, a linking error occured since "libc.lib" was not found for project OpenSees. Does PEER codes provide "libc.lib"?

Any suggestions are apprieciated.

Thanks.
Stan
Graduate Student
Texas A&M University
College Station, TX

fmk
Site Admin
Posts: 5883
Joined: Fri Jun 11, 2004 2:33 pm
Location: UC Berkeley
Contact:

Post by fmk » Mon Feb 05, 2007 1:44 pm

I don't know what your problem is with the cvs version .. i have just installed it on a fresh machine and built it with no problems .. i suggest you start again .. here are the steps:

1. cd into the directory you are going to install OpenSees in.

2. issue the command
cvs -d :pserver:anonymous@opensess.berkeley.edu:/usr/local/cvs login

password is anonymous

3. issue the command
cvs -d :pserver:anonymous@opensess.berkeley.edu:/usr/local/cvs co OpenSees

4. cd to the OpenSees/Win32 directory and open the opensees project (i have vc2005 and used the 2002 project)

5. click on OpenSees project and select build. both the release and debug version compile and link just fine.

GunAndRose
Posts: 44
Joined: Wed Oct 26, 2005 2:23 pm
Location: San Francisco, CA

Post by GunAndRose » Mon Feb 05, 2007 2:25 pm

According to your idea, I did it again. The first problem was solved. But the second one still exist since the linker could not find the "libc.lib". What is it?

BTW: what version of CVS are you using now?


fmk wrote:I don't know what your problem is with the cvs version .. i have just installed it on a fresh machine and built it with no problems .. i suggest you start again .. here are the steps:

1. cd into the directory you are going to install OpenSees in.

2. issue the command
cvs -d :pserver:anonymous@opensess.berkeley.edu:/usr/local/cvs login

password is anonymous

3. issue the command
cvs -d :pserver:anonymous@opensess.berkeley.edu:/usr/local/cvs co OpenSees

4. cd to the OpenSees/Win32 directory and open the opensees project (i have vc2005 and used the 2002 project)

5. click on OpenSees project and select build. both the release and debug version compile and link just fine.
Stan
Graduate Student
Texas A&M University
College Station, TX

Post Reply