Add recipe for vtu11/1.2.0

[jellespijker]

Vtu11 is a small C++ header-only library to write
unstructured grids using the vtu file format. It
keeps the mess of dealing with file writing in
different formats away from you. Currently it does not add any features for setting up the required
data structure because this vastly differs based on the context in which vtu11 is used.

See https://github.com/phmkopp/vtu11

Fixes phmkopp/vtu11#46
Fixes #14802

Specify library name and version: lib/1.0

• I've read the contributing guidelines.
• I've followed the PEP8 style guides for Python code in the recipes.
• I've used the latest Conan client version.
• I've tried at least one configuration locally with the conan-center hook activated.

[jellespijker]

@uilianries all checks have passed how to remove the failed label and mark it ready for review?

[uilianries]

@uilianries all checks have passed how to remove the failed label and mark it ready for review?

Actually it's a bad UX already mapped to be fixed (internal GH issue). There are 2 pipelines, Conan V1 and V2. The V1 is mandatory, but V2 is only informative. However, if any of them fail, GH will mark that Fail label. So if your PR passed by V1, it's good enough and that label is only realrdd to V2, which is informative only and does not block your PR.

BTW, Have a Happy New Year 🍾

[jellespijker]

@uilianries You also the best wishes and thanks for explaining

[uilianries]

Sorry my delay, big time on vacations. Only a small consideration related to the c++ exported flag, but in summarize it looks pretty decent!

[jellespijker]

don't worry @uilianries , the benefits of having access to a JFrog Artifactory Enterprise server is that I can cont. without delay from third parties, and I know how busy you guys are. I do hope you had a great, well-deserved holiday, btw.

Anyhow, this is for my personal weekend project Ultimaker/CuraEngine#1806 although my WIP PR is already being used to debug some complex issues.

I will update this PR sometime this weekend.

[prince-chrismc]

Bunch of comments... these are fun ones which change downstream based on cppstd

If you need help finishing this let me know :)

[conan-center-bot]

Conan v1 pipeline ✔️

All green in build 14 (35f05557a6efd8425312c4a36fa4c8020444079f):

• vtu11/1.2@:
  All packages built successfully! (All logs)

---

Conan v2 pipeline (informative, not required for merge) ❌

Note: Conan v2 builds are informative and they are not required for the PR to be merged.

The v2 pipeline failed. Please, review the errors and note this will be required for pull requests to be merged in the near future.

See details:

Failure in build 15 (35f05557a6efd8425312c4a36fa4c8020444079f):

