New issue 86 by fintanbo...@gmail.com: Debug and Run configurations don't
work for Flash target
http://code.google.com/p/eclihx/issues/detail?id=86
What steps will reproduce the problem?
1. create a basic project and configure hxml file to target flash
2. setup run configuration
3. run
What is the expected output? What do you see instead?
should see a generated swf file in the out folder. Instead I see this
error for run:
Description Resource Path Location Type
/usr/lib/haxe/std/flash9/Boot.hx:199: characters 10-24, lines 199-199:
Unbound variable __this__ build.hxml /tmp Unknown Problem
What version of the product are you using? On what operating system?
OSX 10.6
Please provide any additional information below.
Is this a result of update to haXe 2.08?
Comment #1 on issue 86 by goodwi...@gmail.com: Debug and Run configurations
don't work for Flash target
http://code.google.com/p/eclihx/issues/detail?id=86
(No comment was entered for this change.)
Comment #3 on issue 86 by goodwi...@gmail.com: Debug and Run configurations
don't work for Flash target
http://code.google.com/p/eclihx/issues/detail?id=86
Hello! Could you confirm that it's still actually with the last version of
the eclihx from trunk. Is this problem persistant after building the
project from console without using eclihx?
Hi yes it is still a problem with latest version in trunk and I can build
successfully from terminal window using the same hxml file.
Very strange problem. The only proposal I have now is that eclihx is using
invalid version of compiler. Could you verify the path to the compiler
in "Window -> Preferences -> haXe(eclihx) -> Compiler"
The other place of debug information could be found in "Error Log" view
(Window -> Show View -> Others... -> General -> Error Log). A message with
description of last haXe compiler execution will be posted right after
launching (details could be seen via double click)
For example for my ubuntu environment the message is as follows:
Eclihx ExecuteProcess.
WorkingDirectory: "/home/goodwin/workspace-jdt/TestProblem".
CommandLine: "[/usr/bin/haxe,
/home/goodwin/workspace-jdt/TestProblem/build.hxml]".
Please also verify that all paths are equivalent to console execution.
Thank you for help, I'm really appreciate it.
The message for me is:
Eclihx ExecuteProcess.
WorkingDirectory: "/Users/fintan/Documents/ecliphx_workspace/HelloEclihx".
CommandLine: "[/usr/local/bin/haxe,
/Users/fintan/Documents/ecliphx_workspace/HelloEclihx/build.hxml]".
my console execution uses /usr/bin whereas Eclihx uses /usr/local/bin
I think /usr/local/bin is the default but this can be changed when
installing a development build of haXe
perhaps make this configurable in preferences?
In fact the haXe compiler path in execution message is planned to be the
same as typed in properties "Window -> Preferences -> haXe(eclihx) ->
Compiler". If it's not, then it's probably because of Issue 74
(http://code.google.com/p/eclihx/issues/detail?id=74).
Also I'm going to allow redefine global compiler path for the particular
project.
Hope will be able to resolve those tasks soon.
Comment #8 on issue 86 by goodwi...@gmail.com: Debug and Run configurations
don't work for Flash target
http://code.google.com/p/eclihx/issues/detail?id=86
I have close Issue 74. Now each haxe launch configuration has an option for
haXe compiler. It's possible to select a default one from the preferences
or set up an alternative one. I think you should be able to see your
previous compiler in alternative disabled text field. Hope this bug is done.
Yes I can confirm that it now works. Having an alternative compiler option
for each launch config is a nice feature too :-)