[Cmake-commits] CMake branch, master, updated. v3.9.0-339-ge4edd35

[Kitware Robot]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The branch, master has been updated
   via  e4edd3503ae59a0bfdeeb91609b8da88300ac975 (commit)
  from  af9708881f4c2d8f501ae63a4088c020edb6f070 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e4edd3503ae59a0bfdeeb91609b8da88300ac975
commit e4edd3503ae59a0bfdeeb91609b8da88300ac975
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Sat Jul 22 00:01:06 2017 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Sat Jul 22 00:01:06 2017 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 33c363b..b818f94 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
 # CMake version number components.
 set(CMake_VERSION_MAJOR 3)
 set(CMake_VERSION_MINOR 9)
-set(CMake_VERSION_PATCH 20170721)
+set(CMake_VERSION_PATCH 20170722)
 #set(CMake_VERSION_RC 1)

---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

Re: [CMake] CPack: Create debian packge for each sub-project

[Domen Vrankar]

2017-07-22 1:55 GMT+02:00 DKLind :

> I have a large project and I need to create a Debian package for each
> sub-project (essentially each add_subdirectory).
>
> I have been experimenting with CPack components as outlined here:
> https://cmake.org/cmake/help/v3.8/module/CPackComponent.
> html?highlight=cpack_components_grouping#variable:
> CPACK_COMPONENTS_GROUPING
>

Debian packaging generator specific variables are described here:
https://cmake.org/cmake/help/v3.8/module/CPackDeb.html


> I haven't been able to get any CPACK_DEBIAN__PACKAGE_XXX
> variables to work. I've been using the syntax
> CPACK_DEBIAN_${PROJECT_NAME}_PACKAGE_XXX.
>

I'm guessing that ${PROJECT_NAME} contains lower case characters -
 (called  in documentation) part of the variable name
is supposed to be in upper case.


> I'm calling install as:
> install(TARGETS ${PROGRAM_NAME} DESTINATION lib COMPONENT ${PROGRAM_NAME})
> This way each sub-project is a unique component.
>

This looks fine.


> I would expect that CPackConfig.cmake would contain an entry for each
> CPACK_DEBIAN__PACKAGE_XXX variable. But, I'm seeing only
> variables for the last sub-project that called "include(CPack)".
>

Only the top level CMakeLists.txt should call 'include(CPack)' and the rest
of the CMakeLists.txt (if they can be used stand alone) should only call it
if they are the base binary dir:

if(CMAKE_CURRENT_BINARY_DIR STREQUAL CMAKE_BINARY_DIR)
include(CPack)
endif()

The reason is that including this script generates CPackConfig.cmake and
CPackSourceConfig.cmake files from already set variables.

Here are my requrements:
> 1. Each package must have a unique control file info (version, description,
> etc).
>

Description part is not a problem but the version part is - currently only
one version for all packages is used and can't be set per component. Using
ExternalProject instead of subdirectories would be one solution, the other
would be extending CPackDeb.cmake module (contribution would be welcome).


> 2. Each package filename must be
> ${PROGRAM_NAME}_${VERSION}_${ARCHITECTURE}.deb
>

For package names I'd suggest using:

set(CPACK_DEBIAN_FILE_NAME "DEB-DEFAULT")

to get the default deb package file name format but if you wish to use your
naming convention you can set the per component version for each package.

Regards,

Domen
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

[CMake] CPack: Create debian packge for each sub-project

[DKLind]

I have a large project and I need to create a Debian package for each
sub-project (essentially each add_subdirectory).

I have been experimenting with CPack components as outlined here:
https://cmake.org/cmake/help/v3.8/module/CPackComponent.html?highlight=cpack_components_grouping#variable:CPACK_COMPONENTS_GROUPING

I haven't been able to get any CPACK_DEBIAN__PACKAGE_XXX
variables to work. I've been using the syntax
CPACK_DEBIAN_${PROJECT_NAME}_PACKAGE_XXX.

I'm calling install as:
install(TARGETS ${PROGRAM_NAME} DESTINATION lib COMPONENT ${PROGRAM_NAME})
This way each sub-project is a unique component.

