On May 30, 2007, at 7:59 AM, Reed Hedges wrote: > Eric Sunshine wrote: >> The 'install' targets always build the other targets upon which they >> depend. There is no functionality for installing only those targets >> already built. There are some high-level installation targets >> (install_bin, install_plugin, install_lib, install_include, >> install_data, install_config, install_doc) which you can invoke >> individually, but, as noted, they will build their dependencies >> automatically before installation. > OK, those are useful, except that the plugins are the main thing. > Do you > think it would be hard to add a rule that installs a single plugin?
It would require a bit of work with some attention to detail to do it properly. Theoretically it is a simple matter of defining another non- file target for each application, library, and plugin target. However, the actual implementations are spread through app.jam, lib.jam, plugin.jam, macosx.jam, unix.jam, and win32.jam, and there may be some special cases which one needs to take into account, such as potential external meta-information associated with plugins (such special cases warrant the "attention to detail" caveat). > (Did the old Makefiles have rules for that or am I thinking of another > project?) You are probably thinking of some other project. One may argue, however, that there is some precedent for the addition of individualized application, library, and plugin installation targets by considering that we already create "clean" targets for each application, library, and plugin. -- ES ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Crystal-main mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/crystal-main Unsubscribe: mailto:[EMAIL PROTECTED]
