Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I normally run it like this:</p> <pre><code>&gt; node dojo/dojo.js load=build --profile myprofile.profile.js --release </code></pre> <p>This would build a release for the profile contained in myprofile.profile.js. It assumes you are in a directory, which contains both dojo and util as sub-directories. It also assumes that the path to node is set correctly.</p> <p>If node is not configured in the path variable, you will need to use the full path to node:</p> <pre><code>&gt; &lt;path to node here&gt; dojo/dojo.js load=build --profile myprofile.profile.js --release </code></pre> <p>On windows the path is normally <b>C:\Program Files\nodejs\</b> but you might have to configure it as <b>C:\PROGRA~1\nodejs\</b> to get it working.</p> <p><br /><b>Windows Notes:</b><br /> The build scripts do not work with Node on Windows (except using Cygwin). If you are using Windows you can get it to work via the following patch:</p> <ul><li><a href="http://bugs.dojotoolkit.org/ticket/15413" rel="noreferrer">Windows Patch</a></li></ul> <p>Use the attached <em>node-win.patch</em> file to edit the files: <em>util/build/main.js</em> and <em>util/build/transforms/writeOptimized.js</em>. The patch has worked for me 100% of the time and it a simple matter editing a few lines of code.</p> <p>I've personally found the alternative to Node, using Rhino, useless. It always fails to detect the build paths correctly, no-matter what I set basePath to. I would strongly advise using Node over Rhino as it is more reliable and easier to setup.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload