Watch, Follow, &
Connect with Us
Public Report
Report From: C++BuilderX/IDE/Team Development/CVS    [ Add a report in this area ]  
Report #:  7369   Status: Reported
CVS & build/link do not appear to work together
Project:  C++BuilderX/BC++ 2005 Build #:  1786
Version:    1.0 Submitted By:   Jon Berndt
Report Type:  Minor failure / Design problem Date Reported:  2/22/2004 11:25:54 AM
Severity:    Serious / Highly visible problem Last Updated: 2/22/2004 12:03:37 PM
Platform:    All versions Internal Tracking #:  
Resolution: None  Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: No Ratings Yet
0.00 out of 5
Total Votes: None
Description
Observations of a first time user:

1) I tried to check out a project that I currently maintain at sourceforge: www.jsbsim.org. The pull failed until I by chance happened upon a comment on the borland news server that I needed to provide the entire path to my ssh client. After I did that, it worked.

2) Once I checked out a project, I was unable to build it.  When I checked out the source, it resided (according to the Project Content window) under the "JSBSim" folder, which in turn was under the JSBSim.cbx item.  I could compile individual source files, but not the entire project - in fact, the IDE at this point had the Make and Build menu items grayed out for the project. Nothing I could do allowed me to build the project. The documentation was of no help in this matter.

3) If I tried to create a console project that included all my source, I was able to do this, but was unable to get it to work with CVS.

4) If I tried to create a project in my existing CVS checkout structure, I was unable to manipulate my CVS information - particularly the path to my ssh client, as all CVS information is grayed out in the Configure CVS dialog.

So, given all of these headaches, I am left wondering if it is even possible to use CVS to work with my project within C++BuilderX.  This tool has great potential, but perhaps it was released before it was ready?
Steps to Reproduce:
You may not be able to reproduce this exactly, because I am the administrator for the project as well as a developer. You would need developer status to check out the project as I did.  I might be willing to give developer status to one of your engineers temporarily in order to help debug this problem, if necessary.

You could try this:

1) Select New | Pull from CVS

CVS config:

Connect type: PServer
Login:
Server: cvs.sourceforge.net
User: anonymous
Module location:
repository path: /cvsroot/jsbsim
Module name: JSBSim

2) You will end up with an untitiled.cbx root iceon and a JSBSim icon, underneath which is all the sources and auxiliary directories.

3) Make and Build options for the project are grayed out.

This reproduces one aspect of the possible bug as described.
Workarounds
None
Attachment
None
Comments

Mathew Duafala at 2/22/2004 11:54:30 AM -
Please see my comment in the newsgroup.  

Don't create a new project (or you could, but you would have to set up the CVS options again).  Just add the files that were pulled to the project, and set the compiler/linker options.

Jon Berndt at 2/23/2004 6:30:11 AM -
It's still not clear how set up my project file for creating an executable. I don't see how to tell the linker to create an executable from my object files. I can of course create a console project from the File|New menu and that seems to work. But setting up a project that is pulled from CVS, I have reached a roadblock on linking.

Server Response from: ETNACODE01