This Pull Request makes few structural changes in stdlib to make get it compiled using the compiler wrapper script here.

To solve the issues, the following should be done:

• In CMakeLists.txt: add "-I${PROJECT_SOURCE_DIR}/include" in the definition of the fyppFlags
• In test/CMakeLists.txt: remove the lines:

list(
  APPEND fyppFlags
  "-I${PROJECT_SOURCE_DIR}/src"
)

Did you also solve the issues with:

• test_mean_f03.fypp
• nmash.c
  ?

Did you also solve the issues with:

* `test_mean_f03.fypp`

* `nmash.c`
  ?

For nmhash.c, I have fixed the issues. Will push it.
For test_mean_f03.fypp, Still having the same issue. I have not been able to resolve it. Still working on it.

@awvwgk @jvdp1

CMake build is failing since, it is not able to find test_always_fail.f90 & test_always_skip.f90 as I have deleted those files.

CMake build is failing since, it is not able to find test_always_fail.f90 & test_always_skip.f90 as I have deleted those files.

Than you also have to remove the declaration of the tests from the CMake build files.

I remember we moved the common.fypp file from src to include directory. But seems like fpm-deployment script was not updated to handle that.

@awvwgk @jvdp1

I remember we moved the common.fypp file from src to include directory. But seems like fpm-deployment script was not updated to handle that.

@awvwgk @jvdp1

Should I change the include path of common.fypp in the .fypp files from which common.fypp not found error is coming in the fpm-deployment ?

cc: @awvwgk @jvdp1

Should I change the include path of common.fypp in the .fypp files from which common.fypp not found error is coming in the fpm-deployment ?

No, I don't think so. Instead the variable fyflags in the fpm-deployement should be updated with the flag -I (similar to for the CMake files)
E.g., in my directory, I must adapt the fpm-deployment as follows:

...
fyflags="${fyglags} -I include"
...

[jvdp1]

Should it be

Suggested change

	[preprocess.cpp]
	[preprocess.fypp]

?
As far as I remember, CPP is not used within stdlib.

[arteevraina]

Yes, that is not used. But, we have not enabled fypp inside fpm as of now. So, it cannot identity it as a valid preprocessor. Considering fypp-gfortran.py as a temporary solution, I think when we have fypp integrated inside fpm then I think we should rename it as fypp instead of cpp.

To solve the issue with the Build-API-Docs, the directory include should be added/mentioned in the file API-doc-FORD-file.md (probably under the directive include:).

Hi @jvdp1, I still seem to face some issues with docs ci. Can you help me in resolving this?

This should be related to the version update of FORD, see #673 .

This should be related to the version update of FORD, see #673 .

@arteevraina Indeed it seems to be related to #673

@arteevraina Could you rebase your PR such that @zoziha chnages (#681) are also integrated into this PR, please?
Hopefully this will solve the issue with the CI.

[awvwgk]

Should we support extracting those values automatically in fpm?

[arteevraina]

Yes, I think we should add support to extract them for the version number ?
I will take up this task.

[arteevraina]

PR created for this fortran-lang/fpm#766

[jvdp1]

Why is that provided? IMO a link to fpm should be sufficient.