Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29262 Discussions

Compaq Fortran and Visual SourceSafe

aparker
Beginner
749 Views
For some of my workspaces, Compaq Fortran rewrites SourceSafe's ss.ini file to explicitly define the working folder for a given project. The problem is that the workspace (and source code) exist in subprojects under the main.

Example: I compile a workspace in project $SourceA from path c:TestingSourceA. The software puts a record in ss.ini as:
[$/Source/A]
Dir (APARKER-PC005) = c: estingsourcea

Mind you this is all fine and good, should I continue to work in the c: esting tree. But when I go to "Get Latest Version" from the root project ("$") on down to the path "c:Project" or my RW-CD at "f:Project", all the stuff from project $SourceA still gets written to the c: esting tree.

For this and for the time issue (the VSS database is on the network and takes forever to update some of our larger workspaces) I'd really like to disable the communication between Fortran and VSS.
0 Kudos
2 Replies
Steven_L_Intel1
Employee
749 Views
This is all handled by Microsoft code in Developer Studio - there's no Fortran-specific code that knows anything about source control.

I haven't used the source control features in Developer Studio, but know they're there. You may want to compare project or workspace settings between your projects to see what the differences are.

Steve
0 Kudos
Jugoslav_Dujic
Valued Contributor II
749 Views
Not 100% sure what the problem is... just few hints:

VSS keeps track of local working folder setting for each user for each individual project. If it is a subproject, it inherits parent's working folder setting by default, but it can be overriden. In VSS.exe, for $SourceA, specify "set working folder" and delete the C:TestingSourceA entry if you want it to end up on C:ProjectSourceA (i.e. inherit parent's setting).

It's usually not a good idea to have two working folders for the same VSS user. If you have to, define more user names for yourself and take care to log on under the right one.

Jugoslav
0 Kudos
Reply