Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
Looks good. Usually we don't store the .dsw, but that should be fine... Here is a snippet of my cvsignore list *.sln *.suo *.dsw *.clw *.ncb *.aps *.vcproj* *.plg *.opt *.scc *.tlb *_h.h *_i.h *_i.c *_p.c *~back* *~bak* dlldata.c Note that the .sln, .suo, and .vcproj are because we want to ignore visual studio .NET projects for the time being. They are the equivalent of .dsw and .dsp files. As far as linking, go into the project settings dialog (try Alt+F7) and click on the Link tab, select the "General" category, and there is an "Object/Library Modules" edit control. Note that this setting is per configuration (Debug/Release/etc). keith d. zimmerman, mcsd eagle solutions -----Original Message----- From: Ricardo Fukasawa [mailto:fukasawa at globo.com] Sent: Thursday, February 27, 2003 6:22 PM To: CVSNT Subject: Re: [cvsnt] OT: Which VS6 files to store in CVS? Well, I am not an experienced Visual C++6 user, but I have been using CVS to store my Visual C++6 programs and I only keep there the .c, .cpp, .h, .dsw and .dsp files. All the rest (.ncb, .opt, .plg, .ilk, .pch, .sbr, .pdb, .idb, etc.) I keep out of CVS and Visual C rebuilds them without a problem. I just don't know if this is specific for my applications and in the future I may be in trouble, or if that is the way it works. My best guess is you won't need them. Hope this helped. Ricardo. ----- Original Message ----- From: "Bo Berglund" <bo.berglund at telia.com> Newsgroups: support.cvsnt To: <cvsnt at cvsnt.org> Sent: Thursday, February 27, 2003 7:58 PM Subject: [cvsnt] OT: Which VS6 files to store in CVS? > I know this is really Off Topic, but I guess that there are a whole > bunch of C++ programmers here familiar with MS VS6 so... > > I am normally programming in Delphi or sometimes VB, never C or C++... > Now I have inherited 4 DLL projects that are done using MS C 1.5 (16 > bit) and I have used MS C++ 4 to port the projects to 32 bit. In the > process I have encountered some difficulties (see below) but now they > are at least compatible with VS6 and I must put them into our CVSNT > server. But I don't know which files should go there in the sense that > I don't know which files are rebuilt by VS6 from the other files. > Can someone familiar with VS6 please advice which files apart from the > *.C and *.H sourcefiles and the *.MAK file should be version > controlled? > > And while I am asking: > The projects are linked into two pairs because two DLL:s use the other > 2 DLL:s as low level drivers so they use the exported functions. I am > wondering how to properly declare the import into the "master" DLL > source of the exported functions from the support DLL:s. Specifically > I would like to know where the support DLL file name is given. I have > not found any good spot to enter this info yet in the VS6 IDE and the > project does not link (unresolved external reference) until I > explicitly add the *.lib file of the support DLL to the > *source* file list of the main DLL. > In Delphi it works differently, there the definition of the external > call also specifies the name of the library file (= the dll file). > > Any help greatly appreciated! > > I hope I don't have to do some modification to the functionality of > these DLL:s. (In that case I might as well port them to Delphi....). > > > > /Bo > (Bo Berglund, developer in Sweden) > _______________________________________________ > cvsnt mailing list > cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt cvsnt downloads at march-hare.com https://www.march-hare.com/cvspro/en.asp#downcvs @CVSNT on Twitter CVSNT on Facebook _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt cvsnt downloads at march-hare.com https://www.march-hare.com/cvspro/en.asp#downcvs @CVSNT on Twitter CVSNT on Facebook