If your XML is machine-generated and consistent, a line-by-line regular expression might still get you the results faster. But if your preconditions stretch across multiple lines, I'd stay with XML::LibXML.
From my cursory reading of your XML and your source code, it seems that you are interested in the IntDir and OutDir nodes, as "only these can contain the ReleaseDLL directory" (famous last words here). I'd then make the XPath expression more explicit:
# For the IntDir nodes
# For the OutDir nodes
If you are hell-bent on producing and using one single XPath expression, you can combine the two using the self:: axis. I prefer to avoid such stuff and just keep a list of XPath expressions to run instead:
//PropertyGroup[contains(\@Condition,'$proj')]/*[self::IntDir or self:
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||