Author Topic: Importing MSVC++ Workspaces and Subsequent Loads...  (Read 2961 times)

GMG

  • Guest
Importing MSVC++ Workspaces and Subsequent Loads...
« on: March 30, 2007, 01:22:09 am »
Okay, so the workspaces load perfectly. However, I have a project and a workspace and I can open either, but they both appear to be identical once loaded. So, my question is this: Should I load the Code::Blocks-generated workspace or the Code::Blocks project? Does it matter? Advantages/Disadvantages?

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: Importing MSVC++ Workspaces and Subsequent Loads...
« Reply #1 on: March 30, 2007, 07:31:51 am »
If your workspace contains a single project only it basically the same. But technically it's a completely different thing: A workspace can consist of 1..n projects. A project can consist of 1..n targets. Within a project you define compilation, the sources itself and stuff. Within a workspace you define e.g. dependencies between projects.
So there are numerous ways how to organise your projects/targets. You have to use a workspace at least if you have more than one project... although you could also open them all manually after each other. But in that case they would be part of the "default workspace" which is always present.
I hope this clarifies things - otherwise have a look in the WiKi, for example here:
http://wiki.codeblocks.org/index.php?title=The_build_process_of_Code::Blocks
With regards, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

GMG

  • Guest
Re: Importing MSVC++ Workspaces and Subsequent Loads...
« Reply #2 on: March 30, 2007, 08:19:38 am »
'preciate it! Up until now everything I'd written was in Visual Studio 6/.NET and I was pretty much taught to open the workspace.

Anyway, thanks, 'MacFly. Swell name, btw...