Install LFortran at the CI

[certik]

The easiest would be to just install LFortran using conda on all platforms.

But I don't know if we can live with the "lag" that we fix some bug / add a new feature and we have to make a release, update conda (so at least several hours iteration). But if we can, the advantage would be that we test the actual conda package that it just works, so we don't have to test it separately, and the CI would test it just like users would install it.

[certik]

@Pranavchiku currently one must install LFortran with the WITH_LSP=ON cmake flag. Is there any reason not to make this flag on by default (and enable at conda)? Is is slowing something down for regular compilation?

[Pranavchiku]

@Pranavchiku currently one must install LFortran with the WITH_LSP=ON cmake flag

I don't see any drop in performance. We can do that but it needs refactoring at the following lines. I'll do that.

    if (show_asr || compiler_options.lookup_name) {
#ifdef HAVE_LFORTRAN_RAPIDJSON
        std::cout<<"arg_file: "<<arg_file<<std::endl;
        return get_definitions(arg_file, compiler_options);
#else
        return emit_asr(arg_file, lfortran_pass_manager,
                compiler_options);
#endif
    }

[Pranavchiku]

Enabled by default at lfortran/lfortran#5438

[certik]

Here is how we can create a conda package of the latest lfortran: lfortran/lfortran#5451.

[dylon]

This was added as part of #16, but I will leave the issue open until we can replace the cloned repository with a conda dependency.