none
WinCE OS Build and Software Configuration VSS (Visual Source Safe ) - How to? RRS feed

  • Question

  • Hello Group,

    Now that I have a custom OS started and built along with the BSP, subprojects and other stuff necessary to support the project, what is the best way to control the source and project files using VSS? What source has to be controlled? What have others done?

    TIA,

    Monte---

    Monday, May 16, 2011 7:06 PM

Answers

  • Well, first of all, I wouldn't use VSS, but that's just an opinion...
     
    I use SVN but GIT or Mercurial or ... will work just as well.
     
    So, what goes under source control (valid for both CE6 and WEC7):
     
    PLATFORM\YourBSP:
     
    Everything *except*:
     
    [folders] CESYSGEN\files\, target, lib, all 'obj' folder
    [files] *.bif, build.*
     
    Same goes for any (later installed) SOC folders you use (so in
    PLATFORM\common\src\SOC)
     
    OS Design (CE6):
     
    Everything *except*:
     
    [folders] [OSDesign]\[OSDesign]\RelDir,
    [OSDesign]\[OSDesign]\Wince600\[BSP_CPU]\cesysgen,
    [OSDesign]\[OSDesign]\Wince600\[BSP_CPU]\sdk,
    [OSDesign]\[OSDesign]\Wince600\[BSP_CPU]\OAK\target, all 'obj' folders
    [files] build*.*, *.ncb, *.suo, *.pbxml.user,
    [OSDesign]\[OSDesign]\Wince600\[BSP_CPU]\[all files in this folder],
    [OSDesign]\[OSDesign]\Wince600\[BSP_CPU]\OAK\[all files in this folder]
     
    Just to clarify; you NEED TO INCLUDE:
    [OSDesign]\[OSDesign]\Wince600\[BSP_CPU]\OAK\files and
    [OSDesign]\[OSDesign]\Wince600\[BSP_CPU]\OAK\MISC
     
     
    In WINCE700 the OS Design structure is cleaned up more and it is easier:
     
    Everything *except*:
     
    [folders] [OSDesign]\[OSDesign]\RelDir, [OSDesign]\[OSDesign]\Wince700,
    all 'obj' folders
    [files] build*.*, *.ncb, *.suo, *.pbxml.user
     
     
    Then, what I do is when I create a qualified build (meaning I build
    straight out of source control without any local modifications on my
    build server) I tag the branch and add the generated kernel binaries and
    generated SDK to the branch under source control.
     
    IMHO there is no need to add QFE's if you have access to ECE (if you
    don't know what ECE is you may want to add the QFE's you installed at
    the time of the build to source control just as you add the generated
    kernel and SDK binaries after you've tagged the branch so that you can
    always go back and build exactly the same kernel in the future).
     
    Apart from that I use a system of hardlinking a WINCE root into any
    folder and then set the WINCEROOT to that folder. I created some tools
    to do that, but to explain why this works so fast and great is outside
    of the scope of this email. I will, at some point, write a blog post
    about this and make the tool available...
     
     
    Good luck,
     
    Michel Verhagen, eMVP
    Check out my blog: http://GuruCE.com/blog
     
    GuruCE
    Microsoft Embedded Partner
    http://GuruCE.com
    Consultancy, training and development services.
     
    On 16-5-2011 21:06, RumJungle wrote:
    > Hello Group,
    >
    > Now that I have a custom OS started and built along with the BSP,
    > subprojects and other stuff necessary to support the project, what is
    > the best way to control the source and project files using VSS? What
    > source has to be controlled? What have others done?
    >
    > TIA,
    >
    > Monte---
    >
     

    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: http://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.
    • Proposed as answer by Michael Koster Tuesday, May 17, 2011 8:06 AM
    • Marked as answer by RumJungle Tuesday, May 17, 2011 3:05 PM
    Tuesday, May 17, 2011 7:33 AM
    Moderator