If I do deno --help it shows:
compile = Compile the script into a self-contained executable
install = Install script as an executable
What's the difference between these two commands?
Command
Output
Self contained 1
Deno runtime integrated 2
compile
binary
y
y
install
script (shell / .bat)
n
n
bundle
.js
y
n
1 self contained := includes local and remote dependencies / scripts, single file
2 integrated := no separate runtime is needed
Related
I have a multi-project build. One of my source directories is called "core" that unpacks down to the source files in normal project structure (main/scala/...)
Using the sbt command line, how can I run a main program called Hello.scala (object extends App)?
Tried:
> run my.package.path.Hello
> run Hello
> run
If you want to run some task scoped only to one subproject ("module"), you can do it with the project/task syntax, e.g.
core/run
See documentation on Scopes.
I'm creating a task in SBT that will upload some scripts to S3. I'm uploading to S3 using SBT external process with aws cli s"aws s3 cp ./someDir $uploadPath --recursive" ! log.
It throws error
java.io.IOException: Cannot run program "aws": CreateProcess error=2, The system cannot find the file specified
This happens only on Windows. It works fine when I run the same project/task in Ubuntu build system. AWS cli is installed on Windows machine and PATH is set correctly.
Its not clear to me what is missing.
It seems that the sbt internal process library does not include the PATH variables in windows.
A suitable workaround would be to extract your aws command in a separate file and trigger the execution of this file:
your doSomeStuff.bat would be:
aws s3 cp ./someDir $uploadPath --recursive
and in the build.sbt add
lazy val someStuff = taksKey[Unit]("Execute a aws command")
yarnBuild := {
"./doSomeStuff.bat" !
}
Another possible workaround is to run the command inside a shell (and you must know your shells for all "problematic" environments)
val shell: Seq[String] = if (sys.props("os.name").contains("Windows")) Seq("cmd", "/c") else Seq("bash", "-c")
val command: Seq[String] = shell :+ "<your command here>"
command .!
I am using Sublime Text 2 (2.0.1, build 2217) on Mac OS X (10.7.2).
I have installed the SASS Build package, but every time I try to build the SASS file, I get the following error:
[Errno 2] No such file or directory
My path seems to be correct, and copying the cmd directly and pasting it into the terminal works, I'm really confused why it just isn't working from within ST2.
Most likely such situation happened due to different Ruby versions installed on a machine.
For example I have 1.8.7 installed with Mac OS X by default and later I installed 1.9.3 using rvm for multiuser environment (i.e. into /usr/local/rvm)
I set current version in rvm but GEM_HOME still points to gems from 1.8.7
The only straight and dumb solution I've found - hack environment variables for Sublime Text 2. This can be done creating .py file with any name in folder:
~/Library/Application Support/Sublime Text 2/Packages/User/
See more information in Rob Dodson's blog post:
http://robdodson.me/blog/2012/05/14/hacking-the-path-variable-in-sublime-text/
Example .py that works for me:
import os
LOCAL = '/usr/local/bin:/usr/local/sbin:'
RVM = '/usr/local/rvm/bin:'
RVMGEMS = '/usr/local/rvm/gems/ruby-1.9.3-p392/bin:'
GEMHOME = '/usr/local/rvm/gems/ruby-1.9.3-p392'
# Sublime's default path is
# /usr/bin:/bin:/usr/sbin:/sbin
os.environ['PATH'] += ':'
os.environ['PATH'] += LOCAL
os.environ['PATH'] += RVM
os.environ['PATH'] += RVMGEMS
os.environ['GEM_HOME'] = GEMHOME
print 'PATH = ' + os.environ['PATH']
I am building a Makefile based project using Xcode4. How do I tell xcode to run a script that initializes environment variables for Intel's CC/fortran compiler prior to the Makefile being run?
I instead created a shell script that calls the Intel init scripts and then executes /usr/bin/make.
I am looking options to integrate Python 3 tools / scripts to Plone's buildout.cfg (which targets Python 2.6). How eggs between different buildout recipes are shared? Because namely, running setup.py for Python 3 eggs would cause syntax errors in Python 2 environment.
Can I specify Python 3 interpreter (in portable manner) for a buildout recipe like zc.recipe.egg
Will the rest of the buildout happily eat the eggs coming under this recipe using particular Python interpreter, or would it clash with the host environment
... or do one have to create a virtualenv inside buildout itself to get Python 3 stuff installed
You can specify the executable to be used by many recipes, including zc.recipe.egg:
[python3.3]
executable = /usr/local/bin/python3.3
[py3script]
recipe = zc.recipe.egg:scripts
python = python3.3
eggs = py3script
That should install the py3script scripts with python 3.3. The key here is the python key, which points to a section that should have a executable option, which is a path to the python executable you want to use.
The executable key is then used by the easy_install module internal to zc.buildout to run the setup.py script and install the egg.