Add workflow to test examples are compilable

[d-alonso]

And fix those codes that trip the new workflow

Example of a failing run: https://github.com/codee-com/open-catalog/actions/runs/12238572380/job/34136975245

[jgonzac]

Smart 👍🏼

[alvrogd]

Looking good! This will be super-helpful :)

[alvrogd]

Just noticed that the output of the script you shared seems to be a little convoluted. For instance, the first failure occurs when compiling PWD003/example-omp.f90, and the corresponding compiler errors are shown after the first status line of the next file (Trying ... PWD004 ...).

Could we solve this by only keeping the last status line for each file?; i.e., the ones with the Good or Bad note.

[d-alonso]

Just noticed that the output of the script you shared seems to be a little convoluted. For instance, the first failure occurs when compiling PWD003/example-omp.f90, and the corresponding compiler errors are shown after the first status line of the next file (Trying ... PWD004 ...).

Could we solve this by only keeping the last status line for each file?; i.e., the ones with the Good or Bad note.

This was easier than expected, I just used the CHECK_{START,PASS,FAIL} that CMake already provides. I think it's good to keep the two lines in case the try_compile call has a CMake error itself, you'll see which file was going to be compiled right above it (I know because it happened to me).

[alvrogd]

This was easier than expected, I just used the CHECK_{START,PASS,FAIL} that CMake already provides. I think it's good to keep the two lines in case the try_compile call has a CMake error itself, you'll see which file was going to be compiled right above it (I know because it happened to me).

That's great! This approach looks good to me.