I suppose that would work, but I think allowing "configuration intersection" where a module declares a dependence on the intersection of 2 or more configurations of another module is a cleaner approach. Your wildcard approach would require lots of configurations for all permutations of all axis to be declared which might clutter up the ivy.xml file.
--- Shawn Castrianni -----Original Message----- From: Niklas Matthies [mailto:[email protected]] Sent: Wednesday, April 15, 2009 4:44 AM To: [email protected] Subject: Re: configuration help On Tue 2009-04-14 at 17:35h, Shawn Castrianni wrote on ivy-user: > I need something like: win32 client artifacts, linux64 > server artifacts, etc. I essentially need to specify the > intersection of two configuration names and have the artifacts that > only exist in both configurations get resolved. > > Is this possible? I would think this might be a popular enhancement > for those using ivy for native code modules. Maybe a different approach would be to support configuration names with wildcards, like "win32-*" and "*-server". More generally, if there were four axis A-D, one could declare an artifact to be valid for "A-*-C-*", i.e. for any B and D, for example. -- Niklas Matthies ---------------------------------------------------------------------- This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.