I would expect that CPackConfig.cmake would contain an entry for each
CPACK_DEBIAN__PACKAGE_XXX variable. But, I'm seeing only
variables for the last sub-project that called "include(CPack)".

Here are my requrements:
1. Each package must have a unique control file info (version, description,
etc).
2. Each package filename must be
${PROGRAM_NAME}_${VERSION}_${ARCHITECTURE}.deb



--
View this message in context: 
http://cmake.3232098.n2.nabble.com/CPack-Create-debian-packge-for-each-sub-project-tp7595889.html
Sent from the CMake mailing list archive at Nabble.com.
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

[cmake-developers] Java language support regression (compared with 3.7.x and 3.8.x) for 3.9.0

[Alan W. Irwin]

I have built CMake-3.9.0 on my Linux (Debian Jessie) platform using
the bootstrap method I have always successfully used for other CMake
versions (including 3.7.2).

For a complex project (PLplot) which uses swig_add_module and
swig_link_libraries to implement our Java binding, I get the following
error message at the end of that CMake-3.9.0 output.

-- Configuring done
CMake Error: Error required internal CMake variable not set, cmake may
not be built correctly.
Missing variable is:
CMAKE_Java_CREATE_SHARED_MODULE
-- Generating done
-- Build files have been written to:
/home/software/plplot/HEAD/build_dir

I don't get this error message for CMake-3.7.2.

Using find and xargs -0 grep I have looked in both 3.7.2 and 3.9.0
source code for any mention of CMAKE_Java_CREATE_SHARED_MODULE, and it
just does not exist.

By the way, I have tried the following simple project.

