G'day, A couple of comments about including/excluding libraries, that superficially look good, but may require more effort to realise:
1. The Good: IUP's top-level Makefile has an "EXCLUDE_TARGETS=..." feature, so that subtargets can be switched in/out from the command line. There's relatively little nesting of functionality; all subtargets are fairly self-contained, as, in some cases, they compile to independent programs. Therefore, the EXCLUDE_TARGETS approach works well. 2. The Bad: CD and IM, by contrast, are more heavily nested in the way the code is arranged in the project tree. There is usually only one build subdirectory -- "src/", and you run make from there. So, neither IM or CD has implemented an EXCLUDE_TARGETS facility, despite it being very easy to change the top-level Makefile code in the way that this was done for IUP. 3. zlib -- Half-in, half out. "zlib" is an example of this -- there is a copy of a snapshot of the library at some point, but the build system tries to use an external runtime library (.so/.dll) in preference to the code in the tree. Within the tree, zlib is not a top-level target; it is (forgive my fading memory) a couple of levels deeper below the toplevel. The zlib code has not been removed from the tree, despite being slightly out-of-date. I suspect some existing or proposed platforms exist where an external runtime zlib library binary is not supported. Other reasons may include removal being a low-priority, higher-risk activity that is rated as low-value, relative to competing work (e.g. IUP). cheers, sur-behoffski (Brenton Hoff) programmer, Grouse Software _______________________________________________ Iup-users mailing list Iup-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/iup-users
