You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently compiled binaries are placed in build/debug/ and build/release.
Would it be possible to make this build path dependent on compiler (and maybe architecture)?
e.g.build/gfortran-9.2.0-x86_64_debug/
This reason for this being that I like to build and test my projects on multiple compilers during development; separating the binary output paths allows incremental builds using multiple compilers and allows tests on each compiler to run simultaneously and without clean and rebuild.
This may be considered an 'ugly' directory structure, however since fpm handles all compiler/linker paths and offers the fpm run command, this has no effect on end-user experience.
The workflow for using a non-default compiler could then be along the lines of:
$> export FC=ifort
$> fpm run
or
$> FC=ifort fpm run
or
$> fpm run --compiler=ifort
The text was updated successfully, but these errors were encountered:
Currently compiled binaries are placed in
build/debug/
andbuild/release
.Would it be possible to make this build path dependent on compiler (and maybe architecture)?
e.g.
build/gfortran-9.2.0-x86_64_debug/
This reason for this being that I like to build and test my projects on multiple compilers during development; separating the binary output paths allows incremental builds using multiple compilers and allows tests on each compiler to run simultaneously and without clean and rebuild.
This may be considered an 'ugly' directory structure, however since fpm handles all compiler/linker paths and offers the
fpm run
command, this has no effect on end-user experience.The workflow for using a non-default compiler could then be along the lines of:
or
or
The text was updated successfully, but these errors were encountered: