On Sat, Jul 31, 2010 at 5:38 PM, Alec Berryman <[email protected]> wrote: > - Both time-server and ftp-server have a MAIN: that starts the server, > but no provision to keep it running; a deployed time-server just > starts and exits. I used a while loop with sleep to keep the server > running; is that best way to do it? The examples should be updated.
time-server calls [ start-server ] in-thread when it could just do start-server. I've changed it to do that. > - The deployed application didn't use the GUI, but the executable was > linked to graphics libraries. Not all of them were present on the > server. I ended up rebuilding Factor with NO_UI and using one build > for local development and one for deployment; it would be nice if the > build system made both executables and chose at deploy time. Yes, good idea. I'll change the Makefile to do that, and then the deploy tool can pick one of the two binaries, based on whether or not the application being deployed uses the UI. > - There are still some machines around the office running very old > versions of Fedora without inotify support. Building the vm on these > machines fails because in os_linux.cpp, when SYS_inotify_init is > undefined, the code calls a variable "parent" which does not exist. I > just commented out those lines and had no further difficulties; I > didn't need any features dependent on inotify. I poked around a bit > but didn't see an easy way to get at the vm object in use to fix the > issue. The correct fix is to call current_vm() here. I've fixed the problem. Slava ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
