Collabora Notes: Difference between revisions

Jump to navigation Jump to search
m
Line 213: Line 213:
There are as many ways of configuring MSVC projects as there are developers hacking on mozilla, but to get all the benefits from MSVC, you'll generally want to do the following steps :
There are as many ways of configuring MSVC projects as there are developers hacking on mozilla, but to get all the benefits from MSVC, you'll generally want to do the following steps :


* Create one project per module and create convenient folders/filters for it.
* Create one project per module and create convenient folders/filters for it. (For example, create one project called "widget", another "xpcom", "content", etc.... If you put all the mozilla files into one huge sigle MSVC folder, it'll be a mess!)
  (For example, create one project called "widget", another "xpcom", "content", etc...)


* For each project's
* For each project, choose the "Makefile" configuration type from its "properties" menu.


* For each projects, add appropriate include folder to make Intellisense kick in properly. (don't forget <objdir>/browser/dist/include/... folders !)
* For each projects, add appropriate include folders to make Intellisense kick in properly. (don't forget <objdir>/browser/dist/include/... folders !)




I've created... (to be cont'ed)
I've created some example [http://people.collabora.co.uk/~fred23/collabora_notes/MSVC_projects.zip MSVC project files]. It's easier to start with them and, of course, rename/replace all the absolute and relative directories found in it prior to load them with MSVC.


=== Getting a command prompt for pulling and building ===
=== Getting a command prompt for pulling and building ===

Navigation menu