1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67
|
General information:
- the workspace RDCode.dsw should contain all projects
- the magic for copying files in the post-build step is something
like this:
copy Release\cAlgorithms.pyd $(RDBASE)\Python\ML\Cluster
i.e. you *can* reference environment variables
Things to remember whilst writing extension modules:
- don't forget to update the include and link paths and turn off
precompiled headers (unless you are really using them)
- don't forget to initialize Numeric
- interaction with Numeric data is most easily done using this paradigm:
accum += ((double *)origMetricsContig->data)[(p2*(p2-1))/2+p1];
((double *)newMetricMat->data)[tempIdx] = accum;
- when programming the windows, it's useful to use the XXX_API methods that
microsoft's wizard provides for DLLs. These do, however, need to
have extern "C" added to them, so you get something like this in
your .h file:
#ifdef WIN32
#ifdef CALGORITHMS_EXPORTS
#define CALGORITHMS_API extern "C" __declspec(dllexport)
#else
#define CALGORITHMS_API extern "C" __declspec(dllimport)
#endif
#include <windows.h>
#else // WIN32
#define CALGORITHMS_API extern "C"
#endif
you'll also need to include the magic DLLMain foo in your .cpp
file:
#ifdef WIN32
BOOL APIENTRY DllMain( HANDLE hModule,
DWORD ul_reason_for_call,
LPVOID lpReserved
)
{
switch (ul_reason_for_call)
{
case DLL_PROCESS_ATTACH:
case DLL_THREAD_ATTACH:
case DLL_THREAD_DETACH:
case DLL_PROCESS_DETACH:
break;
}
return TRUE;
}
#endif
|