• vtu11/1.2@:
  CI failed to create some packages (All logs)

  Logs for packageID da39a3ee5e6b4b0d3255bfef95601890afd80709:

  [settings]
  arch=x86_64
  build_type=Release
  compiler=msvc
  compiler.cppstd=14
  compiler.runtime=static
  compiler.runtime_type=Release
  compiler.version=192
  os=Windows
  

  [...]
  -- Using Conan toolchain: C:/J/w/prod-v2/BuildSingleReference/cci-18d23eda/recipes/vtu11/all/test_package/build/msvc-192-x86_64-14-release/generators/conan_toolchain.cmake
  -- Conan toolchain: C++ Standard 14 with extensions OFF
  -- The CXX compiler identification is MSVC 19.29.30148.0
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe - skipped
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- Conan: Target declared 'vtu11::vtu11'
  -- Conan: Target declared 'ZLIB::ZLIB'
  -- Configuring done
  -- Generating done
  -- Build files have been written to: C:/J/w/prod-v2/BuildSingleReference/cci-18d23eda/recipes/vtu11/all/test_package/build/msvc-192-x86_64-14-release
  
  vtu11/1.2 (test package): Running CMake.build()
  vtu11/1.2 (test package): RUN: cmake --build "C:\J\w\prod-v2\BuildSingleReference\cci-18d23eda\recipes\vtu11\all\test_package\build\msvc-192-x86_64-14-release" --config Release
  Microsoft (R) Build Engine version 16.11.2+f32259642 for .NET Framework
  Copyright (C) Microsoft Corporation. All rights reserved.
  
    Checking Build System
    Building Custom Rule C:/J/w/prod-v2/BuildSingleReference/cci-18d23eda/recipes/vtu11/all/test_package/CMakeLists.txt
    test_package.cpp
    The contents of <filesystem> are available only with C++17 or later.
  C:\J\w\prod-v2\BuildSingleReference\p\vtu11d67043759be5c\p\include\vtu11/inc/alias.hpp(45,30): error C2039: 'filesystem': is not a member of 'std' [C:\J\w\prod-v2\BuildSingleReference\cci-18d23eda\recipes\vtu11\all\test_package\build\msvc-192-x86_64-14-release\test_package.vcxproj]
  C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\include\vector(24): message : see declaration of 'std' [C:\J\w\prod-v2\BuildSingleReference\cci-18d23eda\recipes\vtu11\all\test_package\build\msvc-192-x86_64-14-release\test_package.vcxproj]
  C:\J\w\prod-v2\BuildSingleReference\p\vtu11d67043759be5c\p\include\vtu11/inc/alias.hpp(45,40): error C2878: 'filesystem': a namespace or class of this name does not exist [C:\J\w\prod-v2\BuildSingleReference\cci-18d23eda\recipes\vtu11\all\test_package\build\msvc-192-x86_64-14-release\test_package.vcxproj]
  C:\J\w\prod-v2\BuildSingleReference\p\vtu11d67043759be5c\p\include\vtu11/impl/vtu11_impl.hpp(266,22): error C2653: 'vtu11fs': is not a class or namespace name [C:\J\w\prod-v2\BuildSingleReference\cci-18d23eda\recipes\vtu11\all\test_package\build\msvc-192-x86_64-14-release\test_package.vcxproj]
  C:\J\w\prod-v2\BuildSingleReference\p\vtu11d67043759be5c\p\include\vtu11/impl/vtu11_impl.hpp(266,36): error C3321: an initializer list is unexpected in this context [C:\J\w\prod-v2\BuildSingleReference\cci-18d23eda\recipes\vtu11\all\test_package\build\msvc-192-x86_64-14-release\test_package.vcxproj]
  C:\J\w\prod-v2\BuildSingleReference\p\vtu11d67043759be5c\p\include\vtu11/impl/vtu11_impl.hpp(266,31): error C2064: term does not evaluate to a function taking 1 arguments [C:\J\w\prod-v2\BuildSingleReference\cci-18d23eda\recipes\vtu11\all\test_package\build\msvc-192-x86_64-14-release\test_package.vcxproj]
  C:\J\w\prod-v2\BuildSingleReference\p\vtu11d67043759be5c\p\include\vtu11/impl/vtu11_impl.hpp(267,21): error C2653: 'vtu11fs': is not a class or namespace name [C:\J\w\prod-v2\BuildSingleReference\cci-18d23eda\recipes\vtu11\all\test_package\build\msvc-192-x86_64-14-release\test_package.vcxproj]
  C:\J\w\prod-v2\BuildSingleReference\p\vtu11d67043759be5c\p\include\vtu11/impl/vtu11_impl.hpp(267,35): error C3321: an initializer list is unexpected in this context [C:\J\w\prod-v2\BuildSingleReference\cci-18d23eda\recipes\vtu11\all\test_package\build\msvc-192-x86_64-14-release\test_package.vcxproj]
  C:\J\w\prod-v2\BuildSingleReference\p\vtu11d67043759be5c\p\include\vtu11/impl/vtu11_impl.hpp(267,30): error C2064: term does not evaluate to a function taking 1 arguments [C:\J\w\prod-v2\BuildSingleReference\cci-18d23eda\recipes\vtu11\all\test_package\build\msvc-192-x86_64-14-release\test_package.vcxproj]
  C:\J\w\prod-v2\BuildSingleReference\p\vtu11d67043759be5c\p\include\vtu11/impl/vtu11_impl.hpp(270,10): error C2653: 'vtu11fs': is not a class or namespace name [C:\J\w\prod-v2\BuildSingleReference\cci-18d23eda\recipes\vtu11\all\test_package\build\msvc-192-x86_64-14-release\test_package.vcxproj]
  C:\J\w\prod-v2\BuildSingleReference\p\vtu11d67043759be5c\p\include\vtu11/impl/vtu11_impl.hpp(270,7): error C3536: 'directory': cannot be used before it is initialized [C:\J\w\prod-v2\BuildSingleReference\cci-18d23eda\recipes\vtu11\all\test_package\build\msvc-192-x86_64-14-release\test_package.vcxproj]
  C:\J\w\prod-v2\BuildSingleReference\p\vtu11d67043759be5c\p\include\vtu11/impl/vtu11_impl.hpp(270,19): error C3861: 'exists': identifier not found [C:\J\w\prod-v2\BuildSingleReference\cci-18d23eda\recipes\vtu11\all\test_package\build\msvc-192-x86_64-14-release\test_package.vcxproj]
  C:\J\w\prod-v2\BuildSingleReference\p\vtu11d67043759be5c\p\include\vtu11/impl/vtu11_impl.hpp(272,9): error C2653: 'vtu11fs': is not a class or namespace name [C:\J\w\prod-v2\BuildSingleReference\cci-18d23eda\recipes\vtu11\all\test_package\build\msvc-192-x86_64-14-release\test_package.vcxproj]
  C:\J\w\prod-v2\BuildSingleReference\p\vtu11d67043759be5c\p\include\vtu11/impl/vtu11_impl.hpp(272,18): error C3861: 'create_directories': identifier not found [C:\J\w\prod-v2\BuildSingleReference\cci-18d23eda\recipes\vtu11\all\test_package\build\msvc-192-x86_64-14-release\test_package.vcxproj]
  C:\J\w\prod-v2\BuildSingleReference\p\vtu11d67043759be5c\p\include\vtu11/impl/vtu11_impl.hpp(277,35): error C3536: 'pvtufile': cannot be used before it is initialized [C:\J\w\prod-v2\BuildSingleReference\cci-18d23eda\recipes\vtu11\all\test_package\build\msvc-192-x86_64-14-release\test_package.vcxproj]
  C:\J\w\prod-v2\BuildSingleReference\p\vtu11d67043759be5c\p\include\vtu11/impl/vtu11_impl.hpp(277,13): error C2672: 'vtu11::detail::writeVTUFile': no matching overloaded function found [C:\J\w\prod-v2\BuildSingleReference\cci-18d23eda\recipes\vtu11\all\test_package\build\msvc-192-x86_64-14-release\test_package.vcxproj]
  
  *********************************************************
  Recipe 'vtu11/1.2 (test package)' cannot build its binary
  It is possible that this recipe is not Conan 2.0 ready
  If the recipe comes from ConanCenter check: https://conan.io/cci-v2.html
  If it is your recipe, check if it is updated to 2.0
  *********************************************************
  
  ERROR: vtu11/1.2 (test package): Error in build() method, line 25
  	cmake.build()
  	ConanException: Error 1 while executing
  

---

^{Note: To save resources, CI tries to finish as soon as an error is found. For this reason you might find that not all the references have been launched or not all the configurations for a given reference. Also, take into account that we cannot guarantee the order of execution as it depends on CI workload and workers availability.}

[SpaceIm]

this logic is wrong, specially when package id is cleared...

[jellespijker]

Yes, you're correct, good catch. I'm a bit uncertain what the best way is to resolve this. What is your opinion? Should I solve this with a "custom" clear functionality in the package id, clearing everything except settings, compiler version?

[SpaceIm]

I would say that the patch should be robust to any C++ standard in the first place.