Mathijs Kwik <[email protected]> wrote:
>You can go a step further and define multiple sub-profiles. >For example 1 you typically use during c development. >And another for haskell development, and yet another for an >experimental python3 environment. >Then you can jump between those environments on a per-terminal basis >(no interferance, do many different things at once). Like this, you >keep the default packageset (and thus "commands" available in your >shell path) to a minimum. Look for "myEnvFun" in nixpkgs if you want >to try this. Yes this is exactly where I want to go. I need a C++ and Mozart/oz environment, now does one have this default.nix committed to the mozart/oz project's repo? Should one use nix-shell to change to this environment? So portablility is ensured by committing the new environment to some folder branch in nixpkgs, or just ship default.nix? I compile the mozart2 compiler (which is dependent on boost) as soon as I try execute the development environment it blowsup because it can't see boost deps. So I obviously need a hybrid C++/mozart-oz solution. My dependencies are Boost, Tcl, Tk, xlibs, xproto, Java, clang, llvm, gtest, gcc, I also have a load of environmental variables. I noticed there is a build.sh which allows me to abstract away Mozart's build. Kind regards Stewart _______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
