[p4] p4DTI in Perl ?

Nick Barnes Nick.Barnes at pobox.com
Fri Jun 23 15:49:04 PDT 2006


At 2006-06-23 13:23:40+0000, "Weintraub, David" writes:

> There's a lot of issues with P4DTI. One of them is that it doesn't even
> work with the latest version of Python. You must use Python 2.0. Plus,
> most of the code is compiled Python code, so it's hard to modify. I bet
> no one has the original source to the compiled Python too.

I don't know where you get your information.

- The P4DTI is built and tested with Python 2.4.x.

- Almost all of the P4DTI code is provided as Python source.  The sole
  exception is a compiled C++ module on Windows which is required by
  the PyWin32 module for connecting to the Windows event log.  The
  tiny source file for this module is attached to this message.  The
  source and build files for this module form part of the P4DTI
  Integration Kit, and are available from:
  <http://www.ravenbrook.com/project/p4dti/master/code/eventlog/>

- Before TeamShare Inc agreed to take over development and maintenance
  of the TeamTrack P4DTI integration, and that integration was
  therefore removed from the main P4DTI distribution, there was also a
  C++ module which was required to connct to the TeamTrack C++ API.
  The sources for that module similarly formed part of the P4DTI
  Integration Kit and were available for download.  This should be
  unsurprising, since:

- The P4DTI is an open project.  All the sources, design documents,
  test and development materials are available under an open-source
  license from <http://www.ravenbrook.com/project/p4dti/>, and have
  been continuously since the beginning of the project in May 2000.

- Any problems with the TeamTrack P4DTI integration should be raised
  with Serena, Inc; it has been nothing to do with us since June 2003.

Here is the eventlog.cpp source code.

Nick Barnes
P4DTI Project
Ravenbrook Limited

// eventlog.cpp : Defines the entry point for the DLL application.
//

#include <windows.h>

BOOL APIENTRY DllMain( HANDLE hModule, 
                       DWORD  ul_reason_for_call, 
                       LPVOID lpReserved
                                                 )
{
    return TRUE;
}


More information about the perforce-user mailing list