Mercurial > pidgin.yaz
view PROGRAMMING_NOTES @ 6432:f9428d38c03b
[gaim-migrate @ 6940]
(16:11:45) Paco-Paco: lets more than one loader plugin be used at the same time
(16:12:22) ChipX86: uh oh
(16:12:26) ChipX86: how did that bug occur? :/
(16:13:00) Paco-Paco: I'm not sure but I fought it for a WHILE
(16:13:35) Paco-Paco: it took me forever to track it down
(16:13:38) Paco-Paco: I kept overlooking it
(16:15:08) Paco-Paco: why do they bother telling me to expect some disruption?
(16:20:04) Paco-Paco: we're totally going to have Tcl by 0.68
(16:20:24) ChipX86: nice
committer: Tailor Script <tailor@pidgin.im>
author | Luke Schierer <lschiere@pidgin.im> |
---|---|
date | Mon, 11 Aug 2003 20:23:56 +0000 |
parents | 10b5ac17fdd6 |
children | da88e2cd5c53 |
line wrap: on
line source
Notes on keeping GAIM OS independant ------------------------------------ General ------- - Use G_DIR_SEPARATOR_S and G_DIR_SEPARATOR for paths - Use g_getenv, g_snprintf, g_vsnprintf - Use gaim_home_dir instead of g_get_home_dir or g_getenv("HOME") - Make sure when including win32dep.h that it is the last header to be included. - Open binary files when reading or writing with 'b' mode. e.g: fopen("somefile", "wb"); Not doing so will open files in windows using defaut translation mode. i.e. newline -> <CR><LF> Paths ----- - DATADIR, LOCALEDIR & LIBDIR are defined in wingaim as functions. Doing the following will therefore break the windows build: printf("File in DATADIR is: %s\n", DATADIR G_DIR_SEPARATOR_S "pic.png"); it should be: printf("File in DATADIR is: %s%s%s\n", DATADIR, G_DIR_SEPARATOR_S, "pic.png"); - When writing out paths to .gaimrc, use wgaim_escape_dirsep. This is necessary because the Windows dir separator '\' is being used to escape characters, when paths are read in from the .gaimrc file. PLUGINS & PROTOS ---------------- - G_MODULE_EXPORT all functions which are to be accessed from outside the scope of its "dll" or "so". (E.G. gaim_plugin_init) - G_MODULE_IMPORT all global variables which are located outside your dynamic library. (E.G. connections) (Not doing this will cause "Memory Access Violations" in Win32)