summaryrefslogtreecommitdiff
path: root/bindings/bcppmake/sword.c
diff options
context:
space:
mode:
Diffstat (limited to 'bindings/bcppmake/sword.c')
-rw-r--r--bindings/bcppmake/sword.c31
1 files changed, 31 insertions, 0 deletions
diff --git a/bindings/bcppmake/sword.c b/bindings/bcppmake/sword.c
new file mode 100644
index 0000000..4c1c100
--- /dev/null
+++ b/bindings/bcppmake/sword.c
@@ -0,0 +1,31 @@
+//---------------------------------------------------------------------------
+
+#include <windows.h>
+//---------------------------------------------------------------------------
+// Important note about DLL memory management when your DLL uses the
+// static version of the RunTime Library:
+//
+// If your DLL exports any functions that pass String objects (or structs/
+// classes containing nested Strings) as parameter or function results,
+// you will need to add the library MEMMGR.LIB to both the DLL project and
+// any other projects that use the DLL. You will also need to use MEMMGR.LIB
+// if any other projects which use the DLL will be performing new or delete
+// operations on any non-TObject-derived classes which are exported from the
+// DLL. Adding MEMMGR.LIB to your project will change the DLL and its calling
+// EXE's to use the BORLNDMM.DLL as their memory manager. In these cases,
+// the file BORLNDMM.DLL should be deployed along with your DLL.
+//
+// To avoid using BORLNDMM.DLL, pass string information using "char *" or
+// ShortString parameters.
+//
+// If your DLL uses the dynamic version of the RTL, you do not need to
+// explicitly add MEMMGR.LIB as this will be done implicitly for you
+//---------------------------------------------------------------------------
+
+#pragma argsused
+int WINAPI DllEntryPoint(HINSTANCE hinst, unsigned long reason, void* lpReserved)
+{
+ return 1;
+}
+//---------------------------------------------------------------------------
+ \ No newline at end of file