On Wed, May 20, 2020 at 2:12 PM 'Steven Johnson' via emscripten-discuss < [email protected]> wrote:
> Halide uses the EM_CONFIG variable in its build script. > > The reason for this is that we need to ensure that LLVM_ROOT points to the > specific version of LLVM being used by the rest of Halide. (Having these > out of sync can cause amusingly bad things to happen.) We slurp in the > default ~/.emscripten config file and make an altered version (with > LLVM_ROOT pointing to the LLVM we are using), so that we can always build > with the 'correct' version (ie the one that the rest of Halide is using). > > Requiring that ~/.emscripten be edited is problematic as Halide supports > multiple versions of LLVM at any one time (currently, v9, v10, and > v11/trunk), so this file would need to edited in lockstep with other things > in Halide to keep things in step. > Thanks for the heads up steven! We had another report of someone using it, so I reverted the warning for now. I'm hoping we can move both of you in different direction over time. For example, did you know that you can set the LLVM_ROOT using the `EM_LLVM_ROOT` environment variable? This seems more targeted and easier for you. Any variable that you can set from the config file can also be set via the environment in the form of `EM_<NAME>`. cheers, sam > > > > > On Tue, May 19, 2020 at 11:46 AM 'Sam Clegg' via emscripten-discuss < > [email protected]> wrote: > >> emscripten has a feature where you can avoid using a config file >> completely and instead pass a python literal in the EM_CONFIG >> environment variable or `--em-config` command line. >> >> e.g. `emcc --em-config="<python code>` >> >> As part of routine cleanup I'm hoping to be able to remove this >> feature and allow the code to depend on the existence of a config >> file on disk. >> >> I'm not imagining there are any users of this feature, and we can >> make it into warning a few releases to confirm this. >> >> Does anyone know of any users of this feature? >> >> cheers, >> sam >> >> -- >> You received this message because you are subscribed to the Google Groups >> "emscripten-discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/emscripten-discuss/CAL_va28seE50BNe4BKJ4cFzoQNNZPE6xbFFwDvXQSdWfiF2WAA%40mail.gmail.com >> <https://groups.google.com/d/msgid/emscripten-discuss/CAL_va28seE50BNe4BKJ4cFzoQNNZPE6xbFFwDvXQSdWfiF2WAA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/emscripten-discuss/CAM%3DdnveGTKtEqGWue_qyUMjdyLdGXZbXEm8m4fhPjreRgd4tGQ%40mail.gmail.com > <https://groups.google.com/d/msgid/emscripten-discuss/CAM%3DdnveGTKtEqGWue_qyUMjdyLdGXZbXEm8m4fhPjreRgd4tGQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/CAL_va29xtsd5emac0nfmvUys84xaBdx-xMes515U1sATFPJe1w%40mail.gmail.com.
