Re: Brand new to VS!
- From: "Andrew McDonald" <myrmecophagavir@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 17 May 2007 19:59:20 +0100
"Brian McGrew" <brian@xxxxxxxxxxxxx> wrote...
I'm brand new to Visual Studio using VS 2005 Team Edition. I've grown up
in a Unix world and have been doing C++ with a text editor on various
flavors of Unix since I was 13. The whole concept of using an IDE and the
whole way that Visual Studio lays out is so foreign to me...
But yet I have a huge software project that I need to port to Windows.
Now in my Unix world, this includes what compiles out to around 100
libraries and half as many binaries with four main "application" programs.
In the Unix world, in my source tree I have a libs directory where the
sources for each shared library live in their own seperate directory and
I've got a host directory where the sources for each binary live in their
own directory space... Every single directory has a Makefile and from the
top level or any sub directory I can just issue a make command and
everything in the currect directory and all sub directorys is build or
rebuilt... Even though I don't really have the conecpt of a "Project" in
Unix, the entire software build of the world is burried beneath this one
project directory and it's all inclusive in the one project if you will.
That whole concept seems lost in Visual Studio or maybe I'm just missing
something. Obviously getting my above question answer would be good but a
secondary question would be: can someone point me to a Visual Studio C++
project that I can look at for references? I'm looking for a huge project
that includes multiple binaries, libraries, help and resource files;
something that I can use for a guidline or template for creating my new
project in Windows.
I'm not sure of a specific example, but try checking any of the large
open-source projects on e.g. SourceForge. Some of them come with VC project
files.
In general, your codebase sounds like it should map pretty well into VC.
Think of a "project" (stored in a .vcproj file) as a makefile for an
individual lib or executable, and then you have one "solution" (.sln file)
at the root which contains all the projects in one workspace. If you have it
set up correctly, you can just hit "build solution" in the IDE and all the
individual projects will be built in dependency order.
I'd find it a bit of a pain managing 100 project files, but then I suppose
it's not different from managing 100 makefiles. There may already be some
utility out there to automatically convert a makefile setup to a VC
solution, otherwise you could create each project manually and add the
required source files to it. VC can also load makefiles in some way, though
I've never actually used it. I expect your current ones are full of GCC
compiler flags or something, so you might need to make new ones anyway - in
which case I'd just go for VC projects from the off.
--
Andy
.
- References:
- Brand new to VS!
- From: Brian McGrew
- Brand new to VS!
- Prev by Date: Re: struct values and VC++/MFC
- Next by Date: Install VC 6.0 without installing MS Java VM?
- Previous by thread: Brand new to VS!
- Next by thread: Install VC 6.0 without installing MS Java VM?
- Index(es):
Relevant Pages
|
