Making applications build system-aware
Build systems for web applications are great: they give dependency management, code minification, and the ability to use tech like SASS or CoffeeScript that require pre-processing.
Thinking about a language for build definitions
I want to write a little tool that parses build definitions and converts them to a ninja.build file. It should not abstract compilation like CMake or Meson, but be similar to make in that you manually write the commands for a build step.
Separate Version Control repository as Binary Package repository?
(( The context I have is, but is I think not too important to this question: Windows only development; Visual Studio; mostly C++ with some .NET/C# ))
Separate Version Control repository as Binary Package repository?
(( The context I have is, but is I think not too important to this question: Windows only development; Visual Studio; mostly C++ with some .NET/C# ))
Separate Version Control repository as Binary Package repository?
(( The context I have is, but is I think not too important to this question: Windows only development; Visual Studio; mostly C++ with some .NET/C# ))
Pipeline-like calculations with intermediate files: should I use a build system?
I have seen multiple examples of systems that are organized essentially like a pipeline. Each stage produces some intermediate files which are then consumed by the next stage. Also, these take a long time and contain custom code, shell scripts and everything else imaginable (as opposed to everything neatly written in programming language X).
Haskell build and artifact environment similar to Maven
I used to be a Java developer for a long time, but recently, I joined a Haskell team.
In the java world, if you have a large project,
with several teams working on it, a common approach is to use an artifact server such as Maven to ease and speed-up the development.
Numerous build tools, such as Ant, Maven, Gradle, can build the project and
upload a jar file to the artifact server that can be used by the rest of the team
without pain.
Therefore,
by splitting the project into smaller sub-projects, the build time is also drastically reduced.
Haskell build and artifact environment similar to Maven
I used to be a Java developer for a long time, but recently, I joined a Haskell team.
In the java world, if you have a large project,
with several teams working on it, a common approach is to use an artifact server such as Maven to ease and speed-up the development.
Numerous build tools, such as Ant, Maven, Gradle, can build the project and
upload a jar file to the artifact server that can be used by the rest of the team
without pain.
Therefore,
by splitting the project into smaller sub-projects, the build time is also drastically reduced.
Haskell build and artifact environment similar to Maven
I used to be a Java developer for a long time, but recently, I joined a Haskell team.
In the java world, if you have a large project,
with several teams working on it, a common approach is to use an artifact server such as Maven to ease and speed-up the development.
Numerous build tools, such as Ant, Maven, Gradle, can build the project and
upload a jar file to the artifact server that can be used by the rest of the team
without pain.
Therefore,
by splitting the project into smaller sub-projects, the build time is also drastically reduced.
Haskell build and artifact environment similar to Maven
I used to be a Java developer for a long time, but recently, I joined a Haskell team.
In the java world, if you have a large project,
with several teams working on it, a common approach is to use an artifact server such as Maven to ease and speed-up the development.
Numerous build tools, such as Ant, Maven, Gradle, can build the project and
upload a jar file to the artifact server that can be used by the rest of the team
without pain.
Therefore,
by splitting the project into smaller sub-projects, the build time is also drastically reduced.