Actually, I just did some checking with laforge. He's told me something a little different.
Apparently, he would prefer that we do explicitly pin the guids with msvs_guid. They still have some scripts which disable targets by guid. When he's firefighting on the release branch it is useful for him to be able to know the guid of a target without having to check out a client. So sadly, you'll probably make his life easier if you do generate a guid wth VS > Tools > Create GUID and use that. This is not an ideal state of affairs. I'll file an issue to see if we can't fix the relevant scripts to use gyp features instead of manipulating raw sln files. -BradN On Nov 24, 1:26 pm, Marc-Antoine Ruel <mar...@chromium.org> wrote: > AFAIK, you don't need one, it was mainly for the transition period. > > Brad, can we remove them all? > > > > On Tue, Nov 24, 2009 at 3:27 PM, Chris Bentzel <cbent...@google.com> wrote: > > Inhttp://codereview.chromium.org/428004, I introduced a new GYP target - > > but don't have an msvs_guid for it. > > > I'm guessing that I can just use a value from VS > Tools > Create GUID, but > > wanted to confirm this since I didn't see any documentation on generating > > the guids. > > > Chris > > > -- > > Chromium Developers mailing list: chromium-dev@googlegroups.com > > View archives, change email options, or unsubscribe: > >http://groups.google.com/group/chromium-dev -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
