Add psutil build step to fix pyauto media issues. Upgrade psutil to 0.4.0.

third_party/psutil/psutil.gyp

Index: third_party/psutil/psutil.gyp
diff --git a/third_party/psutil/psutil.gyp b/third_party/psutil/psutil.gyp
new file mode 100644
index 0000000000000000000000000000000000000000..55813fbc9e2b713d6fbef9c30bbffb91f99dda7b
--- /dev/null
+++ b/third_party/psutil/psutil.gyp
@@ -0,0 +1,91 @@
+# Copyright (c) 2011 The Chromium Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+{
+  'targets': [
+    {
+      'target_name': 'psutil_lib',
+      'type': 'none',
+      'actions': [
+        {
+          'action_name': 'psutil_build',
+          'inputs': [
+            'setup.py',
+            'psutil/_common.py',
+            'psutil/_compat.py',
+            'psutil/error.py',
+            'psutil/__init__.py',
+            'psutil/_psutil_common.c',
+            'psutil/_psutil_common.h',
+          ],
+          'outputs': [
+            '<(PRODUCT_DIR)/psutil',
+            '<(PRODUCT_DIR)/psutil/_compat.py',
+            '<(PRODUCT_DIR)/psutil/_psosx.py',
+            '<(PRODUCT_DIR)/psutil/__init__.py',
+            '<(PRODUCT_DIR)/psutil/_pslinux.py',
+            '<(PRODUCT_DIR)/psutil/_common.py',
+            '<(PRODUCT_DIR)/psutil/error.py',
+            '<(PRODUCT_DIR)/psutil/_psmswindows.py',
+            '<(PRODUCT_DIR)/psutil/_psbsd.py',
+            '<(PRODUCT_DIR)/psutil/_psposix.py',
+          ],
+          'conditions': [
+            ['OS=="linux"', {
+              'inputs': [
+                'psutil/_pslinux.py',
+                'psutil/_psposix.py',
+                'psutil/_psutil_linux.c',
+                'psutil/_psutil_linux.h',
+                'psutil/_psutil_posix.c',
+                'psutil/_psutil_posix.h',
+              ],
+              'outputs': [
+                '<(PRODUCT_DIR)/_psutil_linux.so',
+                '<(PRODUCT_DIR)/_psutil_posix.so',
+              ],
+            }],
+            ['OS=="mac"', {
+              'inputs': [
+                'psutil/_psosx.py',
+                'psutil/_psposix.py',
+                'psutil/_psutil_osx.c',
+                'psutil/_psutil_osx.h',
+                'psutil/_psutil_posix.c',
+                'psutil/_psutil_posix.h',
+                'psutil/arch/osx/process_info.c',
+                'psutil/arch/osx/process_info.h',
+              ],
+              'outputs': [
+                '<(PRODUCT_DIR)/_psutil_osx.so',
+                '<(PRODUCT_DIR)/_psutil_posix.so',
+              ],
+            }],
+            ['OS=="win"', {
+              'inputs': [
+                'psutil/_psmswindows.py',
+                'psutil/_psutil_mswindows.c',
+                'psutil/_psutil_mswindows.h',
+                'psutil/arch/mswindows/ntextapi.h',
+                'psutil/arch/mswindows/process_handles.c',
+                'psutil/arch/mswindows/process_handles.h',
+                'psutil/arch/mswindows/process_info.c',
+                'psutil/arch/mswindows/process_info.h',
+                'psutil/arch/mswindows/security.c',
+                'psutil/arch/mswindows/security.h',
+              ],
+              'outputs': [
+                '<(PRODUCT_DIR)/_psutil_mswindows.pyd',
+              ],
+            }],
+          ],
+          'action': ['python',
+                     'build.py',

[Nico, 2011/12/12 18:20:12]

Shelling out to a script to do a compilation is…unusual. Have you considered
doing a real gyp file, so that the build can be done by a build system instead
of by a python script?

[DaleCurtis, 2011/12/12 19:23:20]

Hi Nico, I'm not sure what you mean by a real gyp file. Can you elaborate? Do
you mean converting the setup.py that's packaged with psutil into a gyp file? If
so, I'd rather not go that way since it's subject to upstream changes.

On 2011/12/12 18:20:12, Nico wrote:

[Nico, 2011/12/12 23:20:43]

Yes.
It's what we do for all third-party libraries we pull. Usually, upstream doesn't
change that often, and keeping source lists in sync isn't that big of a deal.

Having a normal gyp file means that stuff like goma, custom compilers, new build
systems, etc all have a chance of being supported.

I don't know if it's possible to do python packages that way though. Ideally,
the media tests would not depend on psutil – do you know what they use it for?

[DaleCurtis, 2011/12/12 23:34:57]

I didn't realize you guys were already doing that, if that's the case I can look
into it. At least for the Linux build (which is all we need right now) it looks
pretty easy.

The tests are using psutil to record process utilization metrics while videos
are playing. We could remove it from the tree and just require users install the
package prior to use.

That would mean the chromiumos.perf_av build slave would need these packages
installed manually.

On 2011/12/12 23:20:43, Nico wrote:

[Nico, 2011/12/12 23:42:11]

It sounds like those are all chrome processes – could you use chrome's task
manager code for that instead?
If this is just for linux, you could add the package to
build/install-build-deps.sh, which is executed on new slaves. (I think
chromiumos uses it, too.) chrome-infra-team can install packages on existing
bots.

That sounds a tad cleaner to me (this! is! not! gentoo! :-) ), but maybe you
should ask chromium-dev what the right thing to do is here. (If the chrome task
manager code can do what you want, that's probably the way to go.)

+                     '<(PRODUCT_DIR)'
+          ],
+          'message': 'Generating psutil binaries.',
+        },
+      ],
+    },
+  ],
+}