Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand



Downloads of v 1.1.0:


Last Update:

03 Oct 2015

Package Maintainer(s):

Software Author(s):

  • Qt Project


build jom make nmake qt


This is not the latest version of jom available.

  • 1
  • 2
  • 3

1.1.0 | Updated: 03 Oct 2015



Downloads of v 1.1.0:



Software Author(s):

  • Qt Project

jom 1.1.0

This is not the latest version of jom available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install jom, run the following command from the command line or from PowerShell:


To upgrade jom, run the following command from the command line or from PowerShell:


To uninstall jom, run the following command from the command line or from PowerShell:


Deployment Method:


This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade jom -y --source="'INTERNAL REPO URL'" --version="'1.1.0'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade jom -y --source="'INTERNAL REPO URL'" --version="'1.1.0'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install jom
    name: jom
    version: '1.1.0'
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

chocolatey_package 'jom' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.1.0'

See docs at https://docs.chef.io/resource_chocolatey_package.html.

cChocoPackageInstaller jom
    Name     = "jom"
    Version  = "1.1.0"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.

package { 'jom':
  ensure   => '1.1.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.


Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

Package Approved

This package was approved by moderator ferventcoder on 28 Dec 2015.


jom is a clone of nmake to support the execution of multiple independent commands in parallel.
It basically adds the -j command line switch similar to GNU make.

$ErrorActionPreference = 'Stop'; # stop on all errors

$packageName = 'jom'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url = 'https://download.qt.io/official_releases/jom/jom_1_1_0.zip'

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  url           = $url

Install-ChocolateyZipPackage @packageArgs

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
jom 1.1.1 880 Friday, July 8, 2016 Approved
jom 1.1.0 1445 Saturday, October 3, 2015 Approved
jom 1.0.16 497 Friday, July 10, 2015 Approved

This is the changelog for jom 1.1.0, the parallel make tool.

Changes since jom 1.0.16

  • Restrict the number of parallel jobs in recursively called instances
    similar to GNU make's jobserver (QTCREATORBUG-10846).

Changes since jom 1.0.15

  • Fix occasional hang on exit (QTCREATORBUG-14600).

Changes since jom 1.0.14

  • Fix potential hang on error in a sub-jom.
  • Yield error on missing !endif directives (QTCREATORBUG-14211).
  • Fix ignoring exit codes greater than 255.
  • Fix /DUMPGRAPHDOT option (QTCREATORBUG-14004).
  • Fix $? filename macro for nonexistent targets (QTCREATORBUG-14125).
  • Fix quoting of dependencies with spaces (QTCREATORBUG-12296).

Changes since jom 1.0.13

  • Fix exit code forwarding. (QTCREATORBUG-11556)
  • Fix file name macro modifers for $** and $?. (QTCREATORBUG-6932)
  • Fix equal signs in semicolon command syntax. (QTCREATORBUG-7942)
  • Fix error line numbers for inline files. (QTCREATORBUG-8451)
  • Ignore macro assignments in inline files. (QTCREATORBUG-8452)
  • Yield error on unexpected !ENDIF directive.
  • Support wildcards in dependency lines. (QTCREATORBUG-10439)
  • Use IcrediBuild's BuildConsole instead of the XGE interface in ibjom.

Changes since jom 1.0.12

  • Fix spurious "Can't start command" error.
  • Fix passing of -j argument to subjoms.
  • Sanity check the -j argument.
  • Fix regression of non-functional set command in command blocks.
  • Fix handling of environment variables that would cause a syntax errors in
  • Fix handling of environment variables with lowercase names.

Changes since jom 1.0.11

  • Performance improvements.
  • Fixed whitespace in command line arguments. (QTCREATORBUG-7428)
  • Enhanced responsiveness of subjom output.
  • Separate output of stdout and stderr.
  • Fix the output of silent commands in /n mode. (QTCREATORBUG-7170)
  • Implemented the /U switch for dumping inline files.
  • Fix expansion of environment variables.

Changes since jom 1.0.10

  • Fix exit code for /k command line switch. (QTCREATORBUG-6987)
  • Fix spurious 0x0d characters in process output. (QTCREATORBUG-6986)
  • Fix process output ordering and printing of large amounts of output
    in recursive jom scenarios.
  • Improved performance by caching file time stamps.

Changes since jom 1.0.9

  • Fix regression that caused jom to fail on Windows XP.

Changes since jom 1.0.8

  • The GNU Make option -w is now supported to print the current working
    directory before and after other processing.
  • Fix crash when specifying a target for an empty makefile.
  • Fix lookup for targets in the Makefile's directory. (QTCREATORBUG-6546)
  • Fix handling of environment variables. (QTCREATORBUG-6578)
  • Specifying an exit code with the '-' command modifier was fixed.
  • Fix command modifiers in inference rules. (QTCREATORBUG-6742)
  • Fix parsing of the "ignore exit code" command modifier.
  • Fix (very rare) deadlock and zombie processes.
  • The preprocessor directive !include <file> now looks up files in the
    include directories correctly. (QTCREATORBUG-6869)

Changes since jom 1.0.7

  • Fix spawning of child processes that expect a valid stdin handle.
    E.g. xcopy couldn't be called anymore.
  • CMakeList.txt was fixed (thanks to Ryan Pavlik).

Changes since jom 1.0.6

  • Fix blank lines in output. (QTCREATORBUG-3974)
  • Small performance improvement due to compilation with
  • Ctrl-C handling has been revisited. Much simpler and more correct.
    Before the compiler jobs didn't get a Ctrl-C but were terminated.
  • Special .SYNC dependents implemented. See README for a small description.
  • Handle quoted dollar signs in inline files correctly. (QTCREATORBUG-2875)
  • Respect the MAKEFLAGS environment variable. (QTCREATORBUG-5028)
  • Complete detection of cmd builtins. This fixes annoying warnings when building
    with IncrediBuild.

Changes since jom 1.0.5

  • Fix mean monster spawn issue.

Changes since jom 1.0.4

  • Fix out of date check for pseudotargets. (QTCREATORBUG-3909)

Changes since jom 1.0.3

  • Fix that -j1 wasn't passed to sub jom calls. (QTCREATORBUG-3729)
  • /KEEPTEMPFILES was added for debugging purposes. (QTCREATORBUG-3852)
  • Performance boost for incremental builds.
  • Improved Ctrl-C handling for recursive make.

Changes since jom 1.0.2

  • Support variable names with underscores. (QTCREATORBUG-3235)
  • Keep order of dependencies on build. This is important for makefiles
    lacking complete dependencies. These might fail in parallel builds
  • Fix issues wrt environment variables. (QTCREATORBUG-3108)

Changes since jom 1.0.1

  • Make target names case insensitive. (QTCREATORBUG-3037)
  • Fix reading of include files without newline at the end.
  • Repair the cmake project file for jom.

Changes since jom 1.0.0

  • Cleaner and faster determination of targets that must be built.
  • Fix incomplete up-to-date check for inference rule targets.
  • Don't filter comments in inline files. (QTCREATORBUG-2874)

Changes since jom 0.9.4

  • Inference rule batch mode implemented.
    This improves performance for makefiles that make heavy use of the batch
    mode, e.g. qmake generated makefiles.
  • Improved command execution. No more batch file writing.
  • Macro substitution implemented. Macro expansions like
    $(TARGET:suffix=d) are now possible.
  • .SUFFIXES content is handled properly.
  • Fixed several bugs in file name macro expansion.
  • Output of concurrent processes is explicitely separated.

Changes since jom 0.9.3

  • Opening files from volume mounted to NTFS directory fixed.
  • Output buffering issue fixed. (QTBUG-10798)

Changes since jom 0.9.2

  • Support for multiple inline files per command line added.
  • Its now possible to use "." as target name. (QTCREATORBUG-1131)
  • Support file name macros in the file name part of inline file defitions.
  • Multiple file name macros per command line are possible now.
  • Single name macro invocation was added.
    They can be invoked like this: $A instead of $(A).
  • Several bugs related to file name macros have been fixed.
  • Handle quoted arguments from command files correctly.

Changes since jom 0.9.1

  • Fixed conditionals in preprocessor expressions. (QTCREATORBUG-1091)
  • Improved parser error messages. Now we see the file, in which the
    error occurred. (QTCREATORBUG-1114)

Changes since jom 0.9.0

  • Having too many rules for a target is now a warning and not an error.
  • Fixed several bugs in the preprocessor expression parser, e.g.

Changes since jom 0.8.9

  • Reset the ERRORLEVEL to zero, if command's exit code should be ignored.
  • Command files can be used to pass command line options to jom.
    Usage: jom @commands.txt
  • ANTLR isn't used anymore. We're using QLALR to generate the parser for
    preprocessor expressions now. This makes building jom much easier.

This package has no dependencies.

Discussion for the jom Package

Ground Rules:

  • This discussion is only about jom and the jom package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or jom, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus