Closed smanders closed 5 years ago
solution:
if xpGetArgValue()
had another single value argument NEXT
so that the next label/argument can be differentiated then this would improve multi-value arguments to give the correct result
this isn't pretty... not very good that the order of what's in the PRO_*
has to be known and if the order changes the calls to xpGetArgValue()
may need to be updated... (that's more fragile than I wish it was)
xpGetArgValue(${PRO_ACTIVEMQCPP} ARG BUILD_DEPS VALUES BUILD_DEPS NEXT VER)
NEXT
tells xpGetArgValue()
that VER
is right after BUILD_DEPS
, so it will know that apr openssl_1.0.2a
are the multi-value args for BUILD_DEPS
and VER
is the start of the next field
completed with commit to dev branch referenced above
a previous issue (enhance xpGetArgValue https://github.com/smanders/externpro/issues/93) made it possible to retrieve "multi value" arguments -- see commit https://github.com/smanders/externpro/commit/0b10df72a0cac738a79325a5e7629c87402d49ed
however, there are issues with the multi value argument support added
for example, I was trying to get the
BUILD_DEPS
fromPRO_ACTIVEMQCPP
with the call
and the
BUILD_DEPS
returned would include everything inPRO_ACTIVEMQCPP
afterBUILD_DEPS
there's currently no way for
xpGetArgValue()
to know what the next argument is to know what is part of the multi-value argument and what is the next thing