cmake_minimum_required(VERSION 3.6.2 FATAL_ERROR)
project(test_java NONE)
enable_language(Java)
message(STATUS "CMAKE_Java_CREATE_SHARED_MODULE = 
${CMAKE_Java_CREATE_SHARED_MODULE}")

(I used 3.6.2 for the minimum version because that is what PLplot uses).

That project does confirm that both 3.7.2 and 3.9.0 do not define
CMAKE_Java_CREATE_SHARED_MODULE.  However, both versions failed to
generate the above error so a more complex project such as PLplot
that, e.g., swig-generates a Java binding for a C library is needed to
show the issue.

By the way, inserting the following lines in the PLplot top-level
CMakeLists.txt file

# Temporary workaround for Java language support issue for
# CMake-3.9.0
set(CMAKE_Java_CREATE_SHARED_MODULE "this_command_should_never_be_used")

has no bad consequences for cmake-3.7.2, i.e., I can build our Java
binding and run all our standard Java examples.  However, for the
3.9.0 case, the above change avoids the cmake issue, but there are
many JNI-related build errors for our Java binding (although none
of them mention "this_command_should_never_be_used").

The only cmake-3.8.0 version I have built previously is one of the
release candidates.  But that passed all tests at the time including
building our Java binding and running our Java examples with success
so this appears to be a newly introduced issue for 3.9.0.


From these symptoms, I am pretty sure that language support infrastructure

has been upgraded for 3.9.0, but your Java
language support has not been consistently upgraded at the same time.

If so, the solution is either downgrade your language support
infrastructure to be consistent with CMake-3.8.x or to upgrade your
Java language support to be consistent with your updated language
support for 3.9.0.

Once someone has a patch for this issue I would be happy to test it by
rebuilding a patched version of CMake-3.9.0 and trying out a build of
PLplot with that patched version.

Alan
__
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__

Linux-powered Science
__
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [CMake] CPack Multicore Usage

[Chuck Atkins]

> > In calls to cpack only one core is used if Makefiles are used. Is there
> any option to enable multicore?
>

It depends on what your trying to achieve.  Typically the bottleneck for
CPack is in the compression step of the resulting tar (or rpm, etc.).  In
that case, CMake is limited by the libarchive, libz, libbz2, liblzma, etc.
implementations it's linked to, which are typically single threaded.  It's
really no different than taking an install tree and running "tar -czf
foo.tgz /path/t/foo-prefix".  So in that sense, even if you can
parallelizes the "temporary" install step where it collects the files to
packages, actually generating and compressing the package, which is the
costly part, will likely remain a single process.
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

[CMake] POSITION_INDEPENDENT_CODE's [un]expected behaviour

[Oleksii Vilchanskyi via CMake]

Hello,

I would like to ask about POSITION_INDEPENDENT_CODE target property. As
of CMake 3.8.2 POSITION_INDEPENDENT_CODE appends -fPIE or -fPIC to
CMAKE__FLAGS and CMAKE_EXE_LINKER_FLAGS when building an
executable or a library respectively. However, to build a PIE -pie
linker flag is additionally required. Thus POSITION_INDEPENDENT_CODE is
not behaving as expected being a really easy to fix for someone aware
with CMake codebase.

Is there any reason why it wasn't added when the property was
introduced? Somebody proposed introducing
POSITION_INDEPENDENT_EXECUTABLE later on in addition to
POSITION_INDEPENDENT_CODE to maintain backwards compatibility (I suppose
policies are also a solution?).

This email is the result of the thread
 and the message

by Juan Navarro (big thanks to him), which fully summarizes CMake's
POSITION_INDEPENDENT_CODE treatment and links to multiple bugs: this one
, so far without attention, and
this one , resolved
for Android.

Thank you.

Regards,
Oleksii Vilchanskyi

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

[Cmake-commits] CMake branch, master, updated. v3.9.0-338-gaf97088

[Kitware Robot]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The branch, master has been updated
   via  af9708881f4c2d8f501ae63a4088c020edb6f070 (commit)
   via  81005ff16b9fe0177e6d5bea29d087ec1a658716 (commit)
   via  b7e8b0e2604f36294f34228b912d94f321ec381d (commit)
   via  b7941641430feeefadc6f16e2cecf6b50bd9fbe3 (commit)
   via  351c1b1ad6d68c9c029ae9d92f656b467cd350d0 (commit)
   via  f5ccef17515ed4794659923706989fa059b4df38 (commit)
  from  5e3b29f03af342f301c301abddf7a9af868ce211 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=af9708881f4c2d8f501ae63a4088c020edb6f070
commit af9708881f4c2d8f501ae63a4088c020edb6f070
Merge: 81005ff f5ccef1
Author: Brad King 
AuthorDate: Fri Jul 21 14:17:04 2017 +
Commit: Kitware Robot 
CommitDate: Fri Jul 21 10:17:09 2017 -0400

Merge topic 'autogen-include-tests'

f5ccef17 Autogen: Extended mocInclude tests

Acked-by: Kitware Robot 
Merge-request: !1070


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=81005ff16b9fe0177e6d5bea29d087ec1a658716
commit 81005ff16b9fe0177e6d5bea29d087ec1a658716
Merge: b7e8b0e b794164
Author: Brad King 
AuthorDate: Fri Jul 21 14:16:22 2017 +
Commit: Kitware Robot 
CommitDate: Fri Jul 21 10:16:26 2017 -0400

Merge topic 'string-clear-intermediate-matches'

b7941641 cmStringCommand: clear intermediate matches

Acked-by: Kitware Robot 
Merge-request: !1065


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b7e8b0e2604f36294f34228b912d94f321ec381d
commit b7e8b0e2604f36294f34228b912d94f321ec381d
Merge: 5e3b29f 351c1b1
Author: Brad King 
AuthorDate: Fri Jul 21 14:15:05 2017 +
Commit: Kitware Robot 
CommitDate: Fri Jul 21 10:15:09 2017 -0400

Merge topic 'cpack-dmg-applescript-argv'

351c1b1a CPack: Pass volume mount name to AppleScript instead of volume 
name.

Acked-by: Kitware Robot 
Merge-request: !1069


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b7941641430feeefadc6f16e2cecf6b50bd9fbe3
commit b7941641430feeefadc6f16e2cecf6b50bd9fbe3
Author: Ben Boeckel 
AuthorDate: Tue Jul 18 11:08:10 2017 -0400
Commit: Ben Boeckel 
CommitDate: Fri Jul 21 09:09:56 2017 -0400

cmStringCommand: clear intermediate matches

When `string(REGEX REPLACE)` or `string(REGEX MATCHALL)` loop
internally, they store their matches, but they do not clear the previous
match from an earlier iteration. This can leave the contents of
`CMAKE_MATCH_` with bogus values for later matches in the string if
they have groups which earlier matched a non-empty string, but now match
an empty string.

Fixes #17079.

diff --git a/Source/cmStringCommand.cxx b/Source/cmStringCommand.cxx
index 7a097ba..5a6cf48 100644
--- a/Source/cmStringCommand.cxx
+++ b/Source/cmStringCommand.cxx
@@ -309,6 +309,7 @@ bool 
cmStringCommand::RegexMatchAll(std::vector const& args)
   std::string output;
   const char* p = input.c_str();
   while (re.find(p)) {
+this->Makefile->ClearMatches();
 this->Makefile->StoreMatches(re);
 std::string::size_type l = re.start();
 std::string::size_type r = re.end();
@@ -391,6 +392,7 @@ bool cmStringCommand::RegexReplace(std::vector 
const& args)
   std::string output;
   std::string::size_type base = 0;
   while (re.find(input.c_str() + base)) {
+this->Makefile->ClearMatches();
 this->Makefile->StoreMatches(re);
 std::string::size_type l2 = re.start();
 std::string::size_type r = re.end();
diff --git a/Tests/RunCMake/string/RegexMultiMatchClear-stderr.txt 
b/Tests/RunCMake/string/RegexMultiMatchClear-stderr.txt
new file mode 100644
index 000..4360d79
--- /dev/null
+++ b/Tests/RunCMake/string/RegexMultiMatchClear-stderr.txt
@@ -0,0 +1,12 @@
+^matches: Some::;Scope
+results from: string\(REGEX MATCHALL\)
+CMAKE_MATCH_0: -->Scope<--
+CMAKE_MATCH_1: -->Scope<--
+CMAKE_MATCH_2: --><--
+CMAKE_MATCH_COUNT: -->1<--
+replace: \[Some\]\[Scope\]
+results from: string\(REGEX REPLACE\)
+CMAKE_MATCH_0: -->Scope<--
+CMAKE_MATCH_1: -->Scope<--
+CMAKE_MATCH_2: --><--
+CMAKE_MATCH_COUNT: -->1<--$
diff --git a/Tests/RunCMake/string/RegexMultiMatchClear.cmake 
b/Tests/RunCMake/string/RegexMultiMatchClear.cmake
new file mode 100644
index 000..80b6b3c
--- /dev/null
+++ b/Tests/RunCMake/string/RegexMultiMatchClear.cmake
@@ -0,0 +1,20 @@
+cmake_minimum_required (VERSION 3.0)

[Cmake-commits] CMake branch, master, updated. v3.9.0-332-g5e3b29f

[Kitware Robot]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The branch, master has been updated
   via  5e3b29f03af342f301c301abddf7a9af868ce211 (commit)
   via  7b70023e9323166c252cae1c7335a03b858343b4 (commit)
   via  43383fa9226a07e3bc592fa0d1351f400c99e435 (commit)
   via  29a5cf7c42f2c229ec09ab2fb5666751b3b7e15d (commit)
   via  614921b4c916038fcb7bc8c899a7d1d8b772b143 (commit)
   via  8842a0272b541c0e641c8132070828c3d579d1ea (commit)
  from  6f08ce1a4f6b91a9911dde282f49f53f133c0593 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5e3b29f03af342f301c301abddf7a9af868ce211
commit 5e3b29f03af342f301c301abddf7a9af868ce211
Merge: 7b70023 29a5cf7
Author: Brad King 
AuthorDate: Fri Jul 21 14:14:13 2017 +
Commit: Kitware Robot 
CommitDate: Fri Jul 21 10:14:19 2017 -0400

Merge topic 'cpack-stgz-help'

29a5cf7c CPack: Add missing options to installer shell script help

Acked-by: Kitware Robot 
Merge-request: !1068


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7b70023e9323166c252cae1c7335a03b858343b4
commit 7b70023e9323166c252cae1c7335a03b858343b4
Merge: 43383fa 614921b
Author: Brad King 
AuthorDate: Fri Jul 21 14:13:29 2017 +
Commit: Kitware Robot 
CommitDate: Fri Jul 21 10:13:36 2017 -0400

Merge topic 'add_test_processors_prop_to_cdash'

614921b4 Add the test property PROCESSORS to the CDash xml as a 
NamedMeasurement.

Acked-by: Kitware Robot 
Merge-request: !1066


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=43383fa9226a07e3bc592fa0d1351f400c99e435
commit 43383fa9226a07e3bc592fa0d1351f400c99e435
Merge: 6f08ce1 8842a02
Author: Brad King 
AuthorDate: Fri Jul 21 14:12:24 2017 +
Commit: Kitware Robot 
CommitDate: Fri Jul 21 10:12:33 2017 -0400

Merge topic 'docsExternalProject'

8842a027 ExternalProject: Improve documentation

Acked-by: Kitware Robot 
Merge-request: !1037


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=29a5cf7c42f2c229ec09ab2fb5666751b3b7e15d
commit 29a5cf7c42f2c229ec09ab2fb5666751b3b7e15d
Author: Francois Budin 
AuthorDate: Wed Jul 19 14:13:23 2017 -0400
Commit: Brad King 
CommitDate: Thu Jul 20 11:06:39 2017 -0400

CPack: Add missing options to installer shell script help

`--version` and `--skip-license` were not in the list of
available options when running script with `--help` option.

diff --git a/Modules/CPack.STGZ_Header.sh.in b/Modules/CPack.STGZ_Header.sh.in
index c615851..70f63d2 100755
--- a/Modules/CPack.STGZ_Header.sh.in
+++ b/Modules/CPack.STGZ_Header.sh.in
@@ -7,9 +7,11 @@ cpack_usage()
 Usage: $0 [options]
 Options: [defaults in brackets after descriptions]
   --helpprint this message
+  --version print cmake installer version
   --prefix=dir  directory in which to install
   --include-subdir  include the @CPACK_PACKAGE_FILE_NAME@ subdirectory
   --exclude-subdir  exclude the @CPACK_PACKAGE_FILE_NAME@ subdirectory
+  --skip-licenseaccept license
 EOF
   exit 1
 }

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=614921b4c916038fcb7bc8c899a7d1d8b772b143
commit 614921b4c916038fcb7bc8c899a7d1d8b772b143
Author: Bill Hoffman 
AuthorDate: Tue Jul 18 12:18:11 2017 -0400
Commit: Bill Hoffman 
CommitDate: Tue Jul 18 12:18:11 2017 -0400

Add the test property PROCESSORS to the CDash xml as a NamedMeasurement.

This commit forwards the test property PROCESSORS to CDash in the xml
produced by ctest. This is to allow CDash to know how much processor
time was allocated to a test.

diff --git a/Source/CTest/cmCTestTestHandler.cxx 
b/Source/CTest/cmCTestTestHandler.cxx
index 8797204..ef0fac8 100644
--- a/Source/CTest/cmCTestTestHandler.cxx
+++ b/Source/CTest/cmCTestTestHandler.cxx
@@ -1441,6 +1441,12 @@ void cmCTestTestHandler::GenerateDartOutput(cmXMLWriter& 
xml)
 }
 
 xml.StartElement("NamedMeasurement");
+xml.Attribute("type", "numeric/double");
+xml.Attribute("name", "Processors");
+xml.Element("Value", result->Properties->Processors);
+xml.EndElement(); // NamedMeasurement
+
+xml.StartElement("NamedMeasurement");
 xml.Attribute("type", "text/string");
 xml.Attribute("name", "Completion Status");
 xml.Element("Value", result->CompletionStatus);