1. 22 Mar, 2018 1 commit
  2. 04 Dec, 2017 2 commits
    • Giovanni Campagna's avatar
      IdeBuildTarget: add get_language() · b2e1d33e
      Giovanni Campagna authored
      Add a way to find the programming language of a build target.
      This will be used to weed out incompatible debuggers, profiling
      tools, etc.
      Cargo build targets are changed to return rust, NPM to return JS.
      Similarly, a future Cabal integration should say Haskell, Maven or ANT
      should say Java, etc.
      For now, automake, meson and cmake return "asm" (native code),
      because it's annoying to find if the build target is built from C,
      C++, Vala or Fortran, and it does not matter too much because gdb
      and valgrind can deal with it.
    • Giovanni Campagna's avatar
      IdeBuildTarget: add get_cwd() · e891c088
      Giovanni Campagna authored
      Some build systems (notably, npm), insist that their build targets
      be run in a specific working directory, or they'll misbehave.
      To allow BuildTargets and BuildTargetProviders specify that,
      introduce a vfunc get_cwd(). If this vfunc returns any non-NULL
      value, IdeRuntime uses it to set the cwd of the created IdeRunner.
  3. 23 Nov, 2017 1 commit
  4. 20 Nov, 2017 1 commit
    • Christian Hergert's avatar
      buildsystem: add IdeBuildTargetProvider interface · d61623d5
      Christian Hergert authored
      This moves away from using the build system API for getting
      build targets to this new interface. Build systems will need
      to implement this if they want to support running.
      This will also allow for things like Flatpak to provide a
      default target matching the "command" from the manifest.
  5. 07 Nov, 2017 1 commit
  6. 11 Oct, 2017 1 commit
  7. 03 Oct, 2017 1 commit
  8. 21 Sep, 2017 1 commit
    • Christian Hergert's avatar
      source tree reorganization · 9b9db776
      Christian Hergert authored
      As the project has grown, we've let things get a bit out of their
      logical place. This does a bit of cleanup and tries to bring some
      of the embedded resources closer to where they are used.
      But more importantly, this allows us to clean some things up to
      the point that we can move forward statically linking a bunch of
      the plugins into libide. The plan here is to speed up the initial
      loading by avoiding lots of disk I/O stats which are currently
      hurting us.
  9. 10 Feb, 2017 1 commit
    • Matthew Leeds's avatar
      flatpak: Use flatpak-build for the runner · 82283e92
      Matthew Leeds authored
      We're not doing a full flatpak install to a repo, just building the app
      and running the built binary. So this commit fixes the flatpak runtime's
      create_runner function to use flatpak-build rather than flatpak-run.
      In order to get the name of the binary, it was necessary to add a
      get_name function to the IdeBuildTarget interface and implement it for
  10. 17 Jul, 2016 1 commit
  11. 03 Feb, 2016 1 commit
  12. 29 Jan, 2016 1 commit
  13. 28 Jan, 2016 3 commits
  14. 15 Jan, 2016 1 commit
  15. 17 Dec, 2015 1 commit