On 2014/08/13 21:06, Rupali Roychoudhury wrote:
> Hi Mark,
>
> Thank you for the solutions
> I think I am doing something wrong
>
> This is what i did:
> 1) I installed python27 in C:\python27 directory
> 2) I go to command prompt then i go to C:\python directory and type
> <python script> but it shows this message:The syntax of the command is
> incorrect.
> what do you suggest?
"<python script>" is supposed to be replaced by the name of the python
script you are running, e.g. "emmake" (I'm not actually sure emmake is a
python script so it might be a bad example).
Add C:\python27 in your Windows PATH environment variable, start cmd.exe
(command prompt) then do
cd C:\path\to\your\makefile
emmake.bat
This assumes you have the emscripten directory in your path so that
emmake.bat can be found. There is a foo.bat for each Emscripten command
foo to support use from cmd.exe.
>
> I also have a few queries, the solutions mentioned, will it help to
> get rid of the message "/bin/env: python2: No such file or
> directory"(mentioned in my previous post)?
Yes.
> and why?
Short answer; because both Windows, and therefore cmd.exe, and python
treat #! tags as comments and do not use /bin/env.
Long answer:
Unix-like operating systems (in the case of cygwin, the cygwin dll's
implementation of the exec system call) look for #! tags at the start of
scripts. Sometimes #! is followed by the full path to the executable for
the relevant scripting language (e.g. #! /bin/bash). In other cases it
is followed simply by the executable name (e.g. #! python). In the
former case the system (cygwin) runs the executable passing the script
as an argument. In the latter case the system runs the program /bin/env
which searches your environment for the specified executable. When it is
not found it prints the message "/bin/env: xxxx: No such file or
directory". When it is found, the system runs the found executable as
if the following command had been typed:
/path/to/found/python /path/to/emmake
The above .bat command does something like
python \path\to\emmake
In both cases python correctly treats the #! in emmake as a comment.
Only (some) operating systems pay attention to #!. Applications never do.
Regards
-Mark
--
注意：この電子メールには、株式会社エイチアイの機密情報が含まれている場合
が有ります。正式なメール受信者では無い場合はメール複製、 再配信または情
報の使用を固く禁じております。エラー、手違いでこのメールを受け取られまし
たら削除を行い配信者にご連絡をお願いいたし ます.
NOTE: This electronic mail message may contain confidential and
privileged information from HI Corporation. If you are not the intended
recipient, any disclosure, photocopying, distribution or use of the
contents of the received information is prohibited. If you have received
this e-mail in error, please notify the sender immediately and
permanently delete this message and all related copies.
--
You received this message because you are subscribed to the Google Groups
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
