-
Notifications
You must be signed in to change notification settings - Fork 10
vscode-project.hxml #26
Comments
@MatthijsKamstra it 's an automated file generated file based on your build hxml, it will be deleted when you quit vscode, and it is updated when you edit you build hxml It contains on other thing the temporary path that is used when you edit your .hx file |
It only shows up when temp directory is enabled, right? Could we put it in the temp directory? Or does it need to be in the project dir? |
Wouldn't it be easier to just parse the source hxml file and pass arguments from it directly to the compiler? I was doing that in my ST plugin prototype and it worked out quite well: https://github.com/nadako/hxsublime/blob/master/src/BuildHelper.hx |
@jcward Well it is generated where your build is, if you want to move it on other
|
@nadako I m working on similar thing for target selection, but looking around i see that you can have pretty imbricated build.hxml file with or without --next --each And on other i prefer to have an internal generated file that maybe can be enhanced and used by the ide, who knows... |
There is also an option (not well tested) in the settings to use the tmp directory as your working directory : haxe.haxeUseTmpAsWorkingDirectory (false/true). It is setted to false by default. |
my 5cents
Not something I changed by my knowledge |
It is set now to auto by default, so if not overwritten in your settings it will try to use a tmp directory to avoid the saving problem of your .hx file each time you need completion. |
Hi
I just updated VSCode Haxe plugin, and the new thing I encountered:
which looks very similar to the build.hxml you need for vscode to work.
a new thing or a bug?
The text was updated successfully, but these errors were encountered: