In reply to @dnrix:matrix.org
Hey all, I recently got annoyed by the lack of caching in incremental Go builds in Nix and decided to just fix it to work the way I thought it should (opt-in similar to ccache). I came up with this:
https://github.com/dnr/nix-gocacheprog
Let me know how it works for you!

I think it's really two projects rolled up into one, with different goals:

• One is the cache prog bits which you can use with or without the builder infra

  I'm very much intending for this to be something that you can use in development shells to load cache either from an impure location, or from the nix store, or a hybrid.

• The second one is the builder infrastructure

  I wouldn't get any value out of a ccache style solution as it requires host-specific config for every host/CI. I want to fundamentally fix the packaging model.

I don't know if this is the right channel for this question, but seeing as how I'm trying to build a Go application with devenv I figure it would be worth a shot.

I have a project that I'm using devenv to manage the development environment, and I have everyithng setup already so I can build the project with devenv build but the resulting binary just gets put in the nix store by default. I'm wanting to use the installPhase hook to put the resulting binary in the project directory but I seem to hit a roadblock in doing so. By default the resulting build artifact goes to a directory like /nix/store/l91035h1q89828h3vd5nzcss483k3k3g-dbctl-0.0.1, but I can't figure out what I need to do in the installPhase of my default.nix to have the resulting build artifact go to a path like ${PROJECT_ROOT}/out.

What I do know from trial and error:

• The PWD during the buildPhase and installPhase is /build/source
• The $out variable is set to the path to the Nix store (e.g. /nix/store/l91035h1q89828h3vd5nzcss483k3k3g-dbctl-0.0.1)
• $src doesn't seem to work either, as it results in a perms error

If it helps here is my default.nix file:

{ lib
, pkgs
, name
, version
, ...
}:
pkgs.buildGoApplication {
  pname = name;
  version = version;

  src = builtins.path {
    path = ./.;
    name = "source";
  };

  doCheck = false;

  modules = ./gomod2nix.toml;

  # installPhase = ''
  #   pwd
  #   mkdir -p $src/out/bin
  #   mv dbctl out/bin
  # '';

  meta = with lib; {
    description = "Database management tool for RowLogic";
    homepage = "";
    maintainers = [ ];
  };
}

In reply to@vendion:matrix.org

I don't know if this is the right channel for this question, but seeing as how I'm trying to build a Go application with devenv I figure it would be worth a shot.

I have a project that I'm using devenv to manage the development environment, and I have everyithng setup already so I can build the project with devenv build but the resulting binary just gets put in the nix store by default. I'm wanting to use the installPhase hook to put the resulting binary in the project directory but I seem to hit a roadblock in doing so. By default the resulting build artifact goes to a directory like /nix/store/l91035h1q89828h3vd5nzcss483k3k3g-dbctl-0.0.1, but I can't figure out what I need to do in the installPhase of my default.nix to have the resulting build artifact go to a path like ${PROJECT_ROOT}/out.

What I do know from trial and error:

• The PWD during the buildPhase and installPhase is /build/source
• The $out variable is set to the path to the Nix store (e.g. /nix/store/l91035h1q89828h3vd5nzcss483k3k3g-dbctl-0.0.1)
• $src doesn't seem to work either, as it results in a perms error

If it helps here is my default.nix file:

{ lib
, pkgs
, name
, version
, ...
}:
pkgs.buildGoApplication {
  pname = name;
  version = version;

  src = builtins.path {
    path = ./.;
    name = "source";
  };

  doCheck = false;

  modules = ./gomod2nix.toml;

  # installPhase = ''
  #   pwd
  #   mkdir -p $src/out/bin
  #   mv dbctl out/bin
  # '';

  meta = with lib; {
    description = "Database management tool for RowLogic";
    homepage = "";
    maintainers = [ ];
  };
}

In reply to @diamondburned:matrix.org
also I think you're trying to modify the source directory to add the build output? you can't do that

In reply to@vendion:matrix.org
Yeah, that is exactly what I was trying to do. Okay I'll have to rethink my approach as I was wanting to be able to use a CI pipeline to build the artifacts and use them as downloadable releases. The end users are not using Nix so having to work out deployment strategy