Fix #8848 - Add new recipe for whereami/20220112

[jmarrec]

• Fix [request] whereami/20220112 #8848
• Specify library name and version: whereami/20220112

cf https://github.com/gpakosz/whereami

I somewhat adapted https://github.com/bincrafters/conan-whereami. Revamped the example to use a C one (following https://github.com/gpakosz/whereami/blob/master/example/executable.c), conformed to conan-hooks, and added a cmake target.

---

• I've read the guidelines for contributing.
• 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.

[jmarrec]

@uilianries I am confused by the "unexpected error". Seems like 3 builds at the end are only reporting profile, not build nor test https://c3i.jfrog.io/c3i/misc/summary.html?json=https://c3i.jfrog.io/c3i/misc/logs/pr/8850/4-configs/windows-visual_studio/whereami/20220112//summary.json

[jgsogo]

@uilianries I am confused by the "unexpected error". Seems like 3 builds at the end are only reporting profile, not build nor test https://c3i.jfrog.io/c3i/misc/summary.html?json=https://c3i.jfrog.io/c3i/misc/logs/pr/8850/4-configs/windows-visual_studio/whereami/20220112//summary.json

@jmarrec, The unexpected error is just the final catch-em-all in a try/catch block, so looks like something happened while building one of those last Windows configurations. The logic to collect the log (successful and failed builds) is inside the try, when we capture this exception we just try to kill things in order, we send a message to our internal slack, and report some message to the user. This is why those logs are not reported.

[SpaceIm]

there is no official CMake config file. Just let conan generate default config file & target, otherwise it's just confusing and unecessary complexity.

[jmarrec]

Cleaned up per review comments and rebased onto master. Tested locally on Ubuntu 20.04 that it still works

[jmarrec]

we usually don't add conan topic these days, but that's not a big deal

I probably misread the intent here. Apparently the hook does want to see topics. I'll put them back, minus the "conan" one

[SSE4]

we usually don't add conan topic these days, but that's not a big deal

I probably misread the intent here. Apparently the hook does want to see topics. I'll put them back, minus the "conan" one

sorry, I wasn't clear enough. I mean topic named conan is not necessary, but other topics are okay. so it should be:

topics = "whereami", "introspection", "getmodulefilename",

[conan-center-bot]

All green in build 8 (49c97d526420a89d8a3929948f2fd15c1562ed9f):

• whereami/20220112@:
  All packages built successfully! (All logs)

[uilianries]

LGTM

[jmarrec]

Thanks for the reviews and help!

[Croydon]

Unless I'm missing something, the versioning is wrong. As there seems to be no upstream versioning, it should have been prefixed with cci.

https://github.com/conan-io/conan-center-index/blob/master/docs/faqs.md#what-version-should-packages-use-for-libraries-without-official-releases

[SpaceIm]

Good catch

[jmarrec]

Didn't know that, thanks for pointing to the documentation @Croydon, I'm making a mental note for the future.