#8724: Jamming components that rely upon OptionalBuildFeatures ----------------------------+---------------------------- Reporter: mmadia | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: Component: Build System | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 0 | Platform: All ----------------------------+---------------------------- Comment (by bonefish): I wonder if it's worth the effort. If you build WebPositive often (e.g. because you work on it) it is not a big deal to enable the optional build feature in your UserBuildConfig. To implement the feature is probably not that complicated. To implement it in an elegant way might be, though. A simple solution would be to check in build/jam/CommandLineArguments what targets are built and, if WebPositive is among them, enable the optional build feature. Given that the plan is to eventually outsource a lot more third party software, including libraries, this method will probably need a declaration file similar to OptionalPackageDependencies. The method isn't elegant for at least two reasons: One, the declaration of the dependency is separate from the place where the dependency is used, i.e. it can easily get out of sync. Two, this only works, if the target is listed on the command line like that. Pseudo targets (e.g. "webpositive- with-add-ons") won't work, unless listed as well. I guess the second issue cannot really be solved without modifying jam itself. The first one is at least a bit tricky. -- Ticket URL: <http://dev.haiku-os.org/ticket/8724#comment:1> Haiku <http://dev.haiku-os.org> Haiku - the operating system.