Mercurial > pidgin
view PROGRAMMING_NOTES @ 16369:f64566c2eefc
propagate from branch 'im.pidgin.pidgin' (head 401f15786be56deb06ae79bf29c341bab26203d7)
to branch 'im.pidgin.rlaager.gaim_migration' (head 98f4d6d08b4df8efff0eae9d4805df3572b95415)
author | Richard Laager <rlaager@wiktel.com> |
---|---|
date | Mon, 23 Apr 2007 17:08:09 +0000 |
parents | e8f8d19bf3ee |
children |
line wrap: on
line source
Notes on keeping Pidgin, Finch, and libpurple OS independant ------------------------------------------------------------ General ------- - Use G_DIR_SEPARATOR_S and G_DIR_SEPARATOR for paths - Use g_getenv, g_snprintf, g_vsnprintf - Use purple_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 default translation mode. i.e. newline -> <CR><LF> Paths ----- - DATADIR, LOCALEDIR & LIBDIR are defined as functions in the win32 build 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"); PLUGINS & PROTOS ---------------- - G_MODULE_EXPORT all functions which are to be accessed from outside the scope of its "dll" or "so". (E.G. purple_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)